Slax author's Blog (RSS)

It appears that you are on a roll with upgrading the slax.org site.

Oh yes! :)

thank you.

yep, it works... Assembled 678MB a downloaded (like .iso)... . Unfortunately my pick wasnt lucky enough:D ... It went as far as loading modules to RAM. But other than that, it works smoothly!

If it is feasible, it would be nice for users to be able to bookmark/save in some way the Slax build before downloading.

This would be a nice feature, which would allow for users to download the modified Slax image with new packages when upgrades occur or it could allow for users to share the Slax build that they like.

ie. A Slax 5.x.x user returns to find that there is only one version. They use the Slax build interface to recreate the Slax popcorn image with the updated software.

It could be a pain for the user to tell the other users what packages were used and let them find them for themselves. It would be much nicer for the user to just point them to some interface, which could get the Slax build to the state it was for the initial user.

Yes that is something I was thinking about too :) And it is pretty trivial, user would just download a list of module IDs.

The problem may appear if there are new versions of modules... and also new version of Slax base files. What should the software pick up? Updated versions of everything? Then it would perhaps work.

I think there could be a way to check version depend.

The best way would be by the name of the package. It would be have to have the package name like in slackware with the /var/log/package-version in module. This way it could check what version is in what module. But it will also have to check the files list to know that all files are there. This could be the best way for your approved modules page and version check for building custom livecds.

I have used it, and it looks good. Only 1 problem so far, I built the iso and it told me that connection to slax.org was broken. I tried it again and it told me that it succeeded. I will check it out and report back :)

hi i have recently encounterd something interesting
i had slax 5 cd with open mutisess, burned two years ago
(plain as iso, only with open multisession)
as i figured i would not need it to boot much from it,
i added as second multisess. some modules and one other linux :)
and it has booted ! and recognised new modules.
(dont know is this was recorded somewere on old or new forum ? or if someone else tryed this ? )

now i wonder if this could be used somehow as a longshot for this slax build thingie ?
for example if user has allready downloaded main iso
(or tar archive ) perhaps if to find out that he has it,or select somewhere (checkbox 'i allready have tar untared on usb' )?
and just add the rest what he is selected ,and the result is ,the base modules not be downloaded over and over
(only if updated in meantime ? )
and so the rest of selected modules to be burned as second session for cd ?

but it may be too complicated :(.
perhaps this idea to be left aside for now

yeah building slax is very useful; e.g. i use only textmode linux, so its enough to download a 86M image file.