SliTaz Forum
You are not logged in.
Pages: 1
Hello everyone,
I am new here, and to SliTaz. So far i love it, it's very portable fast and well ... great! But I am have a problem, that i realy want to fix:
I have gone through many topics, but none of them are in the same condition as me.
I am trying to multiboot SliTaz 4(not the cooking version)using YUMI
With a FAT32 pen drive
There are so many methods out there but I'm confused which one would work.
**Should "X:\multiboot\slitaz-4.0\boot\isolinux" be change to "X:\...\boot\syslinux" ?
** and inside that folder should i change "isolinux.cfg" to "syslinux.cfg" ?
Thanks in advance.
*Ducklin5*
Offline
If you want persistance where /home is mounted on the flash drive you must format in a linux filesystem. If you use fat,fat32,or ntfs a regular user will not be able to log into an xsession.
http://doc.slitaz.org/en:guides:liveusb
See the thread here for syslinux menu entry for persistence:
http://forum.slitaz.org/topic/slitaz-40-liveusb-writefs
My post #7 in thread that begins with:
If your booting slitaz-4.0 on SD card with the orange slitaz boot menu you have to modify /home/boot/extlinux/extlinux.cfg to boot rootfs.gz packed by tazusb writefs.
Offline
Thanks for the speedy reply.
I am able to log into a the session now as it is, and if i install it with tazusb will its still be multiboot
Offline
if i use home=UUID i am unable to login to tux, but i can only login to root
if i use initrd=/multiboot/slitaz-4.0/boot/rootfs.gz then i get a command line and alot of drivers are not found
If i use initrd=/boot/rootfs.gz,/boot/rootfs4.gz,/boot/rootfs3.gz,/boot/rootfs2.gz,/boot/rootfs1.gz [http://superuser.com/questions/123399/how-to-make-slitaz-usb-persistent]
doesnt work well either
Offline
No,installing with tazusb will overwrite YUMI bootloader and break multiboot.
if i use home=UUID i am unable to login to tux, but i can only login to root
If you want persistance where /home is mounted on the flash drive you must format in a linux filesystem(ext2 or ext3). If you use fat,fat32,or ntfs a regular user will not be able to log into an xsession.
Offline
so, what you are saying is that, i can use home=UUID if my usb was ext2/ext3 and i can use the rootfs.gz method even if my usb is fat32?
Offline
home=UUID mounts /home to the flash drive.
If the flash drive is formated with fat,fat32,ntfs Xorg authentification fails for a regular user, /home/tux can't login. Root can login because it's home folder is /root which is running in memory and not mounted to the flash drive so authentification succeeds. The rootfs.gz is a tarball so it can reside on any filesystem,it is extracted and runs in memory and not mounted on the flash drive.
Puppy linux is installed and provide persistance on fat32 by saving all files as a tarball before they are written to fat32 flash drive,on boot the tarballed filesystem is extracted to memory .
Offline
Okay, so my only option is is to save it as a rootfs.gz, got it! 
Offline
Try it and see what happens.
Offline
i add rootfs first and the rest after like this:
initrd=/boot/rootfs.gz,/boot/rootfs4.gz,/boot/rootfs3.gz,/boot/rootfs2.gz,/boot/rootfs1.gz
i tried running it in qemu, and i got command line. when i booted it normally, it looks normal but the top & bottom bars disappear after a second or so.
Offline
i plugged the thumb drive into a different computer and it work,but... the wireless network drive doesn't seem to be installed. if not for these installation problems, slitaz would have been great. Im still not giving up on it though
Offline
Pages: 1
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]