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.
Using Slackware64-current.
Do I need these daemons if I'm not communicating in any way with any Apple computers? Are they necessary for anything else? How do I exorcise them? There's an appletalk module loaded too, in the generic kernel. Is the right way to get rid of that to run: modprobe -r appletalk?
I don't think you need them, maybe just blacklist them in '/etc/modprobe.d/blacklist' and also make sure they aren't being loaded by any script in '/etc/rc.d', but I don't think they are. For example comment out the 'netatalk' part in rc.M and 'modprobe appletalk' in rc.modules or rc.modules-$(uname -r) if they exist.
It's true that from the default install you can usually cut the boot time in half by disabling startup scripts, modifying rc.M, maybe using the lilo compact option, and recompiling the kernel. When I install sw 13 I'll make note of what can be done and post a howto.
You should remember that you have the choice when you are installing to select the desired services. 'rc.atalk' is one of the services that should be disabled if you don't have a need for 'apple talk'.
You can always re-run pkgtool then choose scripts to run and then choose the desired option for the service(s). Or in this case just do a 'chmod' from the cli.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Quote:
It mustn't have been activated by default before.
Yeah - I noticed on a recent VM install (think it was -current) that the appletalk stuff was coming up at boot up. I just thought I had inadvertently set this up in the setup script as I tend run setups on "autopilot" now. (Loosing my marbles a bit perhaps).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.