All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dan Maas" <dmaas@dcine.com>
To: "Pavel Machek" <pavel@suse.cz>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Forced umount (was lazy umount)
Date: Tue, 18 Sep 2001 21:15:24 -0400	[thread overview]
Message-ID: <0a0c01c140a8$92b45620$1a01a8c0@allyourbase> (raw)
In-Reply-To: <fa.d1dh3vv.fmmj8f@ifi.uio.no> <fa.e30ljmv.19jambt@ifi.uio.no>

> Imagine (common error for me):
>
> cd /cdrom
> kwintv &
> [work]
>
> I now want to umount cdrom. How do I do it? Do you suggest each app
> to have "cd /" menu entry?
> Pavel

No but now that you mention it, it might be a good idea for GUI programs to
chdir("/") by default immediately on startup. (and fork/daemonize so they
don't disappear if you accidentally close the xterms you used to start them)

Regards,
Dan


       reply	other threads:[~2001-09-19  1:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.d1dh3vv.fmmj8f@ifi.uio.no>
     [not found] ` <fa.e30ljmv.19jambt@ifi.uio.no>
2001-09-19  1:15   ` Dan Maas [this message]
2001-09-19  1:19     ` Forced umount (was lazy umount) Mike Fedyk
2001-09-19 10:20       ` Andreas Schwab
2001-09-14 19:01 [PATCH] lazy umount (1/4) Alexander Viro
2001-09-16 16:37 ` Alex Stewart
2001-09-17  6:57   ` Forced umount (was lazy umount) Ville Herva
2001-09-17  7:03     ` Aaron Lehmann
2001-09-17  8:38       ` Alexander Viro
2001-09-17 10:21         ` Matthias Andree
2001-09-17 10:47           ` Tigran Aivazian
2001-09-17 23:21             ` Alex Stewart
2001-09-17 23:23               ` Xavier Bestel
2001-09-18  1:04                 ` Alex Stewart
2001-09-18 20:19                   ` Pavel Machek
2001-09-17  8:29     ` Xavier Bestel
2001-09-17  8:39       ` Alexander Viro

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='0a0c01c140a8$92b45620$1a01a8c0@allyourbase' \
    --to=dmaas@dcine.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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.