Welcome to the CD v6 Project Page

The first CD overlay for beta testing will be available shortly, it will be a preselected grouping of software in zip format, allowing for instant creation of the EDU-Nix v6 Beta CD - just add Slax 6 and shake.

Creating an EDU-Nix v6 Beta CD

1. Download Slax v6 from slax.org (current version is 6.0.3) and burn it to CD
2. Copy files from Slax 6 CD to your hard drive, to a folder called mycd for example.
3. Extract the overlay zip file (or individual program folder if downloaded seperately) over the extracted Slax CD files, you should be prompted regarding the pre-existing directories, you can select to overwrite all files if prompted.
4. Open up a terminal (command prompt) and navigate to your mycd/slax directory. On Windows, run the make_iso.bat file; On Linux, use ./make_iso.sh to create your own customized .iso image for burning.
5. Tweak and repeat as necessary.

   A good boot 'cheatcode' to familiarize yourself with for testing is the "from=" parameter. It allows you to boot from CD initially, then load the contents of your .iso file from hard drive instead - saving you stacks of blank CDs for testing.

Please note the following:

• These modules are .lzm format, compatible with Slax v6 Technology, and will not work with prior EDU-Nix Dual Mode CDs. You will need to obtain a copy of Slax 6 in order to use these modules, a full EDU-Nix release will be forthcoming based on Slax 6.
• These modules have not (yet) been confirmed to comply with slax.org's "rules" for module creation, since they are still in beta status and not necessarily ready for production. Before going final, all modules will be guaranteed to conform to the rules, but for now be warned.
• The directory layout and file naming conventions are such to work with my personal CD-building script, and allows you to simply copy the app's skeleton directory over your extracted Slax files, quickly identify dependency modules and control loading and noloading of modules easier.
• In some cases, dependency modules may not be completely necessary - some fiddling and testing needs to be done to determine which are build dependencies versus run-time dependencies...