From: Nuno Monteiro <nuno@itsari.org>
To: "Pozsár Balázs" <pozsy@uhulinux.hu>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Re: msdos/vfat defaults are annoying
Date: Mon, 7 Feb 2005 14:27:49 +0000 [thread overview]
Message-ID: <20050207142749.GA29741@hobbes.itsari.int> (raw)
In-Reply-To: <20050207084709.GA30680@ojjektum.uhulinux.hu> (from pozsy@uhulinux.hu on Mon, Feb 07, 2005 at 08:47:09 +0000)
On 2005.02.07 08:47, Pozsár Balázs wrote:
> On Mon, Feb 07, 2005 at 02:48:00AM +0000, Nuno Monteiro wrote:
> >
>
> But the contents of /proc/filesystems comes from the kernel. And the
> order of filesystems comes from the link order.
>
Yes, but /proc/filesystems is only processed after two other checks have
failed first: specifying a filesystem type (-t), and reading /etc/
filesystems. Relying on mount to do the guesswork is asking for trouble
if you realy value your data. And /etc/filesystems is the mechanism mount
(8) has in place to change the probe order, in case you really want that.
This is entirely a userspace problem, the kernel shouldn't have anything
to do with it.
But, anyway, for the sake of argument let's suppose link order is
effectively changed. You just effectively broke people's working setups,
because like you want to rely on fs/ link order to mount your vfats as
vfat and not as msdos, there's people out there relying on that (broken)
assumption to have their msdos filesystems mounted as msdos. Now, with
the new link order, they'll be mounted as vfat, and pop-goes-the-weasel.
Tomorrow, someone unhappy that their msdos fs is now mounted as vfat will
send a patch changing it back, thus breaking vfats. Rinse, repeat. ;-)
See? This is just wrong. This is why mount(8) has a mechanism to change
the probe order. Everybody's happy that way, and no one has to rely on
the broken assumption that the kernel knows how you want your filesystems
mounted.
So, to sum things up: this is entirely an userspace problem. Yours just
appears to be in need of fixing or tuning.
Regards,
Nuno
next prev parent reply other threads:[~2005-02-07 14:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 5:33 John Richard Moser
2005-02-06 7:06 ` Christoph Hellwig
2005-02-06 16:29 ` John Richard Moser
2005-02-06 23:21 ` [PATCH] " Pozsar Balazs
2005-02-07 0:36 ` Al Viro
2005-02-07 0:42 ` Pozsár Balázs
2005-02-07 2:48 ` Nuno Monteiro
2005-02-07 8:47 ` Pozsár Balázs
2005-02-07 12:53 ` Michelle Konzack
2005-02-07 21:59 ` Ingo Oeser
2005-02-07 14:27 ` Nuno Monteiro [this message]
2005-02-08 23:09 ` H. Peter Anvin
2005-02-07 6:53 ` Clemens Schwaighofer
2005-02-07 11:29 ` Andries Brouwer
2005-02-07 12:45 ` Pozsár Balázs
2005-02-07 14:00 ` Clemens Schwaighofer
2005-02-08 0:23 ` Horst von Brand
2005-02-08 2:24 ` Clemens Schwaighofer
2005-02-06 11:15 ` Michelle Konzack
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=20050207142749.GA29741@hobbes.itsari.int \
--to=nuno@itsari.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pozsy@uhulinux.hu \
/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®