Release Candidates :: DSL v4.2RC1



Quote (lucky13 @ Dec. 14 2007,13:51)
. Do you mind getting that error again and then copying and pasting the results of lsmod here to show how many fs modules load?

Sorry haven't been able to figure out how to paste the results of lsmod. It's on my other computer. Saved it as .rtf on floppy. Tried to paste with Dillo and Firefox but not successful.

History. Computer had C and D drives from Win days. Originally when using 3.4.7 I had it  installed as Frugal on hdb (D) with swap, DSL and persistent partitions. hda or C was formatted ext2 with two partitions. No problem.
When I decided to try 4.1 I did a clean install but used HDA for Frugal same three partitions. Added hdb with two partitions for extra space that's when the modprobe xfs showed up.
Edit: To clarify "added hdb" =just formatting the drive. Physically it was always connected.
Now by physically disconnecting hdb the modprobe xfs errors does not appear.

Edit: My mistake. Just ran mkfs.ext2 on hdb1 and hdb2.
Now modprobe xfs error does not appear.
Must have forgotten to do this on second harddrive..
Sorry.
Several things come to mind...
I will start with what I think is the most likely:

1. an unformatted partition even though it has been labeled as ext2 will be mis-identified.

2. partitons that do not match physical and logical boundaries can cause problems. Do an fdisk -l to check.

3. partitons not in numerical cyclinder order can often confuse idetification with what the bios sees versus what the software sees.
Check with fdisk -l and look at partition number versus cyclinder order.

When I am partitioning I check all of the above. I have a dev machine with multiple hard drives with multiple editions of DSL installed without issue.
Thanks roberts.

Will keep that in mind. Still learning dsl/linux.

Best wishes.
meo wrote in the remastering section...
Quote
...
DSL looks twice in the mydsl directory (if you have one) and the optional directory inside the latter. And if you have a lot of extensions in the optional directory it takes a lot of time and you will also end up with two entries of these in the menu. ...


Found it. It occurs when the mydsl folder is found under /cdrom.
It will be fixed in 4.2 final.
Quote (lucky13 @ Dec. 13 2007,06:05)
Quote
Same can be said about the firewall support modules. DSL does not have any support programs to use them. We have such only in an extension. I tried once before to move the modules into the extension. Doing so could also performance enhance DSL. Perhaps this is a good time to try again.

Now that I've gotten to the bottom of my XFS daemon issue, I think it makes a lot more sense to move various modules to extension. It really doesn’t fit in with DSL’s no-bloat philosophy to include modules that can’t be used because the tools to use them aren’t even in the repository. Some of those filesystem modules for which there are available progs in MyDSL can be added to those extensions. That shouldn’t be too inconvenient for those who actually want to load and use them since the progs are already an extension -- e.g., combing ntfs with its progs as well as reiserfs and its progs.

I don't know how many more modules you want to remove from the base.

I am improving the handling of the modules directory placed under the mydsl directory.

This should allow for seamless modprobe capability, rather than the previous insmods. This will allow easy access to additional modules and allow me to move rarely, or much less used, runtime modules into the mydsl extension system.

Doing, so frees more ram for better performance and more useful application extensions.
Next Page...
original here.