Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Unfortunately this is true _only_ if your machine shuts down cleanly. If your machine "crashes", it will not be able to mount your ext3 partition as an ext2 file system. This is because the ext3 journaling would cause the file system to be "inconsistent" as far as ext2 is concerned, and the markings of non-committed journal entries will prevent ext2 from loading the fs. Another way to get around the problem is to supply the ext3 module in an initrd. However, I would recommend you just compile ext3 into the kernel. -derek jbk <jbk at mail2.gis.net> writes: > I am configuring a new kernel and under the help > for the ext3 FS I read something to the effect " > if you compile this as a module be aware that the > file system for your root partition cannot be > compiled as a module..." > > On my standard install of RH7.2 an 'lsmod' shows > ext3 and jbd loaded as modules and in fstab '/' is > mounted as an ext3 partition. > > There seems to be a contradiction here. I am > assuming that the writer of the help file left out > some elaboration on the subject to the effect that > the ext3 journalling is an overlay on the ext2 FS > and as long as ext2 is compiled into the kernel > there is no problem mounting root as an ext3 FS. > > Any commentary would be enjoyed. > > Jim Kelly-Rand > > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://www.blu.org/mailman/listinfo/discuss -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH warlord at MIT.EDU PGP key available
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |