LXNM is not Debian-specific anymore
LXNM, the LXDE network manager, had Debian-specific scripts. That’s why I did not package it in Archlinux. As I said on my previous post, I worked on generic scripts, which use dhcpcd instead of dhclient (smaller, easier to control, DNS updates by default under Archlinux) and stop using ifup/ifdown. They are now in LXNM’s trunk. I’ll wait for a release to include lxnm in Archlinux, but the PKGBUILD with a rc.d script is ready.
Another thing: Did I mention LXDE’s lead developer is using Archlinux? Well, the wiki page about Archlinux was updated to mention the new lxde group even before I finished adding it to the packages :)
One last thing: git-svn rocks. I won’t use svn any longer. Using SVN branches still suck, or I missed something, which is highly possible.
Well, I lied, one last thing: I need to mention that I just started a fork of lxnm which doesn’t work as a daemon anymore. There are little chance that I ever finish. Default policy might be to use SUID with user root, group network, but I’d like to make it easy to use sudoers with NOPASSWD for “extra security” (that would need to adapt lxpanel a little more; anyway, I would have to). That makes installation harder so it won’t become the default behaviour. This sucks as I need to reset ENV.
I’m not ready to replace Steve Jobs…
2 Comments to “LXNM is not Debian-specific anymore”
Leave a Reply
I made a specific commit to be in the AUTHORS file. I suck.
I’d really like to see you get your hands on lxnm. I like the idea of LXDE, mostly for the whole idea of a “modular” DE (if not for the entire DE itself in vanilla form). The lxde guys have really written some nice programs to go with lightweight environments which, after using openbox for so long, I couldn’t get along without. A network manager would be an excellent edition.