Ok so you’re trying to use Linux in a networking environment as a desktop PC. So you’ve got that work share mounted off the file server. You’re working away with OpenOffice 2.1 and after 5 minutes of work it comes up and bails with some error about being unable to save.
Now, you’re no newbie to Linux, and you know it’s a remote share, so you check the permissions first. They look ok when you do an ls -la, your UID is the owner. You think the problem might lie with the file, so you copy it locally, and saving works fine. You check your /etc/fstab, and the remote share is an SSHFS over the FUSE driver. Looks like the mapping to the file system is broken for some applications. Now you know the file server is exporting over NFS also, so you think, maybe that will work since it’s legacy. So you mount that, and it doesn’t work because your IP is not permitted because the DHCP gave you the wrong IP. So you drop to the command line and do an ifconfig on the device to get the right IP and it’s sweet. NFS mounted. And it works with saving files.
Unfortnately, OpenOffice crashes on you. It restarts ok. You go to unmount the SSHFS file system since you’re not using it, only to find it won’t unmount because it’s “busy”. Oh yeah, OpenOffice. You close it but it’s still “busy” when you try to unmount it. Nothing else is open. You check the process listing and there isn’t anything that should be accessing that file system unless…yep, OpenOffice forgot to unhook a file handler. So you do an unmount -l so that it umounts properly in the background, and start using Abiword instead. Now you go to open your files, and Abiword is nice and remembers where the last file was opened from – the SSHFS mounted drive. It tries to open that, but that is unmounted, but not properly…so Abiword hangs. And since GNOME is using fancy pop-up windows, you can’t actually put anything in front of Abiword. So now half your desktop is taken up with a program that is waiting to timeout. The only way you know to fix it is to reboot.
So sure, Linux is ready for the desktop…if you want it to be like Windows (i.e. things still break). But Linux is easier to fix right? Sure. But when I’m using it as a desktop, I want to be using it for productivity…not
messing with the system to make sure my “stable” opensource app doesn’t crash because the filesystem breaks! Come on, just give me an error instead of a 300000 minute timeout!