X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail.tanael.org (unknown [213.234.126.134]) by lists.alpinelinux.org (Postfix) with ESMTP id B65141EB59F for ; Tue, 24 Aug 2010 11:06:14 +0000 (UTC) Received: from [10.65.65.1] (unknown [213.234.126.129]) by mail.tanael.org (Postfix) with ESMTP id 882A6A3DA62F; Tue, 24 Aug 2010 11:06:14 +0000 (UTC) Subject: Re: [alpine-devel] Unattended Installation Ideas for 2.1 From: Natanael Copa To: Matt Smith Cc: alpine-devel@lists.alpinelinux.org In-Reply-To: <1282350536.779815473@192.168.2.227> References: <1282212187.424930332@192.168.2.231> <1282307707.31207.1887.camel@ncopa-desktop.nor.wtbts.net> <1282350536.779815473@192.168.2.227> Content-Type: text/plain; charset="UTF-8" Date: Tue, 24 Aug 2010 13:02:20 +0200 Message-ID: <1282647740.5375.1573.camel@ncopa-desktop.nor.wtbts.net> X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 X-Mailer: Evolution 2.30.2 Content-Transfer-Encoding: 7bit On Fri, 2010-08-20 at 19:28 -0500, Matt Smith wrote: > > So, we have the kick-in mechanism more or less worked out. Some > > questions remains. What do we call the beast? alpine-setup? auto-setup? > > unattended-setup? kickstart? (redhats) > > What about Alpine Unattended Setup (AUS), or Alpine Linux Unattended Setup (ALUS)? > I kinda like AUS. ok. > > We should probably make a service that is triggered if the boot param is > > found (from initramfs) so it is kicked in before login prompt. > > Sounds good. > > > Now, the real question is, how do we do the auto-answer on setup > > scripts. I'd like have that part working before we write any code that > > triggers it. > > As for the free-form idea, I say we recommend either "expect" or a simpler > version of "expect". Simple reason being that without a large amount of > effort, and even then, it's largely impossible to provide an "accept the > defaults" option for anything and everything the user might want to use > during the unattended install. I created lua-pty package which lets you control apps from lua via ptys, similar to what expect does. We dont have expect so we need a package for it. It does require tcl so dependencies might be several MB. If we use lua we get away with 300K probably. There is a expect-light project, but it seems to require expect http://expect-lite.sourceforge.net/ Otherwise we have "emtpy" http://empty.sourceforge.net/ which seems like a good alternative. -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---