Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
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.
Changing ownership of a file is a standard function available in Linux - chown command
Yeah, but in Linux it is mostly not allowed to "give away" files, unless you got special privileges. From the man page of chown(2)
Code:
Only a privileged process (Linux: one with the CAP_CHOWN capability) may change the
owner of a file. The owner of a file may change the group of the file to any group of
which that owner is a member. A privileged process (Linux: with CAP_CHOWN) may change
the group arbitrarily.
This, of course, also applies to the chown(1) command. So a "normal" user (or program) cannot chown a file to root.
Changing ownership of a file is a standard function available in Linux - chown command
If you do not know why you would need it, you probably don't need to use it
It is possible that improper use of this command can damage the OS and make it unbootable,
But changing file ownership isn't going to brick hardware
Linux freedom cannot prevent improper usage, that is a user responsibility
Thank you for the explanation. I experienced it damaging the O.S. where it wouldn't boot because there is a cross connection in Thunar between "Open Thunar root here" and that destructive option in Thunar. I had to re-install MX-Linux to un-brick it. When selecting "Open Thunar root here" doesn't always Open Thunar root here. I removed that destructive feature.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.