From: Bryce Nesbitt <bryce@obviously.com>
To: cs@zip.com.au
Cc: linux-kernel@vger.kernel.org,
Lionel Bouton <Lionel.Bouton@free.fr>,
Andries.Brouwer@cwi.nl
Subject: Re: Why would a valid DVD show zero files on Linux?
Date: Tue, 01 Jan 2002 00:34:43 -0500 [thread overview]
Message-ID: <3C314A73.E94328E9@obviously.com> (raw)
In-Reply-To: <E16L2G8-00050T-00@the-village.bc.nu> <3C307464.2253E26@obviously.com> <20020101103753.A13046@zapff.research.canon.com.au>
Cameron Simpson wrote:
>
> On Mon, Dec 31, 2001 at 09:21:24AM -0500, Bryce Nesbitt <bryce@obviously.com> wrote:
> | Alan Cox wrote:
> | > The autodetection is working. Your DVD has a UDF file system on it and a
> | > blank iso9660 one.
> | Understood. However, why can't that combination "just work"? Changing
> | /etc/fstab every time I switch between sticking in a CD-ROM and DVD-ROM is not cool.
> | Certainly that "other operating system" does not make me do that.
>
> I do this via autofs, and just say /mnt/dvd when I want UDF and /mnt/cdrom
> when I want a CDROM. It does depend on having my eyes open when I stick
> the medium in the drive...
>
> Of course, this merely bypasses the autodetection.
Ok, I admit, I do the same thing. I manually mount. But let's get in
the head of a user, why should they care what type of 5 inch round shiny
thing they just inserted?
Are there any cases where udf filesystems are present on cdrom's that should
be read as iso9660? Someone mentioned it's a hard heuristic to figure out
which fake filename the empty iso9660 filesystem uses. How about, instead,
pick the larger of the two filesystems if both are present.
-Bryce
next prev parent reply other threads:[~2002-01-01 5:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 0:45 Why would a valid DVD show zero files on Linux? Bryce Nesbitt
2001-12-31 1:06 ` Alan Cox
[not found] ` <3C2FB85E.3080508@free.fr>
2001-12-31 2:07 ` Bryce Nesbitt
2001-12-31 13:13 ` Alan Cox
2001-12-31 14:21 ` Bryce Nesbitt
2001-12-31 14:48 ` Marius Gedminas
2002-01-01 10:40 ` Alan Cox
2001-12-31 15:10 ` Vitaly Lipatov
2001-12-31 23:37 ` Cameron Simpson
2002-01-01 5:34 ` Bryce Nesbitt [this message]
2002-01-01 10:12 ` Alan Cox
2002-01-01 10:30 ` Ryan Cumming
2002-01-01 10:43 ` Alan Cox
2002-01-01 10:46 ` Alan Cox
2002-01-01 14:22 ` Bryce Nesbitt
2002-01-01 15:24 ` Alan Cox
2002-01-01 23:29 ` Grahame Jordan
2002-01-01 23:49 ` Bryce Nesbitt
2002-01-01 23:53 ` Alan Cox
2002-01-02 7:57 ` Grahame Jordan
2002-01-30 15:08 ` Bryce Nesbitt
-- strict thread matches above, loose matches on Subject: below --
2001-12-31 0:51 Bryce Nesbitt
2001-12-31 3:01 RaúlNúñez de Arenas Coronado
2001-12-31 15:29 Andries.Brouwer
2002-01-01 11:50 ` Kai Henningsen
2002-01-05 2:50 Andries.Brouwer
2002-01-05 4:20 ` Bryce Nesbitt
2002-01-05 16:14 ` Bryce Nesbitt
2002-01-05 17:16 Andries.Brouwer
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=3C314A73.E94328E9@obviously.com \
--to=bryce@obviously.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=Lionel.Bouton@free.fr \
--cc=cs@zip.com.au \
--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 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.