#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]):
Replying to [comment:7 Bryan Kadzban]:
> Replying to [comment:6 [EMAIL PROTECTED]:
> > The user was created in group 1001, dunno if that is what you guys
expected ?
>
> By that do you mean that the user's primary GID (the one in /etc/passwd)
was 1001? What group name is that?
>
> I didn't really expect it, no...
First time, I added user fubar with just 'useradd fubar', then user barfu
with -g users. From passwd:
{{{
fubar:x:1000:1001::/home/fubar:/bin/bash
barfu:x:1001:1000::/home/barfu:/bin/bash
}}}
and from group:
{{{
users:x:1000:
fubar:x:1001:
}}}
so, if I'm reading it correctly, useradd seems to have invented a group,
given it the user's name, and made it the user's primary group. Yes,
here's a cleaner example
{{{
root in chroot /# useradd third
root in chroot /# grep third /etc/passwd
third:x:1002:1002::/home/third:/bin/bash
root in chroot /# grep third /etc/group
third:x:1002:
}}}
This is the expected behaviour for distros that put each user in their own
group - from memory, all the rh-derived distros, not sure about debian-
derived.
--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2144#comment:8>
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