A few strange issues with Slack
 

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?

Barbara

/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..

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?

Barbara

well, you should not be able to change permissions on symlinks directly!!

symlinks "reflect" the permissions to whatever they point to.........

> 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.