Release Candidates :: DSLv3.0RC2

Yeah, i think that unionfs just dosen't agree with my computer. I tried live with no options(just hit enter) and it froze my computer, had to hit the reset. I booted " dsl toram xsetup legacy " and everything works fine. So i guess i'll just test the standard setup for ya.

I'll let you know if i find any problems running it regular. :;):

Robert - I noticed that in DSL's 2.4 and lower /tmp is a symlink to /var/tmp. In 3.0, /tmp is linked to /ramdisk/tmp. I believe this is causing the problem with some of the mydsl.menu items not being added. The extensions I tested that were built using /tmp/mydsl.menu are being added to the Fluxbox/Mydsl menu, the ones that use /var/tmp/mydsl.menu are not.

OK. Then those extensions need to be adjusted. /tmp should be on ramdisk and not in union space. Once I have a list of those I can start making adjustments. /tmp should have always worked on all extensions.

I guess I was just wondering if the directory structure could be adjusted to resemble DSL 2.4 - with /tmp being a symlink to /var/tmp. I had built a few packages according to this write up in the wiki. The example uses /var/tmp for the mydsl.menu, which unfortuately doesn't add to the MyDSL menu in 3.0. I am just afraid there will be packages in the repository that this will effect.

It is unfournate that it was wriiten that way, as using /tmp works equally as well.
However, in moving forward and to try to stay compatible with Knoppix and DSL-N dictates that we use /tmp. I am hoping that some or many extensions will work on both systems. DSL-N is going to be moving to a newer Knoppix base which is unionfs based. Knoppix 5.0 has /tmp on /ramdisk/tmp as I have in DSL 3.0. I don't want to have to adjust that one as well. The wiki documentation needs to be adjusted. Bottom line, I would rather have a directory structure that is compatible moving forward and not adjust back to the Knoppix 3.4 level. Especailly when using /tmp all along works.

Next Page...
original here.