Re: [PATCH] Re: msdos/vfat defaults are annoying
On 2005.02.07 08:47, Pozsár Balázs wrote: On Mon, Feb 07, 2005 at 02:48:00AM +, 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Re: msdos/vfat defaults are annoying
On 2005.02.07 00:42, Pozsár Balázs wrote:
On Mon, Feb 07, 2005 at 12:36:10AM +, Al Viro wrote:
> On Mon, Feb 07, 2005 at 12:21:08AM +0100, Pozsar Balazs wrote:
> > On Sun, Feb 06, 2005 at 07:06:59AM +, Christoph Hellwig wrote:
> > > filesystem detection isn't handled at the kerne level.
^
IIRC currently if both msdos and vfat are compiled in (not modules),
and
you try to mount a vfat filesystem without explicitly specifying the fs
type, it will be mounted with the msdos type. With the, it will mounted
vfat.
But since filesystem detection isn't handled in the kernel, changing the
link order is pointless. Please fix your /etc/filesystems instead.
~# grep camera /etc/fstab
/dev/sda1 /mnt/camera auto users,noauto 0 0
~# strace -o mount.trace mount /mnt/camera
~# grep filesystems mount.trace
open("/etc/filesystems", O_RDONLY|O_LARGEFILE) = 3
~# cat /etc/filesystems
ext2
ext3
nodev proc
nodev devpts
iso9660
reiserfs
vfat
udf
Also check man 8 mount, specifically option -t:
[...] Creating a file /etc/filesystems can be useful to change the probe
order (e.g., to try vfat before msdos) ...
This is from man-pages 1.66, btw.
Regards,
Nuno
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] remove dead cyrix/centaur mtrr init code
On 2005.03.02 08:02, Dave Jones wrote: The Winchips never really sold that well, and stopped being produced when IDT sold off Centaur. It was a niche processor in 1997. In 2005, I'll be surprised if there are that many of them still working. Mine lost its magic smoke for no reason around ~2002. If there are any of them still being used out there, I'd be even more surprised if they're running 2.6. Then again, there are probably loonies out there running it on 386/486's. 8-) Heh. Let me brag about it a little: $ cat /proc/cpuinfo processor : 0 vendor_id : CentaurHauls cpu family : 5 model : 4 model name : WinChip C6 stepping: 1 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu de msr mce cx8 mmx centaur_mcr cid bogomips: 399.76 $ uname -a Linux kawasaki 2.6.10-rc3 #3 Fri Dec 17 21:44:53 CET 2004 i586 unknown $ uptime 19:00:14 up 58 days, 1:21, 1 user, load average: 0.37, 0.17, 0.11 Running 2.6 at least since 2.6.0-test11-wli-something, dated Dec 6 2003 according to /boot (may have been running other 2.6-test before, but I dont have them around any longer): $ ls -al /boot/vmlinuz-2.6.0-test11 -rw-r-1 root root 840607 Dec 6 2003 /boot/vmlinuz- 2.6.0-test11-wli Not a single hiccup, so far *knock on wood*. Bragging even further, I also have a genuine 80386 DX 33 up and running, although that one is still on 2.0.37, iirc. Oh, yes, I'm a loonie ;-) Regards, Nuno - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
