Ditto. I'd hate to see dsl-n die a death. But I know Robert can only be stretched so far ...
Quote (WDef @ Feb. 09 2007,12:14)
Ditto. I'd hate to see dsl-n die a death. But I know Robert can only be stretched so far ...
DSL-N is/was my great hope, but I can't roll it out at it current release state. Its been on-again/off-again with DSL-N. Tried all the alternatives I could find. Xubuntu/Icebuntu/UbuntuLite/PicoDebian/Puppy. Puppy uses it own package manager, and the *buntu's have too big a disk footprint. DSL-N is just north of 300M of disk on an HDD install with X and Flux. It fits well with the hardware I'm using, runs well. I'll never convence management to use DSL with the 2.4 kernel, so I'm stuck between DSL-N RC4 or more expensive hardware and one of the BUNTU/Debian distros.
I've worked on *NIX since the pre-SYS V days as an sysadmin, and a fair amount of s/w development has passed under the bridge, so Robert, if I can be of help to get DSL-N moving, please let me know.
regardsSounds like an offer John & Robert! - enslave Greengrass into doing some work for you? Doesn't sound like he's one of these urchins either - sounds more like Robert and my generation (ie old! correction: youthful middle-aged)
ipw2200 is a common wireless card now and from Robert's post about the problems with dsl-n it seems these types of hardware issues are part of the holdup ...
Just curious: for what purpose do you want to roll out dsl-n?One of the big issues for me, is not having the hardware to test. Without it is like shooting in the dark.
Greengrass, if you have an ipw2200 and wish to compare and look for possible missing udev related files as WDef has suggested, then that would be welcomed. I would think it would not be too difficult, with unionfs, to add in any found missing files for quick and easy testing. I would then add those in and do an RC5 and then a release.
We would still have the issue of Debian and those who clamor for the latest kernel and modules.
Then there is my philosphy of non traditional hard drive installations. Those who know me, know that I like to do new things with code.
No offense to those who maintain distributions, but I don't want to swim in the sea of sameness. DSL has been fun for me, because it has a stable base, with which I could "do my thing", push and extend this small base system in many new ways.
Having the burden, of constantly compiling a kernel, compiling all the modules, i.e., compiling other people's work, is not very fun or interesting for me
It was the basis of why Knoppix was chosen to be the base and strip it down. At least the mundane task of kernel, modules, and libs were tested well beyond the "well it works for me" stage.
Perhaps there were some mis-steps with DSL-N. Obviously some hardware did not work that should have. For some Debian is mandatory. Perhaps DSL-N should have contained both sets of libraries, gtk1 ansd gtk2. At least the existing MyDSL extensions would have a better chance.
I am currently extremely busy with a DSL related project. Hopefully it will come to fruition and then all will benefit.
After that, a decision needs to be made with DSL, DSL-2.1b, and DSL-N on how to move forward.
There are some who would like to see 2.1b be brought forward with all the new features of DSL.
I am still leaning towards a smaller base. A leaner core. But there is much debate on that as well.
One thing for sure, for any new kernel based system, I will need to package up and release a development system so that the community can easily compile and therefore contribue modules for any hardware that they may own.
Comments and suggestions on moving forward are welcomed.
RobertRobert, top of your long paragraph, is that you need certain hardware.
What is the best way to get you a ipw2200, donate to DSL, or post (ship,) you actual hardware item? Including the ipw2200, are there 3 or 5 items of hardware you could really do with?Next Page...
original here.