Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I don'tknow if it is the correct category to post this post, but what is the difference between newgrp command and role? Does it differ or not?
For example, in a System V-based UNIX system, in which a process can have exactly one group identity, and in order to change groups users must execute the newgrp command.
Do these groups differ from roles?
does my question make sense?
It sets the processes group id - which in most systems is irrelevent. All groups are available.
Groups are defined as collections of users, group access is granted to files based on the file group.
Normally, (see getgroups/setgroups) all groups are in the process access list. A process may access a file if the file belongs to the user (the owner of the file), or if the file group identifier match on of the groups in the users group list. That access is still limited by the corresponding permissions flags on the file.
Groups HAVE been overloaded with some "role" definitions - but these are only overloaded, and not a good use of groups. The use of a group as a role was supported by the set group id flag, AND by utilities like sudo - where a group name also matches a security control. It assumes that the group name is NOT used for files... but once a user is in the group, that user can then apply the group to a file, even if it isn't what the group was for.
This overloaded use worked where systems did not support true "roles". The overloaded use was just a workaround.
Linux has true role definition - supported by SELinux models, and can be applied to files, users, and or processes.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.