Messages in this thread | | | Date | Thu, 17 Jan 2002 09:38:39 +0300 | From | Oleg Drokin <> | Subject | Re: [reiserfs-list] Boot failure: msdos pushes in front of reiserfs |
| |
Hello!
On Tue, Jan 15, 2002 at 06:47:12PM +0100, Matthias Andree wrote: > > Looking at init/main.c and fs/super.c, rootfsflags parameter is never > > saved, moreover - it's original value is destroyed, once initrd fs is > > mounted. And I only see not very nice ways of fixing this, so perhaps > > someone more exeprienced can come up with the solution? (my crappy > > ides is not to do putname() on fs_names, if (real_root_dev != > > ROOT_DEV), all of this is only when CONFIG_..._INITRD enabled) > Thanks for confirming a bug, so I understand that mounting an initrd > loses the rootfsflags, and as the actual root= parameter is kept over an > initrd boot, it should also be possible for rootfsflags= -- can the > rootfsflags maybe be saved along with the root= parameter?
No. rootfsflags is saved. What is not saved is rootfstype. And yes, it can be saved, of course.
> > > Yup, reiserfs is last in /proc/filesystems when loaded as module, but on > > > my private machine (where it's linked into the kernel), it's right after > > > ext2 and before vfat. > > Do you have vfat as a loadable module? > Hum, yes, but that's not the point, someone turned up with a SuSE 7.3 This is the point in fact. If you'd have both reiserfs and vfat compiled-in, you'd see that vfat ebfore reiserfs in /proc/filesystems.
Bye, Oleg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |