linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: =?unknown-8bit?Q?J=F6rn_Engel_=3Cjoern=40wohnheim=2Efh-wedel=2Ede=3E?=@win.tue.nl
Cc: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] make cramfs look less hostile
Date: Mon, 16 Jun 2003 13:21:28 +0200	[thread overview]
Message-ID: <20030616112128.GA9415@win.tue.nl> (raw)
In-Reply-To: <20030616091215.GA17446@wohnheim.fh-wedel.de>

On Mon, Jun 16, 2003 at 11:12:15AM +0200, J?rn Engel wrote:
> On Sun, 15 June 2003 23:49:09 +0200, Andries Brouwer wrote:
> > On Sun, Jun 15, 2003 at 07:18:53PM +0100, Christoph Hellwig wrote:
> > > 
> > > The only places where this should happen is mounting the rootfs.
> > > mount(8) has it's own filesystem type detection code and doesn't
> > > call mount(2) unless it found a matching filesystem type.
> > 
> > Too optimistic a description.
> > Any person who likes reliable results will give mount a -t option.
> > If someone likes to gamble, and doesnt mind system crashes, he'll
> > omit the -t and let mount guess what the type should have been.
> > Mount has a battery of heuristics for a handful of filesystems.
> > If any of these succeeds mount will try that type.
> > If none succeeds, mount will try consecutively all types listed
> > in /proc/filesystems for which no heuristic is present.
> 
> Actually, I have one example of reality matching Christoph's
> description, so he wins this fight as well.

Please don't distribute misinformation.
If you doubt, read the mount(8) code first.



  reply	other threads:[~2003-06-16 11:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-15 16:05 [PATCH] make cramfs look less hostile Jörn Engel
     [not found] ` <Pine.LNX.4.44.0306151245070.29663-100000@coffee.psychology.mcmaster.ca>
2003-06-15 17:17   ` Jörn Engel
     [not found] ` <200306151157.10493.brian@mdrx.com>
2003-06-15 17:19   ` Jörn Engel
2003-06-15 17:26 ` Christoph Hellwig
2003-06-15 17:39   ` Jörn Engel
2003-06-15 17:44     ` Christoph Hellwig
2003-06-15 17:58       ` Jörn Engel
2003-06-15 18:03         ` Christoph Hellwig
2003-06-15 18:14           ` Jörn Engel
2003-06-15 18:18             ` Christoph Hellwig
2003-06-15 21:49               ` Andries Brouwer
2003-06-16  9:12                 ` Jörn Engel
2003-06-16 11:21                   ` Andries Brouwer [this message]
2003-06-16 11:37                     ` Jörn Engel
2003-06-18  0:24             ` Robert White
2003-06-15 17:27 ` Jörn Engel
2003-06-16  5:54   ` H. Peter Anvin
     [not found] <20030615161009$6dde@gated-at.bofh.it>
     [not found] ` <20030615174004$76d0@gated-at.bofh.it>
     [not found]   ` <20030615175007$7f59@gated-at.bofh.it>
     [not found]     ` <20030615175012$0573@gated-at.bofh.it>
     [not found]       ` <20030615181004$3663@gated-at.bofh.it>
     [not found]         ` <20030615181010$7f10@gated-at.bofh.it>
     [not found]           ` <20030615182013$7a4e@gated-at.bofh.it>
     [not found]             ` <20030615183011$3fc0@gated-at.bofh.it>
2003-06-15 21:20               ` Pascal Schmidt
2003-06-16  5:37                 ` Christoph Hellwig

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=20030616112128.GA9415@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc==?unknown-8bit?Q?J=F6rn_Engel_=3Cjoern=40wohnheim=2Efh-wedel=2Ede=3E?=@win.tue.nl \
    --cc=hch@infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).