Wireless network management - wicd removed from Slackware -current
Slackware - ARMThis forum is for the discussion of Slackware ARM.
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.
Wireless network management - wicd removed from Slackware -current
Although it's still in SlackwareARM, for the moment at least.
Interesting news and seems a shame to me. I used wicd at first on my RPI4, and found it simple and nicely usable in both GUI and CLI, although in playing with my RPi, I ended up trying NetworkManager and just stuck with it.
Exaga, something to consider for an update or rewrite of the Sarpi site's mini project "Setting up a wireless network connection." Which, BTW, is fantastic. I don't think I would have worked out how to set up wireless connection via wicd without it, and I learned some useful things in the process.
TKS
From the changelog:
Sat Aug 1 19:08:49 UTC 2020
extra/wicd/wicd-1.7.4-x86_64-3.txz: Removed.
This is unmaintained, possibly insecure, and doesn't work with Python versions newer than 2.7.18. NetworkManager is a better choice these days.
Sorry to see wicd go. It was always my preference although I have on occasion also used nm as recently as three or four months ago on an old acer netbook where I couldn't get wicd set up. PV's reasoning for removal is sound and what I would expect if I was smart enough to expect PV to do anything.
Exaga, something to consider for an update or rewrite of the Sarpi site's mini project "Setting up a wireless network connection." Which, BTW, is fantastic. I don't think I would have worked out how to set up wireless connection via wicd without it, and I learned some useful things in the process.
From the changelog:
Sat Aug 1 19:08:49 UTC 2020
extra/wicd/wicd-1.7.4-x86_64-3.txz: Removed.
This is unmaintained, possibly insecure, and doesn't work with Python versions newer than 2.7.18. NetworkManager is a better choice these days.
Thanks TKS. I've added your request for a rewrite of the mini project in question to the to-do list. It makes good sense to implement what you're suggesting if we're going to lose wicd-cli and wicd-curses. What you've quoted is from the Slackware 32/64-bit Changelog but it's only a matter of time before that's reflected in Slackware ARM.
I appreciated I could try wicd. I use a municipal free wifi that has an antenna about 100 feet from the house. My analysis was that wicd only worked if the NetworkManager was running! But the main problem with wicd, I think, is that it is using dhcpcd all wrong. Notice the ps axw output for dhcpcd. NetworkManager keeps dhcpcd listening until the connection drops and then it brings the link down. Wicd also sends dhcpcd to do some connecting but without the parms that would make dhcpcd stick around and keep listening and notify us when the link goes down.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.