#2144: shadow-4.1.0 --------------------------------------+------------------------------------- Reporter: [EMAIL PROTECTED] | Owner: [email protected] Type: task | Status: new Priority: normal | Milestone: 7.0 Component: Book | Version: SVN Severity: normal | Resolution: Keywords: | --------------------------------------+------------------------------------- Comment (by [EMAIL PROTECTED]):
Now I'm confused - the behaviour of useradd from shadow 4.1.0 is the same as previous versions - if you do not specify a group on the command line using -g, then a group with the same name as the user is created by default. The "command line" override for this behaviour is to manually specify a group to use. OR maybe I'm not understanding the issue.... tests from lfs6.3-20070731 rc2 show what I expected to see, and what the new version does as well. Note that GID 1000 (admin) was already created previously, and portions of /etc/passwd and /etc/group have been redacted. -bash-3.2# cat /etc/lfs-release 6.3-20070731 - jhalfs build -bash-3.2# cat /etc/default/useradd # useradd defaults file HOME=/home INACTIVE=-1 EXPIRE= SHELL=/bin/bash SKEL=/etc/skel CREATE_MAIL_SPOOL=no -bash-3.2# useradd fubar -bash-3.2# useradd barfu -g admin -bash-3.2# cat /etc/passwd fubar:x:1001:1001::/home/fubar:/bin/bash barfu:x:1002:1000::/home/barfu:/bin/bash -bash-3.2# cat /etc/group admin:x:1000: fubar:x:1001: So, fubar gets a new group, also called fubar barfu gets the main system group of admin, but no private group. Is this not the behaviour of shadow 4.1.0? (the "group 1000 not found is a seperate issue) -- Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2144#comment:13> LFS Trac <http://wiki.linuxfromscratch.org/lfs/> Linux From Scratch: Your Distro, Your Rules. -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
