3 replies to this topic

[911CD.net]

I'm booting an old Slax ISO that works, it boots, the wifi works and I am able to post this from it.     But I'm having problems with the boot parms.

title Slax 7.0.8 - changes\n 216MB\n slax-English-US-7.0.8-i486.iso \n https://www.slax.org/starting.php
find --set-root /ISOs/slax-English-US-7.0.8-i486.iso
map /ISOs/slax-English-US-7.0.8-i486.iso (0xff) || map --mem /ISOs/slax-English-US-7.0.8-i486.iso (0xff)
map --hook
root (0xff)
# boot to Desktop using slax.flags=xmode
kernel /slax/boot/vmlinuz vga=773 rw slax.flags=xmode,perch,nosound from=/ISOs/slax-English-US-7.0.8-i486.iso
initrd /slax/boot/initrfs.img

The perch flag isn't working and changes are not being saved.  On the ISOs drive I have a slax folder with a changes subfolder but no changes.dat file in it.  I thought Slax would create the file if perch was specified but that hasn't happened.  If I need to create it I need instructions how to do it.  I also don't know how Slax would know where it is, there is no flag for telling Slax where the folder is that I'm aware of.

 

Suggestions? 

[Wonko the Sane]

The ISO is - by definition - read only, you are essentially telling the OS to save changes in a place where saving is not possible

 

Normally you would have an added parameter *like*:

changes=/slax/slax

 

In your specific case, probably

changes=/ISOs/slax/

would do.

 

See:

http://shishtpal.blo...7-from-usb.html

 

Wonko

[911CD.net]

Thank you Wonko. 

 

changes= is definitely not mentioned in the Slax User manual on the Slax desktop nor in Google searches for Slax perch but Slax changes= has all kinds of hits. 

 

I initially tried changes=/slax/changes/ because that's the folder structure on the drive with the ISOs folder which the Slax documentation I read says Slax writes the changes.dat file too.  It didn't work.  But after reading your link it implies I should move the /slax/changes folders under the ISOs folder.  So I got to try more things.

 

Thanks again for your help. 

[Wonko the Sane]

Yes, it needs to be tested.

 

Since the path is "relative" I am assuming that 

changes=/ISOs/slax/

has the same root as 

from=/ISOs/slax-English-US-7.0.8-i486.iso

 

BUT it may well be needed to prepend to it an actual device path as an example:

changes=/dev/sda1/ISOs/slax/

 

or (maybe) something like passing also a root to the device-by-uuid path:

http://reboot.pro/to...-from-grub4dos/

 

 

Wonko