netcfg2 disappointment
For netcfg2, I made lots of it’s guts reusable. I hoped that people would take it and develop it further, making separate auto-connect scripts and things. netcfg2 was meant to be a foundation for people to work with. Just source functions from /usr/lib/network/ and use them.
And it’s cool. You can do useful things with those functions. My ~/.xinitrc starts up different applications depending on what network I connect to. Or you could write a really good detection/automatic script.
That kinda didn’t happen. I don’t think I’ve seen a single third party script. Slightly my fault, I should have advertised it better, though I’m surprised nonetheless.
netcfg2 wasn’t mean to be the automatic network magic tool either. I probably didn’t do myself any favours including the auto-wireless and EXCLUSIVE= hacks though.
I’ll release another netcfg 2.0.x bugfix, and netcfg 2.1. After that the work will be on netcfg3 which will remedy netcfg 2.0’s flaws and bring it up to date with current standards. More on that another time…
not! I had a look at it, and it’s on my todo list.
lloeki
May 20, 2008 at 6:43 pm
Don’t be disappointed, you merely made a tool that already fits the need of most Arch users perfectly.
glen
March 5, 2009 at 2:02 am