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 have not. Though I have a couple of minor install issues, this is my first hitch in regular operation. New Slackware user here, though I'm not new to Linux.
So. I will chmod .xinitrc-backup and .xinitrc to read and write permission for my user and see if that takes care of it.
Thanks for the reply, Karimo.
Last edited by AtomicAmish; 09-06-2007 at 09:04 AM.
Permissions for both .xinitrc and .xinitrc-backup have been changed to 0755 and there is no improvement. The same error messages are given at exit from xwmconfig, and startx times out and doesn't start X.
Permissions for both .xinitrc and .xinitrc-backup have been changed to 0755 and there is no improvement. The same error messages are given at exit from xwmconfig, and startx times out and doesn't start X.
as root run:
chown username /home/username
chmod 0700 /home/username
That makes sense, of course, but the two affected files were owned by the user. So I don't see why they were giving permissions problems.
Anyway, thanks for the reply.
Sometimes permissions of directories are changed by scripts you run and do not understand well. Also when you copy files to a directory as root some permissions change. The issue is not quite clear to me too.
That makes sense, of course, but the two affected files were owned by the user. So I don't see why they were giving permissions problems.
Anyway, thanks for the reply.
Is not sufficient, sometimes, that the file is owned by the user.
For instance: a file owned by the user with permissions 400 can't be written or executed by the user.
Your .xinitrc files must have had permissions like 400 because, although owned by the user, the user itself couldn't write to that file (infact 400 means: r-- --- --- [Only reading permission only for the user]).
A little clearer now?
Besides, to be able to delete a file from a directory, you must have a write permission to that directory. To be able to cd to a directory, or to modify a file in a directory you have to have the executable perission, etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.