Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
Seems like I have problems with starting up Gnome because of the permissions on /dev/audio. Maybe that's not the main problem - but seems like what's happening isn't right:
chmod 666 /dev/audio
It sets the permissions to:
crw-rw-rw-
After 1/2/3 reboots it sweeches back to
crw-------
Why? I'm pretty new to Linux, but I think that this shouldn't happen.
I'm not sure of why it happens, but maybe you could put chmod 666 /dev/audio in your startup rc file.. it isn't a good fix, but it will solve the problems somewhat.
(Also, did you make sure to change the permissions while in root? not "su" but "su -")
I'm somewhat new to linux so I hope this helped, if not...
Is /dev/audio a symlink or is it created by devFS? Probably. the chmod command should work as long as it's in your rc.local file which will be executed long after DevFS has created your device(s). To find if it's a symlink to the actual device:
ls -l /dev/audio
If it is a symlink, apply the chmod perms to the actual device.
Thanks for the replays.
Where is this rc file that I should change?
And since I'm pretty new to Linux - I don't know what is "devFS".
The /dev/audio is not a symlink.
DevFS is something that creates your devices during boot. The old way was to create MANY (just about anything I've ever needed) during the initial install. DevFS has quite a few advantages, good stuff I think.
On my Mandrake system, rc.local is in /etc/rc.d and there is also a symlink in /etc/rc.local for it. In there you would just enter the lines:
chmod 666 /dev/audio
And that's it. On subsequent reboots this should chmod that device at the end of the bootup process.
Ok, thanks - I'll see if it's working (since my problem appears after a few reboots).
Now, when I started Linux in text mode - I noteced one thing. I didn't notice it before since it was all working well, but now I saw that it says something like this:
Failed to start devfs deamon: something something file .devfs is missing etc.
I never get the time to see it entirely... But I don't see this error at all when I start Linux in graphical mode...
Wierd that I saw it just now when you told me about it...
Do you know what might be a problem?
Thanks for your help so far...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.