Pisses me off how more things these days in our trusted "lil OS that could" are automatically done for you in order to make you more efficient. As it turns out, many of these things make me LESS efficient, and cause me to break things near my computer. And I'm quite certain that my computer is quite tired of me slapping it on it's face (monitor) for automatically doing something I don't want it to do.
For example, I copy a lot of my family movies that my Dad is now converting to DVD. Seems pretty straightforward, right? Start k3b, and let it Copy DVD, right? No.
Because I'm running Gnome, and fucking nautilus, automount, kd3init, and k3b are all competing for the same resource (/dev/hdd), I have to sit on my thumb for 30+ seconds until one of the asshat daemons decides to give up the buttplug it's rammed up the kernel's ass so that the rest of the deadlocked processes can unwedge themselves. Only then will k3b start copying. But we're not finished! Oh no, not by a long shot. When I'm finished sucking in a disk image, I have to wait for k3b to clean itself up. I don't know what this means other than k3b has to disassociate itself with the kde session it has established. To this day, I'd like to know who DCOP is, and why the hell he won't give up the goods when I want to start/stop k3b.
If I am fortunate enough to be able to exit the k3b process I started in an xterm, I face an insurmountable challenge the next time I want to run k3b. k3b (possibly through kdeinit) leaves some kind of droppings (in the form of defunct processes) that dont' allow me to run k3b again without rebooting my machine. Does this sound like Windows 3.1?
Other times, I can't even exit k3b. I can't Ctrl-C the process. I can't "Force the application to quit" (I love that - as if my "kill -9" shell commands were not forceful enough. But gnome is going to magically "force the application to quit". Possibly through some kind of jedi/vulcan hybrid mindmeld). If I do, it just leaves the window on the screen and it never refreshes itself. GIVE ME BACK MY "kill -9"!
Let's look at other applications that try to do things "automatically" to help you.
How about gtkpod? You can ask gtkpod to manage the ipod device for you (this presumably means mount and umount it). However, if you ask gtkpod to do this, you'll wedge your system in such a way that you'll get "Read-only filesystem" on just certain files on your ipod (not all files mind you. The key noun in the previous error message is "filesystem". Nowhere does it say "file". Asshats). Also, gtkpod will try to mount the filesystem using root privileges, which means that a regular user can't read/write to it! How assinine! It's so much better to simply tell gtkpod *where* the ipod is mounted, and then mount it yourself.
Now onto kudzu.
After adding the "user" option to
It turns out that kudzu fucks up your
This brings me to my last "automatic" gripe: NFS. Why is it that anytime an NFS server becomes temporarily unavailable that every process goes tits up and becomes unresponsive?! Why does my Firefox process care that my
I just wish that Linux could be more forgiving when unexpected situations occur. I just had to reboot 3 times in order to unwedge my ipod. I feel like I'm running Windows 3.x, and it's making me want to change OSes.