From: Greg Stark <gsstark@mit.edu>
To: William <wh@designed4u.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: the umount() saga for regular linux desktop users
Date: 15 Jan 2005 23:39:00 -0500 [thread overview]
Message-ID: <87brbqt2cb.fsf@stark.xeocode.com> (raw)
In-Reply-To: <200412311741.02864.wh@designed4u.net>
William <wh@designed4u.net> writes:
> In my opinion, in order for linux to be trully user friendly, "a umount()
> should NEVER fail" (even if the device containing the filesystem is no
> longuer attached to the system). The kernel should do it's best to satisfy
> the umount request and cleanup. Maybe the kernel could try some of the
> following:
What you're asking for is for the umount -f option to be supported. This isn't
a new fangled idea. BSD supported has supported it since sometime in the last
millennium. Seriously, it's pretty basic functionality and really ought to be
supported.
The semantics of umount -f are simpler than you make it sound. It just
unmounts the file system normally and revokes any file descriptors for that
file system. Any further i/o on those file descriptors just gets an error
(EINVAL I expect).
This is one of my biggest pet peeves about Linux.
--
greg
next prev parent reply other threads:[~2005-01-16 4:39 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-31 17:41 the umount() saga for regular linux desktop users William
2004-12-31 17:47 ` Arjan van de Ven
2004-12-31 17:48 ` Ush
2004-12-31 18:22 ` Gene Heskett
2004-12-31 18:31 ` Miquel van Smoorenburg
2004-12-31 21:48 ` Tom Felker
2005-01-01 0:07 ` Gene Heskett
2004-12-31 17:50 ` Andries Brouwer
2005-01-01 19:40 ` Andy Lutomirski
2004-12-31 17:51 ` Gene Heskett
2005-01-16 4:39 ` Greg Stark [this message]
[not found] <fa.iji5lco.m6nrs@ifi.uio.no>
[not found] ` <fa.fv0gsro.143iuho@ifi.uio.no>
2005-01-02 12:38 ` Bodo Eggert
2005-01-02 20:27 ` Adrian Bunk
2005-01-03 0:37 ` Bodo Eggert
2005-01-02 22:43 ` Valdis.Kletnieks
2005-01-04 20:28 ` Lee Revell
2005-01-05 2:12 ` Bodo Eggert
-- strict thread matches above, loose matches on Subject: below --
2005-01-02 19:37 Pavel Machek
2005-01-02 20:11 ` Adrian Bunk
2005-01-02 20:15 ` Pavel Machek
2005-01-02 20:34 ` Oliver Neukum
2005-01-02 20:51 ` Adrian Bunk
2005-01-02 20:56 ` Pavel Machek
2005-01-02 21:05 ` Adrian Bunk
2005-01-03 9:35 ` Frank van Maarseveen
2005-01-03 19:14 ` Ingo Oeser
2005-01-02 20:36 ` Adrian Bunk
2005-01-03 1:36 ` Puneet Vyas
2005-01-02 20:36 ` Andreas Schwab
[not found] <fa.foeqpaf.nlmd9n@ifi.uio.no>
[not found] ` <fa.d9avdr3.1jm46gr@ifi.uio.no>
2005-01-03 1:17 ` Bodo Eggert
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=87brbqt2cb.fsf@stark.xeocode.com \
--to=gsstark@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=wh@designed4u.net \
/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