You are not logged in.
Anyway. I did it.
Added rootfs1.gz to boot line, but I get kernel panic:
VFS: Cannot open root device "null" or unknown-block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.37-slitaz #2
Offline
that was your bootline?
initrd (hd0,0)/boot/rootfs.gz (hd0,0)/boot/rootfs-1.gz
Offline
initrd=/boot/rootfs.gz,/boot/rootfs1.gz rw root=/dev/null vga=normal autologin home=f6b89c11-13b7-4739-b0e8-a113a44ac73e lang=en kmap=uk
(Im running live-usb)
Offline
did you check with 4 in1 iso - I think there is no , in between
Offline
there is.
Offline
isolinux/syslinx/extlinux: with ,
kernel /boot/vmlinuz
append initrd=/boot/rootfs.gz,/boot/rootfs1.gz rw root=/dev/null vga=normal autologin home=f6b89c11-13b7-4739-b0e8-a113a44ac73e lang=en kmap=uk
grub4dos*: without ,
kernel /boot/vmlinuz rw root=/dev/null vga=normal autologin home=f6b89c11-13b7-4739-b0e8-a113a44ac73e lang=en kmap=uk
initrd /boot/rootfs.gz /boot/rootfs1.gz
Offline
Before, I was adding rootfs1.gz to boot line manually.
This time, I edited extlinux.conf.
Success! System boots up!
Warzone was 'instelled' but it didnt launch because of missing sdl.
I installed sdl package, tazusb write, reboot and... KERNEL PANIC!
Now I'm posting this from Debian because my Slitaz system is non-bootable.
(I moved /home from pendrive to hard disk and after that each time I performed writefs, I had to move 'new' rootfs.gz manually from / to /media/pendrive/boot overwriting old rootfs so there is no 'previous.gz' to go back with. Stupid me.)
Offline
I will start from scratch (slitaz-4.0-gtkonly) but I think I will give up matryoshka system - too much work, time, downloading - It would only make sense if I created separated rootfs for every game - rootfs-warzone, rootfs-assaultcube etc. But then rebooting,reboting,rebooting.
I will stay with keeping 'big' packages in /home - so I can install quickly programs (even offline) without reboot.
Thanks for support!
Martin
Offline
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]