From: "Lasse Kärkkäinen / Tronic" <tronic@trn.iki.fi>
To: Oliver Neukum <oliver@neukum.org>
Cc: "Lasse Kärkkäinen / Tronic" <tronic+lzID=lx43caky45@trn.iki.fi>,
ioGL64NX <iogl64nx@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Supermount
Date: Sat, 23 Jul 2005 20:35:08 +0300 [thread overview]
Message-ID: <42E27FCC.5050601@trn.iki.fi> (raw)
In-Reply-To: <200507231247.17034.oliver@neukum.org>
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
> To mount on demand use autofs. Unmounting and dealing with media removal
> is the problem.
Granted, that can get pretty close. However, having to use /auto/*
instead of mounting directly where required often limits using it quite
a bit. Thus, I don't see it as a real alternative.
- Tronic -
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-07-23 17:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 21:04 Supermount Lasse Kärkkäinen / Tronic
2005-07-21 21:41 ` Supermount Francois Romieu
2005-07-21 21:50 ` Supermount ioGL64NX
2005-07-22 16:38 ` Supermount Lasse Kärkkäinen / Tronic
2005-07-23 10:47 ` Supermount Oliver Neukum
2005-07-23 17:35 ` Lasse Kärkkäinen / Tronic [this message]
2005-07-24 1:44 ` Supermount Ian Kent
2005-07-24 1:48 ` Supermount Ian Kent
2005-07-24 20:05 ` Supermount zhilla
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 13:41 supermount ismail donmez
2003-05-14 13:54 ` supermount Alan Cox
2003-05-14 13:40 supermount ismail donmez
2003-05-14 15:04 ` supermount Con Kolivas
2003-05-15 6:16 ` supermount ismail (cartman) donmez
2003-05-13 16:30 supermount Maciej Górnicki
2001-06-25 16:50 supermount Sam Halliday
2001-06-26 0:30 ` supermount Steve Kieu
2001-06-30 5:17 ` supermount John Silva
2001-06-25 16:44 supermount Sam Halliday
2001-07-07 1:43 ` supermount Dj_RzulF
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=42E27FCC.5050601@trn.iki.fi \
--to=tronic@trn.iki.fi \
--cc=iogl64nx@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=tronic+lzID=lx43caky45@trn.iki.fi \
/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