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'm having a few strange things going on and not sure why.
To sync my Handspring visor and to run DVDs using xine, I need to su then chmod 777 /dev/pilot and /dev/dvd. They work fine. They work once, maybe twice, then I get error messages. I chmod again, then they work, once or twice... When I check the permissions, they haven't changed, it just doesn't seem to recognize them.
Second, I have a few entries in my /etc/rc.d/rc.local. It is set as 744 permissions. It runs webmin, my firewall and privoxy. However, it doesn't actually run those. There is a rc.privoxy in /etc/rc.d and it also has correct permissions, and if I run /etc/rc.d/rc.privoxy start, it works fine. Just won't start on bootup. What am I missing?
/dev/pilot and /dev/dvd are just symbolic links - in my case, to /dev/ttyUSB1 and /dev/hdc respectively. Check the file permissions of the actual device, rather than the link..
Last edited by oneandoneis2; 05-11-2004 at 11:43 AM.
oneandoneis2: Right, mine are the same, and the permissions are correct on those as well. I'm also wondering why if I re-chmod the symbolic links, they start working again?
> There is a rc.privoxy in /etc/rc.d and it also has correct permissions, and if I run
> /etc/rc.d/rc.privoxy start, it works fine. Just won't start on bootup. What am I missing?
This seems to be the way that slackware works. It doesn't run anything added to rc.d without explicitly telling it to run it. Just run your /etc/rc.d/rc.privoxy start from rc.local. That should do the trick.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.