Message-Id: <1330856371.12000.140661044546873@webmail.messagingengine.com>
From: lists+alpine-devel@jimpryor.net
To: alpine-devel@lists.alpinelinux.org
Precedence: list
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
References: <1330852060.31716.140661044540177@webmail.messagingengine.com>
Subject: [alpine-devel] Re: Understanding alpine-setup
In-Reply-To: <1330852060.31716.140661044540177@webmail.messagingengine.com>
Date: Sun, 04 Mar 2012 05:19:31 -0500

Thanks Paul for the reply; that helps give me some guidance.

I'm still reading the setup scripts to get a general overview though.
Some more questions...

* In setup-interfaces, in various places, the response "abort" is parsed
but undocumented. Intentional?

* Perhaps not a problem, but I notice that "none" is only accepted by
setup-lbu interactively. You can't pass it in via the LBUOPTS variable
in an ANSWERFILE read by alpine-setup. On the other hand, you can pass
"none" to setup-apkcache in that way. Just verifying that this
difference is intended. Is the idea that running setup-lbu isn't
optional if the diskmode isn't "sys"? (But then why permit "none" as an
interactive answer?)

* setup-cryptswap tries to apk add cryptsetup-luks, but this package
doesn't exist (anymore)? Should it just be cryptsetup?

About to dive into setup-bootable and setup-disk now. It looks like
setup-bootable (like setup-cryptswap and some others) is only invoked
manually, correct?

-- 
Jim Pryor
jim@jimpryor.net



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---