Talk:HOWTO Supermount

From Gentoo Linux Wiki

[edit] Supermount

I read the forum that this came from, and, I think there all valid points. But when it comes down to it, there is nothing that does the job the *right* way. I think the best way to get the most out of, either autofs, or ivman, or supermount.. How about ppl share what they think is wrong with each one. and try and help development for them. I prefer supermount, mainly because it is, so simple to add a fstab entry, its in the kernel, and because its ONE *thing*. :) I havent had any problems with it, have you?

mikeyb

You said it yourself, because its in the kernel. The more you put in the kernel, the harder it becomes to maintain, and also adds risk for unnessary instability, especially when there is a solution that exists in user-space-land. I can't remember if it was supermount or submount that increased the risk for unnessisary drive locking, as well. Basically, it comes down to: if you want to add it to your own kernel, great, but it will probably never be officially supported, and long term is a bad idea (even though right now it is the easiest). MighMoS 21:03, 9 May 2005 (GMT)

Steelneck

I have just ben thinking around this the last couple of days (26 Nov 2005). Supermount has two issues as i see it. 1) Mountpoints are static and does not get created on the basis of the hw or volume in question. 2)One has to hunt around for new, hopefully working kenel patches for every new kernel version, and of course patch and compile the kernel.. What i like to do is to automaticly crate a mountpoint named after the HW-type (mass-storage/CD/DVD/Floppy .. ) or its volume name if present, then adjust the mountpoint in fstab and let supermount do the rest. But i do not know how to do it. But i am searching....

Pastychomper

I think the problem with userspace alternatives is that the drive itself isn't in userspace. It's there as part of the hardware for as long as it's connected, so it might as well be treated as such - mount it once it's available, and unmount it when it's removed. Supermount does this regardless of whether a user is logged in, using the console, or running KDE (for example), and I've yet to find a userspace alternative that works as well.