X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@mail.alpinelinux.org Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.alpinelinux.org (Postfix) with ESMTPS id 797DADC19A2 for ; Sun, 4 Mar 2012 09:07:41 +0000 (UTC) Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 000A1207E6 for ; Sun, 4 Mar 2012 04:07:40 -0500 (EST) Received: from web4.nyi.mail.srv.osa ([10.202.2.214]) by compute6.internal (MEProxy); Sun, 04 Mar 2012 04:07:40 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date; s=smtpout; bh=OjAgNUru7XEXy3XT4fG4i6jqVy4=; b=en3NfoS80G38AZS7qtv2bYORJ8P7 95K9VVcfO4VXH78/FKEf6WWX0ALyfVFKgJliZUDhGFcvBuFCAuzlcr0n8b/l/aW9 A2aMADANpbX2MR0cHmXx0CFhXztkNobpKoQHwC8AXn+7/ruPOHTMXH9KFG8ZuZbo Z0DLBZxc/YGx53c= Received: by web4.nyi.mail.srv.osa (Postfix, from userid 99) id D13B43C1FA5; Sun, 4 Mar 2012 04:07:40 -0500 (EST) Message-Id: <1330852060.31716.140661044540177@webmail.messagingengine.com> X-Sasl-Enc: uYDEbHNXN9RWqw2uMPJhdmLQBsnsrmnpWOEf+1Al1psA 1330852060 From: lists+alpine-devel@jimpryor.net To: alpine-devel@lists.alpinelinux.org X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" X-Mailer: MessagingEngine.com Webmail Interface Subject: [alpine-devel] Understanding alpine-setup Date: Sun, 04 Mar 2012 04:07:40 -0500 Hi, I recently discovered Alpine, and it looks great! --- like most of what I'd been hankering for when dissatisfied with Arch or FreeBSD. I've tried it out on a test system and am eager to start using it in earnest. I'm trying to do a somewhat custom install (onto a pre-partitioned LVM-over-luks drive), and thought I should read through the setup scripts to see what's going on. There's only the thinnest of information available on the Wiki. (Only for LVM, not for luks, and not for LVM during installation.) But it looks like the installation scripts are either using some very subtle tricks or are very much works in progress. I thought I had better start asking questions. In setup-alpine: 1. The "-q" option is parsed but not documented in usage. Intentionally? 2. The "-a" option is bewildering. If I supply it, we create a directory under /tmp and save its name in ROOT. However we set a trap on exit to remove this directory, and never cancel the trap. From what I've seen so far, that ROOT directory is never copied anywhere else, right? So this functionality doesn't yet work? Also, the ROOT variable isn't exported, so I don't see how the subroutine scripts like setup-{hostname,interfaces,keymap} expect to have it populated. Is all of this just under construction? 3. And if I don't supply the "-a" option, then setup-alpine sets PKGADD="apk add"; but then so far as I can see, PKGADD is never again referenced in any of the setup-* scripts. That's what puzzles me so far. Still reading... -- Jim Pryor jim@jimpryor.net --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---