Submitted 18-Sep-01 by Matthew D. Pitts:
> Anton,
> What sort of problems have you experienced with supermount? I have used it
> since 7.0 and never had a problem with it.
I had several kernel panics caused by incorrect addressing.
Essentially, if you use two different size floppies and inadvertantly
attempt to access the mount point for /dev/fd0h1440 and you really
wanted to mount /dev/fd0h1743 (a higher capacity disc in the same
physical drive), supermount pukes and causes a kernel panic. Autofs
simply refuses to mount the erroneous volume.
Admittedly, the panic is caused by a user error, but the fact that a
user *can* cause a panic because of this module makes it too dangerous,
IMHO.
Further problems related to the use of writeable removeable media
included incomplete writes as the buffers weren't always flushed. With
a system like supermount, you cannot afford to cache writes as the user
expects to be able to remove the media when the drive light goes out.
Supermount has also caused several conflicts with IDE CD-R(/W) drives.
Specifically, attempting to mount the volumes while a write was either
in progress (which of course fails), or beginning (cdrecord's countdown
was in progress) which results in a coaster. These accesses are
frequently unexpected such as a remote user logging into an X server and
having an icon for the burner (as a cd-rom drive) on his desktop.
--
Anton Graham GPG ID: 0x18F78541
<[EMAIL PROTECTED]> RSA key available upon request
"I got everybody to pay up front...then I blew up their planet."
"Now why didn't I think of that?"
-- Post Bros. Comics
