robert’s rant room

Don’t use them. Or review the results before clicking “Send”. (via hadess)

Old news for those who follow commits and bugs, but last week KNetworkManager hit the portage tree after living in the Gentopia overlay for a while.

Why did it take so long?

I know Gentoo is one of the last distros to feature this. One reason this took so long is that I learned about it quite late (a friend of mine switched to Debian because Gentoo didn’t have it). Also, it was my intent to enable VPN support in KNM before committing it. As the KNM is a GUI for the famous NetworkManager, it only can do what NM features. VPN support in KNM thus depends on VPN support in NM itself.

NetworkManager releases

Here’s where the problems begin: The NetworkManager moved its homepage over to gnome.org, and lost its VPN releases on the way. Compiling the VPN plugins from SVN didn’t work with the latest release (even from releases’s branch). Also, I don’t understand their release policy. They got some work done in the stable branch all the time. Every distro is shipping snapshots of it, but we didn’t see a release for almost a year. So what changed for Gentoo?

• We have a (hopefully) working snapshot of net-misc/networkmanager, called 0.6.5_p20070823.
• We have a KDE GUI for it, called kde-misc/knetworkmanager-0.2 (hey, an actual release)
• We have three VPN plugins: net-misc/networkmanager-{pptp,vpnc,openvpn}. Read on if you’re interested in them.

What does which package give me?

Basically, the packages in net-misc/networkmanager only feature command line tools that do the background work. You can install them in two ways:

• If you need GNOME support, enable the gnome use flag for any/all of them. That also installs gnome-extra/nm-applet for you.
• If you need KDE support, install kde-misc/knetworkmanager and enable the VPN use flags you need.

Be sure to add the packages to your package.keywords so you can install them on a stable system.

WLAN Support

Ok, this is the great part! Configure your wireless network via a GUI. No more editing weird config files once you move your laptop, no iwlist. Just select the network you want and get on with it! KNM can even store your keys to your KDE wallet. Any user may change the internet connection without root privileges when he or she is in the plugdev group.

VPN Support

The VPN plugins are SVN snapshots of the stable branch. The pptp plugin is currently p.masked because its GNOME gui segfaults on amd64. This bug was obviously fixed in the trunk, but the trunk code is not usable with stable versions of (K)NetworkManager. I’ll have a closer look at this later. The other plugins seem to work, but I couldn’t do extensive tests yet (where’s my vpnc password?). Please report failures to me on our Bugzilla. When reporting, be sure to attach the relevant parts of your syslog (”grep Network /var/log/messages“) or start NetworkManager in non-daemon mode (”NetworkManager --no-daemon“). If you succeed on using them, please leave a report here.

Acknowledgements

Thanks to Steev for the maintaining the ebuilds of NetworkManager itself and testing!

Writing a bug report is a hard thing to do. I know. Fortunately, there’s some easy rules to follow when you want to get it fixed and fast! To ease your understanding, I will illustrate them with some real-life examples:

1. Scream. It’s so easy to write upper-case (thanks for caps lock!). And for most people, they’re much easier to read. They’re stupid anyway, so they’re probably used to being screamed at. So start with a nice “OH MY GOD. What went through your head when you did this?”, then go on explaining your problem: “gcc is FUCKING SLOW”.
2. Annoy. If possible, mark the bug with highest priority and severity. You filed it, so you decide on how important it is for others! After you expounded your problems that verbosely, say something personal. This helps: “You should be ashamed of yourself.”
3. Show that you’re annoyed. There’s quite some ways to do that. Use your fantasy, remember how you did that when you were a child. “Even Apple and Microsoft would be ashamed of fucking up this badly.” or “What a great distro you have there. Debian would be proud of you.”
4. When people ask questions, insult them. Really, they shouldn’t try to reproduce the bug anyway. Why would they want to have the bug themselves, instead of just fixing it! “I’ll give you personally ten bucks if this helps you debug the issue. … I dare you to tell me how the emerge –info helps you. Do it publicly, please, so the humiliation is greater. “
5. Threaten. If not everyone will know how important your bug is to you until here, you should make that clear again: “But apparently Gentoo is not interested in fixing bugs. … Don’t bother. I’ll switch distros.”
6. Propose bad solutions. This is actually hard. You have to distinguish your solution from the way it is right now (”This whole construct is braindead.”) Remember not to ask or think about the reasons why it’s the way it is right now.
7. Point fingers. “This is so unbelievable that I will blog about it, too.”

Sadly for the example, following these steps didn’t fix the bug. Another report did.

Finally, I joined those great masters and friends and conquer the web with my new and shiny blog.

Let’s see if I get this all working.