Release Candidates :: DSL v4.0 alpha1



Quote (andrewb @ July 18 2007,16:25)
OK, so I probably missed something obvious, but... is there an easy way to turn the DFM desktop context menu menu back on after it has been turned off (via the 'Desktop Context Menu' checkbox')? Is there any documentation for DFM? The website http://www.kaisersite.de/dfm/ doesn't seem to have any .

Obviously, you should have an icon somewhere on your screen, right click on it and then the usual selection that you used to turn it off turns it on. It is a toggle. DFM for X11 -> Desktop context menu

I leave it on and use the bottom edge right click menu.

dfm manpage

So far I am liking 4.0 a lot, thanks!
Is there an updated copy of the bootfloppy available? I have been using this so i can burn customised bootable CD's on an M$ machine for running DSL inside a virtual machine (VirtualBox).
Quote
How can this be backward compatible when such is the case?
You cannot go back and change the mydsl loading scripts on all previous versions of DSL.


By 'backwards compatible" I meant that, with a test something like this added, the scripts could (to provide transitional support) be made to recognize both the old .dsl and .tar.gz and "new" .dsl which would, from then on, be redefined to include both red and green .dsl. Users could then be told to call any new "green" extensions .dsl, not tar.gz.   Perhaps "backwards compatible" was the wrong way to express this - I was referring to the change being conveivably compatible with both old and new extension suffixes, but not with earlier dsl versions on low ram hardware.

Yes, users of previous versions of dsl on old hardware could then be running wkriteable unneccesarily on new extensions from the newly-broadened .dsl category and running into problems.   This would be a mandatory upgrade to the new dsl version (or some sort of patch extension as you say) if they wanted to avoid that.  But I don't see any way around that if you want to get rid of tar.gz while maintaining support for legacy.   And if you don't and rely on unionfs to solve the problem, then users of even older pre-unionfs versions of dsl on old hardware will be left behind anyway.  Perhaps can't avoid a mandatory upgrade for a minority of users to a newer dsl version one way or the other?  Then there are an increasing number of those with newer hardware (me) for whom running mkwritable has no negative effects anyway.

Quote
Must I continue to still support both unionfs and legacy?


I've obviously assumed you would be, and didn't know dropping it was on the cards.  I'm one of those often using a legacy boot, because I need ipw2000 with my hardware as you know (dsl-2.1b) (I however still try newer versions).  Eventually that will be resolved also.

Quote
a test should be made for
1. The operating mode is legacy.
2. The extension is of type .dsl


Yes.

Granted it requires more thinking through, I've just raised it as an idea.
Quote (andrewb @ July 18 2007,23:31)
Is there an updated copy of the bootfloppy available? I have been using this so i can burn customised bootable CD's on an M$ machine for running DSL inside a virtual machine (VirtualBox).

New boot floppy now posted to the Release Candidate area!
Next Page...
original here.