Message-Id: <1330880212.26962.140661044634665@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"
In-Reply-To: <CAHwjr34S+diQ=y84AzAy67xUMyrxqFM=aG-7W5=4b2q9JnmSzw@mail.gmail.com>
References: <1330852060.31716.140661044540177@webmail.messagingengine.com>
 <CAHwjr34S+diQ=y84AzAy67xUMyrxqFM=aG-7W5=4b2q9JnmSzw@mail.gmail.com>
Subject: Re: [alpine-devel] Understanding alpine-setup
Date: Sun, 04 Mar 2012 11:56:52 -0500

Thanks Jeff for your reply.

> > 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?
> 
> The idea with that option is to create an apkovl that can be copied to
> boot media.  On boot, those settings would be copied into tmpfs along
> with the packages that are specified in that overlay file.  However, I
> haven't done much with that option in the past.

Yes, I figured it was supposed to do something like that. But I don't
see how it could succeed in doing so, in the scripts as currently
written (on the 2.3.6 ISO). Or is your last sentence acknowledging that
this functionality is still being developed?

I realize many of these scripts are most likely works in progress, and
maybe no one's even aimed to fully document them yet. Nonetheless I
thought it might still be useful for me to point out these gaps as I see
them. And once I get myself better set up on Alpine, I will post patches
or enter bug reports directly. At the moment, I'm still just getting
into the water.



On Sun, Mar 4, 2012, at 05:19 AM, lists+alpine-devel@jimpryor.net wrote:

> 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?

Things I notice with setup-bootable:

* undocumented that the script respects MNT when SOURCE is a ISO
* The usage message neglects to say that SOURCE can also be a url.
* undocumented that the script respects WGET when SOURCE is a url
* The usage message says that DEST/$2 can be a mounted directory or a
device. This may be misleading: (a) If I mount /dev/foo to /mnt/foo, and
then there exists a /mnt/foo/subdir, does the latter count as a "mounted
directory"? I wouldn't be sure it doesn't; however, if I understand the
logic of setup-bootable correctly, I can't provide /mnt/foo/subdir as a
value for $2. Perhaps it would be clearer to say "a directory
mountpoint" instead of "a mounted directory"? That would also help with
the second misleading aspect: (b) DEST need not be mounted;
setup-bootable will try to mount it and I guess if it's listed in the
fstab will succeed.
* When setting srcdir, an echo ... | sed ... construct is used to strip
any trailing "/". Is there a specific reason for doing it that way,
instead of just with srcdir=${src%/}, as is done several times elsewhere
in the same script?


I started to make a wiki page to document the setup scripts better.
Based solely on my skimming of the code. If some of this is also
documented elsewhere in the wiki, such as in
http://wiki.alpinelinux.org/wiki/Alpine_Linux_Handbook, I expect I'll
notice eventually and will try to integrate the notes then. Or someone
else who notices this is welcome to point it out.

Anyone should of course feel free to correct inaccuracies or
misunderstandings I express on that page.

Reading setup-disk now...
-- 
Jim Pryor
jim@jimpryor.net



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---