mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Herve Fache" <herve.fache@europemail.com>
To: linux-kernel@vger.kernel.org
Subject: Removing/ejecting and mount
Date: Mon, 05 Jan 2004 10:50:27 +0000	[thread overview]
Message-ID: <20040105105027.15858.qmail@iname.com> (raw)

I was reading someone's wish to support removal of media such as USB keys or CompactFlash cards at any time. I have the same wish. In fact, I thought it through a bit and I would like a bit more mount options. I could do with:
- almost-sync: allow for delay in writing (not as 'hard' as sync), but do not return until the data is actually safely written onto the medium
- nobusy: umount works (maybe with -f option?) even if the medium is 'busy'
- ephmerary: if the device is mounted rw from a user's point of view, it is not from a kernel point of view unless required by a write operation, and only for the duration of it

Why? Imagine the standard user:
- inserts medium (such as a compact flash card) - hotplug mounts it for him automatically and the WM opens a file manager window
- copies files to/from it - the medium is only in rw mode for the time of the writes (ephemerary option)
+ copy window disappears - we know it _IS_ done (almost-sync option) and we're now mounted ro
- removes compact flash card - hotplug needs to be able to 'clear' the mount, even if busy (nobusy option), and the WM can close any active window pointing to it
+ the medium is still 'clean'

Also, the nobusy option means I can always eject my CD, and that my CD can be handled the same way as described above...

Note that explaining users what mounting is about is very time consuming; such a solution would be greatly beneficial to my nerves...

I am open to comments, and pointers to where this can be implemented but please no flames!
Hervé.
-- 
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm


                 reply	other threads:[~2004-01-05 10:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040105105027.15858.qmail@iname.com \
    --to=herve.fache@europemail.com \
    --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®