Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
View Poll Results: wicd or networkmanager?
|
wicd
|
  
|
75 |
50.68% |
networkmanager
|
  
|
81 |
54.73% |
 |
|
04-20-2013, 09:06 AM
|
#16
|
LQ Veteran
Registered: Feb 2007
Distribution: Slackware64-current with KDE4Town.
Posts: 9,782
|
I've used both and if wicd it didn't have a 'refresh' button it would be completely worthless. NM, on the other hand, seems to do a better job of making the connection and hanging on to it.
|
|
|
04-20-2013, 09:41 AM
|
#17
|
Guru
Registered: Mar 2004
Location: Canada
Distribution: Slackware, Void, VM: Debian, Arch
Posts: 7,508
|
I've used both. I'm using wicd on my slackware-current acer netbook. I prefer wicd; it does what I need it to do.
|
|
|
04-20-2013, 10:16 AM
|
#18
|
LQ 5k Club
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,575
|
For my comparison of NetworkManager and wicd, see here http://www.linuxquestions.org/questi...0/#post4803085
Due to USB modem support and automatic reconnection, I am using NetworkManager in preference to wicd on my netbook.
|
|
1 members found this post helpful.
|
04-20-2013, 10:39 AM
|
#19
|
Member
Registered: Aug 2009
Location: /Universe/Earth/India/Pune
Distribution: Slackware64 -Current
Posts: 890
Rep: 
|
I use both. Network-manager for personal 3G USB dongle and wicd for the wi-fi.
Regards.
|
|
|
04-20-2013, 10:46 AM
|
#20
|
Senior Member
Registered: May 2004
Location: Belgium
Distribution: Debian, Slackware, Fedora
Posts: 1,466
|
Quote:
Originally Posted by onebuck
I use 'wicd' via 'wicd-curses' when on console'cli'
|
Thanks.
Didn't know it had ncurses interface.
I mostly use NM since Wicd doesn't support everything in my home network.
Last edited by jens; 04-20-2013 at 10:48 AM.
|
|
|
04-20-2013, 11:57 AM
|
#21
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,418
Rep: 
|
Now that netconfig proposes NetworkManager, I use it (on my laptop, with Fluxbox.)
At first reboot after installation:
(1) I am automatically connected by wire, if available
(2) I just have just to run once nm-applet to get the widget on the tray after installation.
Then getting a wireless connection is just a left-click away, plus possibly typing the password the first time when demanded.
It could hardly be simpler to use IMO.
|
|
|
04-20-2013, 03:03 PM
|
#22
|
Senior Member
Registered: Oct 2003
Location: WA
Distribution: Slackware
Posts: 1,286
|
Wicd
Maybe its just my weird old laptops (Compaq and Dell), but NM has one hell of a time switching back to wired from wireless; wired TO wireless is fine, but the reverse requires more button clicks than I care for. For systems without wifi, I disable NM: easier to just edit the appropriate files in /etc/rc.d
|
|
|
04-20-2013, 03:18 PM
|
#23
|
Member
Registered: Jan 2011
Location: Czech Republic
Distribution: Slackware, Gentoo, FreeBSD
Posts: 176
Rep:
|
I use both. Each has it's own glitches, but I get used to "wicd way" so now I find NetworkManager's applet the weird one  Although I'm pretty sure anyone coming from NetworkManager to Wicd will feel the same about wicd.
I use networkmanager for VPN and wicd for everything else.
So far wicd always worked flawless, while networkmanager sometimes acts weird (can connect to wired network but didn't even try to connect to wireless network, although it connected fine just few minutes ago). Besides, wicd doesn't intentionally hide informations (like complete list of available wifi AP's, so I can choose AP if it operates on both 2.4 GHz and 5 GHz band) to simplify GUI. Which I find as advantage, but someone else could take it as disadvantage. It's matter of preferences.
Last edited by yenn; 04-20-2013 at 03:20 PM.
|
|
|
04-21-2013, 09:38 AM
|
#24
|
Member
Registered: Jun 2012
Posts: 78
Rep: 
|
Neither. Wired eth0 here. 
|
|
|
04-21-2013, 09:18 PM
|
#25
|
Member
Registered: Feb 2013
Location: Sydney
Distribution: slackware
Posts: 110
Rep:
|
At one point (maybe fixed now?) wicd had a bug that meant automatic wifi reconnections sometimes didn't work (maybe after reawakening from hibernation?). I remember I had to actually restart for the connection to be accepted with the stored credentials.
Since NetworkManager appeared I have used it for my laptop and this problem has not occurred.
Michael
|
|
|
04-21-2013, 09:27 PM
|
#26
|
Moderator
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian, EndeavourOS, OpenSUSE, KDE Neon
Posts: 4,031
|
I can't get NM to connect automatically on boot if X isn't running, so it's no choice for me, Wicd.
|
|
|
04-22-2013, 01:10 AM
|
#27
|
Member
Registered: May 2004
Distribution: Slackware
Posts: 76
Rep:
|
I use wicd, with the dhcpcd backend. The dhclient backend changes my computer's hostname without my permission, which (aside from being rude) wreaks havoc on the desktop session.
I like that Wicd gives me more options and easier access to configuration. The interface is a little sluggish (it likes to refresh a lot?), but I find it works better for me than NM. NM didn't always play nicely with a multi-user setup and kept forgetting passwords in a way that made no sense to me. Wicd works fine, so long as I don't use the dhclient backend :P
Last edited by josiah; 04-22-2013 at 01:11 AM.
|
|
|
04-22-2013, 08:11 AM
|
#28
|
Senior Member
Registered: Dec 2008
Posts: 1,213
|
Quote:
Originally Posted by vdemuth
I use both depending on circumstances. Mostly to do with 3G dongles being recognised and usable with NM. But on the whole, it seems that Wicd is just more stable and reliable.
A PITA having to swap about, so the sooner Wicd gets 3G support the sooner I can ditch Nm.
|
I switched to NetworkManager for the same reason but soon found NetworkManager forces me to accept too many things. e.g. It forces me to let it manager my ethX while in wicd I can disable this. NetworkManager also disallows the use of "/etc/resolv.conf.{head,tail}".
After quite some struggles, I had to switch back to wicd+blueman. Blueman also gives more stable 3G modem connection than NetworkNamager does.
|
|
|
04-30-2013, 09:28 PM
|
#29
|
Member
Registered: Sep 2009
Location: Perth, W.A.
Distribution: Slackware, Debian, Gentoo, FreeBSD, OpenBSD
Posts: 208
Rep:
|
I dislike both of them because of bloat, so I use wpa_supplicant and hand edit its config as needed.
If I had to choose, it would be wicd, but I very much dislike its design decisions. I mean, c'mon, it expects me to run a full Python interpreter as a daemon? Along with a bunch of third-party libraries. And as root? WT...?
It's been on my To-do list for ages: write a simple wireless manager in C that would interface with iwlist and iwconfig or iw to bring up and close down wireless connections. It would automatically remember certain APs and would offer to connect when one comes in range, all user configurable.
I think it is something that is really lacking in Slackware land at the moment, especially for those of us who don't use a Desktop and have no concept of a systray or applets.
|
|
1 members found this post helpful.
|
05-01-2013, 12:11 AM
|
#30
|
Senior Member
Registered: Sep 2004
Distribution: slackware
Posts: 4,927
|
Quote:
Originally Posted by joncr
Neither. Wired eth0 here. 
|
Yessirree! Same on the desktop.
On the laptop, however, I use NetworkManager because it is the default in KDE and works very well out of the box. It has been a solid performer for me.
It wasn't that long ago that the kernel didn't have many wireless drivers built in. I had a wireless card which used an Atheros chipset. Had to download the Madwifi drivers and compile them, as well as wpa_supplicant which wasn't a stock Slackware package. Things have certainly come a long way since 2004!
|
|
|
All times are GMT -5. The time now is 07:50 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|