DSL Ideas and Suggestions :: My ideas and suggestions for DSL
When testing mydsl extensions, you should always boot up DSL liveCD with no backups or mydsl extensions loaded. This way you get a default system on which to properly test.
Glad to hear that there is interest by some to compile additional modules and such...
As I have posted before, the next release of DSL will be major. DSL has always been based on Knoppix. Knoppix is no longer 2.4 based. Pretty easy to figure out what I am saying. You may want to hold off for a little because a new kernel means new modules means your new stuff today that is module based will not work when the next DSL is released.
LTmodems is in the base of the new system that I have made. It was one of the first things that I did. It is even autodetected. I felt that it is necessasy as it seems to be the most widely used one. I felt that it should be in the base as how would someone get it if dial-up is their only net connection. I smiled when I saw someone in the forums make an LTmodme.dsl as the beta testers were already using the pre-release with that capability.
After much testing, the base system is working extremely well on the many test systems that we have access to.
Notice that I said base system. There are some user contributed extensions that use modules. I felt that those should still be left to the community and their respective authors to update. Afterall, the myDSL system that I made was for the purpose to allow community members to participate.
The Wiki has the guidles for creating extensions of all types and the rules that should be followed.
With the new release, full kernel source will be provided to make building compatible modules easy.
Note that I have already provided automatic module loading at boot time with a /modules directory using a boot time option of modules
There will also be a logistical challenge of how to offer the new while still having the old around at least for awhile. By that I mean those extensions that are module based will become release specific.
Because of the aforementioned, look for a release candidiate, an RC1. During the RC series those who like to compile modules will have the opportunity to update those module based extensions. Those users who need module based extensions should stay with 1.5 until the RC series is completed. Afterall the RC series is like public beta testing.
John and I have have are hands full with the base. The extensions belong to the community.
Exciting and challenging times just around the corner...
I am glad that we have such a talented, ready, willing, and able community.
Robert
Weeeeeeee!
Every release just gets more pleasantly surprising.
This is exciting indeed. Thanks for all the hard work. 
Created and emailed libncurses5-dev.dsl and all of its dependencies in .dsl format to extensions@damnsmalllinux.org This will make it possible to do <<make menuconfig>> when compiling 2.6 kernels. I already tried <<make menuconfig>> on my system with 2.6 kernel source and it worked.
Files that were emailed:
linux-kernel-headers.dsl (dependency of libc6-dev.dsl)
linux-kernel-headers.dsl.info
linux-kernel-headers.md5sum.txt
libc6.dsl (dependency of libc6-dev.dsl)
libc6.dsl.info
libc6.md5sum.txt
libc6-dev.dsl (dependency of libncurses5-dev.dsl)
libc6-dev.dsl.info
libc6-dev.md5sum.txt
libncurses5.dsl (dependency of libncurses5-dev.dsl)
libncurses5.dsl.info
libncurses5.md5sum.txt
libncurses5-dev.dsl
libncurses5-dev.dsl.info
libncurses5-dev.md5sum.txt
This should provide everything necessary for <<make menuconfig>> to work on a later 2.6 kernel in DSL, assuming I made the .dsl files correctly.
Next Page...
original here.