mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vitaly Lipatov <LAV@VL3143.spb.edu>
To: Bryce Nesbitt <bryce@obviously.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why would a valid DVD show zero files on Linux?
Date: Mon, 31 Dec 2001 18:10:58 +0300	[thread overview]
Message-ID: <20011231151059.404B34394E@VL3143.spb.edu> (raw)
In-Reply-To: <E16L2G8-00050T-00@the-village.bc.nu> <3C307464.2253E26@obviously.com>
In-Reply-To: <3C307464.2253E26@obviously.com>

On 31 December 2001 17:21, Bryce Nesbitt wrote:
> A disk with a blank iso9660 plus a full UDF ought to automatically mount
> UDF, no? How hard would that be to detect?
You have to set type 'auto' in fstab and add 'udf' in first line of 
/etc/filesystems.

Follow is piece of man mount:
              The type iso9660 is the default.  If no  -t  option
              is  given,  or  if  the auto type is specified, the
              superblock  is  probed  for  the  filesystem   type
              (minix, ext, ext2, ext3, xiafs, iso9660, jfs, reis-
              erfs, romfs, ufs, ntfs,  qnx4,  bfs,  xfs,  cramfs,
              hfs,  hpfs,  adfs,  vxfs  are  supported).  If this
              probe fails,  mount  will  try  to  read  the  file
              /etc/filesystems,  or,  if  that  does  not  exist,
              /proc/filesystems.  All  of  the  filesystem  types
              listed  there  will be tried, except for those that
              are labeled "nodev" (e.g., devpts, proc and nfs).

Please tell me is you successfully done it.
On my system it do not work. :(
-- 
Lav
Vitaly Lipatov
GNU! Linux! LaTeX! LyX!

  parent reply	other threads:[~2001-12-31 15:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-31  0:45 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 [this message]
2001-12-31 23:37         ` Cameron Simpson
2002-01-01  5:34           ` Bryce Nesbitt
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
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=20011231151059.404B34394E@VL3143.spb.edu \
    --to=lav@vl3143.spb.edu \
    --cc=bryce@obviously.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®