mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gerry <gerry@c64.org>
To: linux-kernel@vger.kernel.org
Subject: supermount ?
Date: Thu, 22 Mar 2001 23:21:07 +0100	[thread overview]
Message-ID: <01032223210703.00829@localhost.localdomain> (raw)

I recently upgraded my kernel to version 2.4.2, with no problems at all, 
except one: supermount. I guess you already know that supermount haven't been 
upgraded to support 2.4.2 or even 2.4 yet, and i guess there's nothing to do 
about that but wait. But that's not why i'm writing this.

Supermount sounds to me like a very important part of linux, at least for us 
who like our cds/dvds/etc. to work as easily as in fx. windows. For linux to 
be popular among "normal" users, it should be present at every system with 
local removable drives. So, my question is; why isn't supermount a standard 
part of the kernel, or at least a module ?

Right now i have to use autofs to manage automounting, but there's several 
problems with that (as it's aimed at use with network devices): Fx, it locks 
my dvd/cdrw-drives every time they get mounted, so that eject isn't possible 
until it gets unmounted. Floppy disks aren't updated until they're remounted. 
Setting low timeouts doesn't help at this, since it doesn't seem to work that 
well with local devices for some reason..

So, supermount is required even if autofs is included in the kernel, from my 
point of view anyway. I'm sure there's many people out there like me :)

Any chance supermount will be a standard kernel module in the future ?

Gerry

             reply	other threads:[~2001-03-22 22:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22 22:21 Gerry [this message]
2001-03-22 22:49 ` Erik Gustavsson
2001-03-22 23:03 ` Alan Cox
2001-07-22  9:20 Supermount? David Findlay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=01032223210703.00829@localhost.localdomain \
    --to=gerry@c64.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®