On Sun 17 Aug 2014 at 16:03:13 +0200, Christian PERRIER wrote: > Quoting Brian Potkin (claremont...@gmail.com): > > > > After more thinking, my (wild) guess is that, at the time this is > > > done, these groups...do not exist on the system. And "adduser <user> > > > <group>" then fails when "<group>" doesn't exist. > > > > > > If I'm right, there are probably traces of this is the installer log, I'd > > > guess. > > > > Not such a wild guess. > > .../... > > Right. > > The package changelog indeed does give the key: > > user-setup (1.3) unstable; urgency=low > > * Add first user to two additional groups: netdev and powerdev > Note that this assumes that something creates these groups during > the task installation, as hal does with powerdev. The first user is added > to the groups in finish-install so the groups need not be static. > Closes: #352713 > > .../... > > -- Joey Hess <jo...@debian.org> Mon, 10 Jul 2006 18:23:44 -0400 > > In short, if packages that need some groups are installed *during > installation*, then the first created user will be added to these > groups.
I'm beginning to see the light. base-passwd copies group.master to /etc/group. Other installed programs create groups as needed. For example, ifupdown creates netdev and systemd adds systemd-journal. Here was me thinking d-i itself created groups. If I go for the "Printer server" task I'd now expect it to create lpadmin. And so it does. And the first user is a member of that group. > Which brings the question: what package is in charge of creating "lpadmin"? The postinst of cups-daemon. May I leave it to you deal with this non-bug? Close it or mark it "wontfix" and leave it open as a sign of user naïvety. :) Regards, Brian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/17082014180110.9e057a705...@desktop.copernicus.demon.co.uk
