Re: diskles-image-*
> Adam> Hmm... These are pretty much all things which are currently
> Adam> handled by dbootstrap. I think we should make an effort so
> Adam> that base2_2.tgz, even w/o dbootstrap's "configure base
> Adam> system" option, is in some sort of reasonable state. Should
> Adam> we provide defaults for all of the above? Would you be
> Adam> willing to patch against our CVS's basefile.sh and get it
> Adam> done that way?
>
>Either some reasonable defaults and/or a script that will prompt
>the user for the required information (as required, eg for
>selecting the timezone - I am not sure if this is still an issue
>for potato).
It is.
> >> The only real solution I can think of is to have a file on the
> >> base2_2.tgz that does configuration automatically. So then my
> >> script would look like:
> >>
> >> if [ -f /sbin/configure-image ]; then /sbin/configure-image rm
> >> /sbin/configure-image endif
> >>
> >> Which would mean that all the messy, version specific code, is
> >> where it belongs, within the base image. The same script, could
> >> be used when installing from the boot disk, too. However, this
> >> affects packages outside my own, so I thought I should post
> >> here to get the opinion of other developers.
> >>
> >> Any ideas? What should I do?
>
> Adam> I think you're right that this would be the best thing to
> Adam> do. That just means that someone should take the
> Adam> configuration stuff, and port it *out* of dbootstrap, and
> Adam> into something else (either C code using newt like the new
> Adam> tasksel, or else debconf-tiny compatible stuff --
> Adam> debconf-tiny is probably going to be pushed into base).
>
>debconf-tiny sounds like it might be the best approach. More
>standard. I have no idea though what debconf-tiny is, or how to
>program debconf even - these are issues I am going to find out soon.
The nice thing is that we could run 'dpkg-reconfigure <whatever>' to
rerun the debconf configuration whenever.
Ideally, base packages themselves should all support debconf.
However, that is not yet so. I am conflicted whether we should try to
take at least the postinstallation tasks and debconf-tiny'ify them,
and try to either:
(a) get the upstream base pkg maintainers to add the scripts
(probably not possible)
(b) make a new little package, base-config which has all this stuff,
then you cuold do 'dpkg-reconfigure base-config' or some such
(c) just have the scripts be part of the boot-floppies themselves
>It has been a while since I looked at this configuration stuff.
>Wondering aloud: Are there any parts that are not appropriate for
>NFS-Root systems? Probably the network configuration is redundant (the
>NFS-Root kernel automatically detects this at startup).
Shaleh and Marcel are working on bootp/dhcp for this, which is more
appropriate.
>The loopback
>(ie localhost) device must be configured though.
Ah yes, I think that is done, but only if there is no other network....
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: