Christian Perrier wrote:
> 1) Create a udeb from shadow and use it
>
> 2) use our own udeb in d-i tree, stealing as much as possible from
> shadow
>
> 3) create two smaller udebs, one for the root password stuff and
> another for the user creation
4) Run dpkg-reconfigure passwd from inside d-i using the passthrough
frontend to let it talk to the user with cdebconf.
That's what I'm hoping to do for this and a lot of other parts of
base-config (notably tasksel). There's no reason to use udebs for this
stuff. There was a reason to use udebs for clock, timezone, and apt
setup, since they can be simplified by being tied into the installer
and/or by running before there is a base system.
> passwd config script is fairly simple and actually does something ONLY
> on "reconfigure" so, in (very) short, it is only useful on new systems
> installs.
That's a good point and if the passwd mantainers prefer to not have the
password prompting in there for that reason we can come up with another
approach, but I still don't see a reason to do it in code that runs in
the d-i environment as opposed to code that runs in the base system.
Anyway, the next bits I really want to deal with in base-config after
the beta are:
- finishing moving apt-setup out
- then removing the redundant keyboard and hostname setup stuff
(after making sure d-i configures them appropriatly in all cases)
- and only then worrying about passwd, second-stage preseeding,
tasksel, and exim setup.
If all of those can be migrated to run inside d-i and work ok which is
still unknown in the case of tasksel), then base-config can be removed.
--
see shy jo
Attachment:
signature.asc
Description: Digital signature