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.
Hi, I have Slackware64 13.37 and I install NetworkManager from Slackbuilds.
The only problem is that I have to run rc.networkmanager when I do startx to see the applet running.
I have used wicd for the last few years - but I'm planning on going with NetworkManager for the new rebuild of my laptop (with 13.37). I don't think wicd is practically supported anymore - there's hardly any movement at the home site. Also, Robbie Workman (who put wicd into Slackware anyway) appears to be pushing NetworkManager. That settled it for me.
Look for the spot in /etc/rc.d/rc.M where wicd is started and add the call to rc.networkmanager there.
NetworkManager is very nice and there are plugins for connecting to vpns etc. I would go with putting the startup line in rc.local though, to avoid it being lost if rc.M is overwritten on an upgrade.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,096
Rep:
Quote:
Originally Posted by rg3
If rc.networkmanager resides in /etc/rc.d, make sure it's executable and launch it from /etc/rc.d/rc.local like:
Code:
/etc/rc.d/rc.networkmanager start
I've tried that, twice, and both times it hung up the computer; couldn't even log on.
If started in a terminal, as root, and use the applet as user, it works, but not if the daemon is started on boot up.
I've tried that, twice, and both times it hung up the computer; couldn't even log on.
If started in a terminal, as root, and use the applet as user, it works, but not if the daemon is started on boot up.
This works:
/etc/rc.d/rc.local:
Code:
#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local startup commands in here. Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.
# To disable networkmanager, chmod rc.networkmanager to 644
if [ -x /etc/rc.d/rc.networkmanager ]; then
. /etc/rc.d/rc.networkmanager start
fi
/etc/rc.d/rc.local_shutdown:
Code:
#!/bin/sh
# To disable networkmanager shutdown, chmod rc.networkmanager to 644
if [ -x /etc/rc.d/rc.networkmanager ]; then
. /etc/rc.d/rc.networkmanager stop
fi
I've tried that, twice, and both times it hung up the computer; couldn't even log on.
If started in a terminal, as root, and use the applet as user, it works, but not if the daemon is started on boot up.
This is odd. At what point does it hang? Did you disable wicd?
BTW, if you want help on this you may want to start a new thread as this thread is marked solved.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.