old school unix philosophy is focused on multiuser mainframes. For this reason, the more basic utilities such as 'adduser' do not create a group for a new user.
All users are part of the "users" group. For desktop system that emulate the way mac and windows handle file ownership, the user creation tool will create a group named after the user, specific to that user. DESKTOP distros (like ubuntu) do things a little bit differently. It's an odd quirk between server and desktop use cases. So in general, a linux desktop utility that creates users will 1) create user rsteff 2) create group named after new user (rsteff) 3) add rsteff to group rsteff 4) assign rsteff the next available UID after 1000 (first user is UID 1000) That is how most graphical user management tools do it. On Slackware people get opinionated about which tool you should use, so I'll just lay out the options for creating a new user. adduser: command line utility that creates a user, profile, and adds groups for basic functionality - DOES NOT create a dedicated group for that user. - defaults to next available UID KUser: graphical tool in KDE for user management. Can create, delete, and modify user accounts in a graphical interface. This interface provides very similar functionality to the gnome user management in Ubuntu. - DOES create a dedicated group for that user (for user rsteff, group rsteff is automatically created and user rsteff added to it) - User ID's start at 1000, and climb from there. Contrary to popular belief, there is no correct way to define user groups and ID's. Pick a tool and stick with it, the only mistake would be to randomly bounce from one tool to the next. Personally, I use KUser. I like having my user IDs start at 1000 and having a group for each user makes things simpler when interacting with other distros. On Sun, Jan 6, 2019 at 9:09 AM Dick Steffens <[email protected]> wrote: > (Stuff from old "Can't kill process" thread) > > I wrote: > > > On ENU-1, my Ubuntu 18 machine, when I run groups, I see that my user, > > dick, has a group: > > > > dick@ENU-1:~$ groups > > dick adm cdrom sudo dip plugdev lpadmin sambashare vboxusers > > dick@ENU-1:~$ > > > > Somehow I don't have one on ENU-2, the Slackware machine, for rsteff. > > Ed replied: > > > if you created user 'rsteff' via the "adduser" command, the groups > > assigned (if you choose the full default) to that user will be: > > > > users lp floppy audio video cdrom games plugdev power netdev scanner > > > > group 'rsteff' is not created. You can do so and then use that group to > > hide $HOME from other users that may log in. > > On ENU-2, the Slackware machine, I have the following: > > rsteff@ENU-2:~$ groups > users lp floppy audio video cdrom plugdev power netdev scanner > rsteff@ENU-2:~$ > > When I try to change ownership on a file I've always used > > root@ENU-2:/home/rsteff/Desktop# chown rsteff:rsteff hardware.html > chown: invalid group: 'rsteff:rsteff' > root@ENU-2:/home/rsteff/Desktop# > > That's what I've always done before. Since it was what I was used to I > didn't think to look a ls -l. I finally thought to do that this morning > and I find: > > rsteff@ENU-2:~$ ls -l > total 32 > drwxr-xr-x 2 rsteff users 4096 Jan 4 14:14 Desktop/ > ... > > Is that something that's different between Slackware and Ubuntu? Should > I always expect ownership of files rsteff creates to be rsteff:users? > > > -- > Regards, > > Dick Steffens > > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
