Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
|
03-15-2014, 02:28 PM
|
#1
|
Senior Member
Registered: Jan 2008
Distribution: Arch/Manjaro, might try Slackware again
Posts: 1,859
|
Write bits inexplicable changed in /home
Here's a puzzle:
All my files in my home directory somehow suddenly lost their w attribute, ie became ro. The execute and read bits were not affected, and the filesystem was still mounted rw. They looked like -rw-r--r-- I was not running X as root, never do. The user and group ownership were unchanged.
I was running KDE and first noticed it when I tried downloading a file and could only copy it to my Desktop, not my downloads in /home/me. I also had an open file in Kwrite which couldn't save. I had removed lesstif and added openMotif. Root's account seems to be the same, but I'm not sure the permissions weren't always that way.
I shutdown, ran fsck from init 1, looked at smartctl and there were no errors. Of course I couldn't run init 4 or startx from init 3, because no .Xauthority could be written, nor any .serverauthority.
So I typed chmod a+w *, and everything seems to be ok again.
BUT:
What could account for that, and what else might have been affected?
Last edited by mostlyharmless; 03-15-2014 at 02:30 PM.
|
|
|
03-15-2014, 05:07 PM
|
#2
|
Senior Member
Registered: Feb 2011
Location: Massachusetts, USA
Distribution: Fedora
Posts: 4,258
|
-rw-r--r-- means owner may read/write, group and others may only read. So I think they were in the correct state. This is the normal permissions on files in the home directory.
|
|
|
03-15-2014, 07:21 PM
|
#3
|
Senior Member
Registered: Jan 2008
Distribution: Arch/Manjaro, might try Slackware again
Posts: 1,859
Original Poster
|
Perhaps, but I couldn't write to them. I see that I can no longer run Crossover either; is the ownership of /home/me supposed to be me and users or is it supposed to be root and root?
|
|
|
03-15-2014, 07:41 PM
|
#4
|
Moderator
Registered: Oct 2008
Distribution: Slackware [64]-X.{0|1|2|37|-current} ::12<=X<=15, FreeBSD_12{.0|.1}
Posts: 6,311
|
It should be me and users.
BUT - your case is not clear to me from your posts, the execute bit MUST be set on all those directories and sub directories. - That is, whereas files should be rwxr--r-- in the user home by default, sub directories should be rwxr-xr-x by default.
Last edited by astrogeek; 03-15-2014 at 07:55 PM.
|
|
|
03-16-2014, 12:11 AM
|
#5
|
Senior Member
Registered: Jan 2008
Distribution: Arch/Manjaro, might try Slackware again
Posts: 1,859
Original Poster
|
Hmm, so then the directory ownership got changed. Interesting, thanks.
|
|
|
All times are GMT -5. The time now is 10:10 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|