Skip to contentSkip to conversation

Supermount

DISCUSSION Lasse Kärkkäinen / Tronic 7 participants 9 messages Jul 21, 2005 – Jul 24, 2005

lore
Share & tools
lore
#0 lore raw

Is there a reason why this magnificient piece of software is not already in the mainline? It seems to be working very well and provides functionality that simply isn't available otherwise.

For those who are not familiar with it: this system does on-demand mounting when the mount point is accessed and automatically umounts afterwards. Unlike autofs, this does not require a special automount filesystem to be mounted, but the actual filesystems can be directly mounted where-ever. Also, it "just works" and the CD drive will eject when the button is pressed, without having to wait for the umount timeout to pass. I haven't looked inside to find out HOW it actually does it, because I simply don't care, as long as it just works.

- Tronic -

#1 lore raw

Lasse Kärkkäinen / Tronic <[email protected]> :

Quoted 2 lines

Is there a reason why this magnificient piece of software is not already in the mainline?

Yes, there is. Please search the archives.

--
Ueimor

#2 lore raw
In reply to Lasse Kärkkäinen / Tronic
Quoted 5 lines

2005/7/21, Lasse Kärkkäinen / Tronic <[email protected]>:
Is there a reason why this magnificient piece of software is not already in the mainline? It seems to be working very well and provides functionality that simply isn't available otherwise.

Hi Tronic,

Supermount is obsolete there are other tools in userspace that do the job perfectly.
e.g ivman which uses hal and dbus.

Including source like supermount because it simply work is not a good argument. And why to hell should everthing in the kernel, to make sorry *leazy* people happy? The kernel is not a trash...also supermount uses ioctl which is nearly removed from kernel?! Please correct me if i am wrong with ioctl.

Also there are other fs like supermount e.g submount etc...

Quoted 8 lines

For those who are not familiar with it: this system does on-demand mounting when the mount point is accessed and automatically umounts afterwards. Unlike autofs, this does not require a special automount filesystem to be mounted, but the actual filesystems can be directly mounted where-ever. Also, it "just works" and the CD drive will eject when the button is pressed, without having to wait for the umount timeout to pass. I haven't looked inside to find out HOW it actually does it, because I simply don't care, as long as it just works.

I used supermount, too - for a long long time...but it cost me a second to write a bash script with does supermount job's for eject. ;-)

Quoted 5 lines

- Tronic -

Signature · 5 lines
Mit freundlichen Grüßen
Michael Thonke

Best regards
Michael thonke
#3 lore raw
Quoted 3 lines

Supermount is obsolete there are other tools in userspace that do the job perfectly.
e.g ivman which uses hal and dbus.

They cannot mount on demand, thus cannot do the same job. The boot partition, for example, is something that should only be mounted when required. The same obviously also goes for network filesystems in many cases (i.e. avoid having zillion idling connections to the server).

Quoted 1 line

Also there are other fs like supermount e.g submount etc...

I woudldn't care about the implementation (original supermount, supermountng, submount or something else). Getting the job done is what counts.

- Tronic -

#4 lore raw

Am Freitag, 22. Juli 2005 18:38 schrieb Lasse Kärkkäinen / Tronic:

Quoted 8 lines
Quoted 3 lines

Supermount is obsolete there are other tools in userspace that do the job perfectly.
e.g ivman which uses hal and dbus.

They cannot mount on demand, thus cannot do the same job. The boot partition, for example, is something that should only be mounted when required. The same obviously also goes for network filesystems in many cases (i.e. avoid having zillion idling connections to the server).

To mount on demand use autofs. Unmounting and dealing with media removal is the problem.

Regards
Oliver

#5 lore raw
Quoted 2 lines

To mount on demand use autofs. Unmounting and dealing with media removal is the problem.

Granted, that can get pretty close. However, having to use /auto/* instead of mounting directly where required often limits using it quite a bit. Thus, I don't see it as a real alternative.

- Tronic -

#6 lore raw
Quoted 6 lines · Lasse Kärkkäinen / Tronic
Quoted 2 lines

To mount on demand use autofs. Unmounting and dealing with media removal is the problem.

Granted, that can get pretty close. However, having to use /auto/* instead of mounting directly where required often limits using it quite a bit. Thus, I don't see it as a real alternative.

What do you mean "/auto/*"?

Ian

#7 lore raw
In reply to Oliver Neukum
Quoted 5 lines · Oliver Neukum

Am Freitag, 22. Juli 2005 18:38 schrieb Lasse Kärkkäinen / Tronic:

Quoted 4 lines
Quoted 3 lines

Supermount is obsolete there are other tools in userspace that do the job perfectly.
e.g ivman which uses hal and dbus.

Quoted 7 lines
Quoted 4 lines

They cannot mount on demand, thus cannot do the same job. The boot partition, for example, is something that should only be mounted when required. The same obviously also goes for network filesystems in many cases (i.e. avoid having zillion idling connections to the server).

To mount on demand use autofs. Unmounting and dealing with media removal is the problem.

That's not the only problem.
We can't do owner mounts of the floppy, for example.
smb mounts have similar problems in needing to identify the requester in order to get authentication info.

But that's on the agenda to be fixed.

Ian

#8 lore raw
In reply to Lasse Kärkkäinen / Tronic

well, for a bit of OT discussion sake, here's how it imho SHOULD work, from user (noobs and non guru) desktop point of view:
cd/dvds: mounted automatically on insert / first access. if a program is running from it (or a file is open from it), and user tries to eject it using button, or any eject-like software, kernel sends a signal to a central place. which is, for example, picked up from a window manager, or even X itself. which, in a friendly and non intrusive way, displays something like this: "drive hdc busy, please close the following processes first: 1. mplayer 2. blabla". also, if a blank media is detected on access, it should not be mounted.
usb drives: similar. if user plugs it out without unmounting, its unmounted, and processes using files on it gracefully killed, or somehow "warned". how to "warn" them? ill let someonbe smarter think of the way :) and about ripping it out without closing, wm/anything should yell "bad user!! you should ALWAYS unmount first!"
floppys: i suggest leaving things 100% same. btw. i saw some distros having problem with accessing ie /mnt/floppy when there is no floppy present. bash goes wild with autocompletion. programs pause for a looong time. this could be a kernel bug.
other stuff: dont want to sound like troll, but i guess 98% of people dont use anything else.
system partitions: make a clear cut between folders which should be seen at all by anyone but root, kernel, special software. in other words: reduce clutter in / by hiding almost anything! and partition specific mount option such as
"userinvisiblefolder=/dev;/sys;/lib;/proc;/sys;/var"
should also be possible. face it, for regular user in varoius distros, / is to crowded.
i'm not saying this is all 100% correct or possible. couse this is, imho, greatest ugliness, user friendlyness and productivity reducer in linux. m$ has it a bit better in some ways, but crappier in other. any of these could be a killer feature for 2.8 kernel series. or 2.6.2x :)
i would like people to discuss this. be polite please :)