schamberlin

Group: Members
Posts: 6
Joined: Jan. 2006 |
 |
Posted: Jan. 14 2006,06:16 |
 |
To answer my own question, it seems that it _is_ as simple as a kernel recompile. I did some sleuthing and learned that the DSL kernel is configured with ext3 support as an external module, instead of being compiled directly into the kernel. I recompiled the kernel with ext3 compiled directly in, and now it works!
Or I think it works, at least. After switching to my new kernel, I can now power off my laptop with impunity, and it always reboots fine the next time without any fsck complaints. I don't see any special ext3 or journaling related messages at startup, but I assume it's working.
Question to the DSL maintainers: why is ext3 support not compiled directly into the DSL kernel by default? Since it's already included as a module, I don't think it would require any extra space to compile it in directly instead. That would solve a lot of problems that me and other people seem to have with ext2, without needing to worry about setting up reiserfs.
|