Subject: Re: [alpine-devel] Should `setup-apkrepos -f` if fails.
To: alpine-devel@lists.alpinelinux.org
References: <CABErt4d0f0BfDk3itMnbrMuHQRixD=a3EGCeEnyVt=Kr1E3MzA@mail.gmail.com>
 <4794e0ed-092a-c051-d850-bef86b8bb475@linux.ibm.com>
 <20190308155207.GA7260@homura.localdomain>
From: Tuan Hoang <tmhoang@linux.ibm.com>
Date: Fri, 8 Mar 2019 17:00:47 +0100
Precedence: list
MIME-Version: 1.0
In-Reply-To: <20190308155207.GA7260@homura.localdomain>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Message-Id: <e831e144-ac3b-ad3b-98c9-2c9371547089@linux.ibm.com>

I would love to hear opinions from Alpine dev team on this matter.

What's in my mind is something like established method like kickstart
(and preseed too?).

Something like, you have an init service that watches for kernel parm
'auto_inst'. If there is, it starts the automated installer for you (and
somehow can reuse our setup-* scripts), with a provided configuration
file. Could be like 'auto_inst=https://yoursite.com/auto_inst.conf'. I
think this would be a nice fit for Alpine.


On 3/8/19 4:52 PM, Drew DeVault wrote:
> A little bit late to this thread, but I found the installation scripts
> wholely unsuitable for unattended installation. You're probably better
> off ditching them. Here's the script I use:
> 
> https://git.sr.ht/~sircmpwn/builds.sr.ht/tree/master/images/alpine/genimg
> 
> Feel free to adapt it to your needs. IMO given the simplicity of doing
> these steps manually, I think that the setup-* scripts should be
> considered useful only in an interactive install.
> 
> 
> ---
> Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
> Help:         alpine-devel+help@lists.alpinelinux.org
> ---
> 



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---