SlackwareThis Forum is for the discussion of Slackware Linux.
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 searched a little in the forums and most of the solutions were similar,in order to change ownership :
chown -R username.groupname /path/to/files
but why the hell does it need to change ownership uid to 500 i think 0 is root, right? and root is the only user on the system. can anyone give a hand here please, i have tar packages that i need to install and i am stuck with this . thanks in advance
I found an article that talks about my problem, but thats way too extensive and complicated for me( i copie it tough, for later maybe).
I remember about setuid and stuff but i dont really know what to do, can anyone help here, please?
because you should not be running as root. Root is only used in certain rare instances (installing programs, configuration). Running as root will eventually allow you to make mistakes that mess up your box. perhaps that is what has happened now. Also some apps will not run for root for security reasons.
I know it has been a long time, but this thread appears at the top of the Google search so this may help someone.
When extracting with tar, the default for the root user is that tar attempts to retain the owner:group of the files originally stored in the tar.
When transferring tar files across systems, this may cause problem if the same user does not exist in the target machine.
Using the option --no-same-owner will force tar to extract the files and assign them root as owner.
The error does not appear when extracting with a normal user because in that case the default option is --no-same-owner.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.