myDSL Extensions (deprecated) :: MyDSL Maker
Hm. I've never used the toram option, so I can't tell you. I test the output using qemu, and you can understand, ram is limited.
Concerning the theme: dsl 0.9* has removed the /home/damnsmall folder I've been putting themes into (in the 0.8* series, this was symlinked to /home/dsl for compatibility with older dsl and tar.gz modules). This needs to be fixed and will be in the next release.
I do like your idea of a fully stripped core with extensions as wanted. It would sure kill my penchant for accidentally making DSL 0.9* disks with two copies of firefox.
Dillo, however, is required and very small. As is the monkey server and perl. These three are necessary for the MyDSL system (the myDSL script is written in a combination of sh and perl and is served locally to dillo)
the toram option prevent dsl extensions from loading, to ensure that the cdrom is not needed...
The current delay in making a new release of the MyDSL maker is in remastering DSL with slightly modified scripts and bootsplash capabilities (and now that I've been given the idea, perhaps also the stripping of several more programs, making of new extensions, etc.) anyway, essentially, I'm rebuilding bite of the core, and that's going to take some time, as the debugging process is a bit arduous (make minute changes and tweaks, make KNOPPIX image, build into CD, boot with QEMU, step through startup, lather, rinse, repeat).
On the script side of things, the isolinux.cfg maker is almost complete and will be released with the new core. (since the core is no longer an official DSL release, it's fmDSL 0.9.0.1 (Fordi's MyDSL).
Oh, and here's the good part: When I'm done, the ENTIRE FILESYSTEM will be writable without being on an HD. You know, RAM warnings and all to those with low RAM. Don't try and compile KDE either.
(Essentially, the / will be the ramdisk, KNOPPIX mounted within, the CI Filesystem soft-linked to the ram filesystem, and DSL started proper. This works similarly to mkwritable. Thing is, the actual disk use for symlinks is close to nil. maybe 1k overhead per file. So I'm eating up about a meg of ram at best. On the other hand, it enables one with large gobbing amounts of ram to really scream in the installation department.)
Hi,
I am new, just tried the MYDSL maker. I selected a few apps and when I click Gimme MYDSL buttom I get a message saying "Connection was refused when trying to contact 127.0.0.1"
What is hapenning?
I really like the web-interface in concept, but if it ever became widely adapted it will be a tremendous recourse in terms of CPU cycles and also Bandwidth. I think we should look into a way of incorporating this into DSL proper which isn't a burden on our mirrors. I am worried about losing them as it is.
Next Page...
original here.