Release Candidates :: DSL v4.0 alpha2

I was just digging through the (unfortunately) outdated wireless configuration script and I encountered something interesting. The variable declaration in wlcardconfig:

Code Sample

WLDEVICES=`grep -v "|" /proc/net/wireless | awk -F: '{print $1}]`

This seems to produce two leading spaces when executed, i.e. it gives:
" wlan0"

When I tried to use this command in another script, the two leading spaces caused errors. (I removed these with the ugly addition of a third pipe: "| sed -e 's/ //g' ".)

Is there any reason why these leading spaces don't produce an error in the current wlcardconfig? I personally use a text-based script I wrote that autoconfigures wpa_supplicant in the same way for my wireless configuration, but I was just curious in terms of the script in DSL why this wouldn't produce an error.

On another note, cpu frequency scaling on my Gateway Turion 64 laptop, which worked in DSL 3.4 but failed in DSL 3.4RC1 also does not work with DSL 4. I could find no discernable reason why it would work in 3.4 final but not 3.4RC1; it might be some weird problem that can't be easily fixed.

Finally, Dillo autostarting is not working for me in DSL 4 - it doesn't show up like it does in previous versions.

Quote

I could find no discernable reason why it would work in 3.4 final but not 3.4RC1; it might be some weird problem that can't be easily fixed.

Excellent, because 3.4rc1 was *superceded* by other release candidates and ultimately the official version (3.4). See the notes/changelog. I don't know why you would be concerned about a release candidate when the official version is already out.

Quote

Dillo autostarting is not working for me in DSL 4 - it doesn't show up like it does in previous versions.

How are you running DSL? CD, USB, frugal, debian-style?

I usually try to be responsive to fourm user requests and other observations that I have come to my attention. Specifically two areas are presently on my mind.

1. The real benefits of the 2.4.34.1 kernel presently in alpha.
2. The real need for support of ipw2100 and ipw2000 wireless.

Both ipw2x00 and sata were supported in 2.4.31 (dsl 2.1b). Several other extensions were made for 2.4.31including an nvidia one.

No one has yet to contribute a 2.4.34.1 module based extension. Therefore we have less hardware support than before. And it appears that some hardware such as ipw2x00 is no longer supported by later 2.4.x kernels, or at least newer hacks are not available. Of course a 2.6 kernel easily supports these but is physically much larger than a 2.4.

Since we are still at an alpha stage, is it worth considering for me to deploy the 2.4.31 kernel and modules of dsl 2.1b to the new basis for 4.0?

We would instantly gain additional hardware support. Some of which 2.4.31 was the last kernel for which a hack is available.

Would like feedback from the community.

Future roadmap would be DSL v5.0 to be a small core 2.6 kernel based system.

But for DSL 4.0, the question I pose to the community, is shall DSL use 2.4.31 with existing modules or 2.4.34.1 and hope that some who have such hardware and/or a hack exists to create such module(s).

-- Robert

Quote (lucky13 @ Aug. 11 2007,19:18)

Quote

I could find no discernable reason why it would work in 3.4 final but not 3.4RC1; it might be some weird problem that can't be easily fixed.

Quote

Dillo autostarting is not working for me in DSL 4 - it doesn't show up like it does in previous versions.

How are you running DSL? CD, USB, frugal, debian-style?

With regard to the issue of DSL 3.4 RC1, it was the only release candidate, and the changelog between it and the final version did not mention changes to the acpi scripts, as far as I know. I don't want to get off topic - I'm just mentioning it as a reason why acpi might be having a weird interaction with something else.

I have performed Frugal, Hard Drive, and LiveCD 'installs' and have never gotten Dillo to autostart.

There have been no changes to the acpi scripts.

Next Page...
original here.