From: Lee Revell <rlrevell@joe-job.com>
To: Valdis.Kletnieks@vt.edu
Cc: 7eggert@gmx.de, Andy Lutomirski <luto@myrealbox.com>,
linux-kernel@vger.kernel.org
Subject: Re: the umount() saga for regular linux desktop users
Date: Tue, 04 Jan 2005 15:28:44 -0500 [thread overview]
Message-ID: <1104870524.8346.27.camel@krustophenia.net> (raw)
In-Reply-To: <200501022243.j02MhANg004075@turing-police.cc.vt.edu>
On Sun, 2005-01-02 at 17:43 -0500, Valdis.Kletnieks@vt.edu wrote:
> On Sun, 02 Jan 2005 13:38:29 +0100, Bodo Eggert said:
>
> > Maybe it's possible to extend the semantics of umount -l to change all
> > cwds under that mountpoint to be deleted directories which will no
> > longer cause the mountpoint to be busy (e.g. by redirecting them to a
> > special inode on initramfs). Most applications can cope with that (if
> > not, they're buggy),
>
> You mean that a program is *buggy* if it does:
>
> cwd("/home/user");
> /* do some stuff while we get our cwd ripped out from under us */
> file = open("./.mycconfrc");
>
> and expects the file to be opened in /home/user???
Yes, of course. Any program that doesn't check the return value of a
system call is buggy. Unless it really, really doesn't care - clearly
not the case here.
Lee
next prev parent reply other threads:[~2005-01-04 20:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.iji5lco.m6nrs@ifi.uio.no>
[not found] ` <fa.fv0gsro.143iuho@ifi.uio.no>
2005-01-02 12:38 ` the umount() saga for regular linux desktop users 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 [this message]
2005-01-05 2:12 ` Bodo Eggert
[not found] <fa.foeqpaf.nlmd9n@ifi.uio.no>
[not found] ` <fa.d9avdr3.1jm46gr@ifi.uio.no>
2005-01-03 1:17 ` Bodo Eggert
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
-- strict thread matches above, loose matches on Subject: below --
2004-12-31 17:41 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
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=1104870524.8346.27.camel@krustophenia.net \
--to=rlrevell@joe-job.com \
--cc=7eggert@gmx.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@myrealbox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.