On Thursday 30 May 2002 05:13 pm, Michael Adams wrote:
> On Thu, 30 May 2002 22:50, et wrote:
> > the file system for / and /boot need to be compiled into the
> > kernal, not loaded as a module, that was (as I understand it) the
> > reason not to use reiserFS for those partitions. however in later
> > kernals, the journal FS can be complied to the kernal during
> > install, ending the no ReiserFS for /boot reasoning. however,
> > since most newbies don't know weither the file system is loaded
> > as a module or is compiled into the kernal...no ReiserFS /boot
> > still seems a fair rule.
>
> Thanks, clear and concise. Just the info required.
I've been usin ReiserFS for almost two years. During that time
I've always installed Mandrake into one big 'ol '/' partition (IOW,
no separate /boot partition, or any other for that matter). ReiserFS
has always been loaded as a module, not compiled into the kernel.
During this period I've used dozens of kernels from 2.2.x up to my
current 2.4.18-13k7 that I compiled. Making my own kernel from
mandrake sources has always been one of the first things I do shortly
after a fresh install. Usually within days. Still either with the
default install kernel, or my own, ReiserFS has always been a module.
'lsmod' always shows ReiserFs module loaded.
I've never had a problem with ReiserFS loaded as a module with
/boot being ReiserFS (or XFS). I see this "/boot can't be Reiser",
or even "/boot must be ext2" all the time. I don't know where it
comes from, or why these ideas persist. I can only say it's never
been true here with many kernels, and usin first with an Intel/Intel,
now with an AMD/VIA system.
--
Tom Brinkman Corpus Christi, Texas
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
