From the changelog of user-setup, the D-I component that sets the root user password AND creates the first regular user:> * 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 addedIt should be time to take advantage of the new "add user to useful groups" feature of adduser (--add_extra_groups). The problem is that these "extra" groups is defined in /etc/adduser.conf so the task of maintaining the list of default extra groups would be delegated to the maintainer of adduser. PS to Marc (Haber): would you be OK to work with us (D-I team) to define a "reasonable" list of "extra" groups? That should be the list of groups which it seems reasonable to pu the first created user in (audio, etc...) PS2 to Marc: it seems that adduser.conf(5) does not document the newly added directive(s) to deal with extra groups.
This one time, at band camp, Christian Perrier said:> From the changelog of user-setup, the D-I component that sets the root > user password AND creates the first regular user: > > > * 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 > > > It should be time to take advantage of the new "add user to useful > groups" feature of adduser (--add_extra_groups). The problem is that > these "extra" groups is defined in /etc/adduser.conf so the task of > maintaining the list of default extra groups would be delegated to the > maintainer of adduser. > > PS to Marc (Haber): would you be OK to work with us (D-I team) to > define a "reasonable" list of "extra" groups? That should be the list > of groups which it seems reasonable to pu the first created user in > (audio, etc...) > > PS2 to Marc: it seems that adduser.conf(5) does not document the newly > added directive(s) to deal with extra groups.That is true - I will add something as soon as I find the time. -- ----------------------------------------------------------------- | ,''''`. Stephen Gran | | : :'' : sgran@debian.org | | `. `'' Debian user, admin, and developer | | `- http://www.debian.org | ----------------------------------------------------------------- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/adduser-devel/attachments/20060711/fe1db231/attachment.pgp
> Should the default UID of the first user be indicated but optional so > that it can be matched to one used throughout a local network?It''s actually preseedable in D-I through passwd/user-uid.... -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/adduser-devel/attachments/20060711/9e673a19/attachment.pgp
On Tue 11 Jul, Christian Perrier wrote:> From the changelog of user-setup, the D-I component that sets the root > user password AND creates the first regular user: > > > * 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 > > > It should be time to take advantage of the new "add user to useful > groups" feature of adduser (--add_extra_groups). The problem is that> these "extra" groups is defined in /etc/adduser.conf so the task of > maintaining the list of default extra groups would be delegated to the > maintainer of adduser. >Should the default UID of the first user be indicated but optional so that it can be matched to one used throughout a local network? -- Chris Bell