![]() I'm only guessing, though, but I'll take it. Now that the creation of the stick is slightly different, regards the building sequence, unetbootin may have stabilised itself to recognise just one OS. If the stick is plugged into a computer, the file manager will open up two notifications, one being the system and the other the casper-rw partition. This might have something to do with our discussion on unetbootin thinking there are two systems/partitions. Having mentioned the triple unetbootin menus previously, I've now noticed that this new stick is now booting only one instance of the unetbootin menu before the feather logo, so that's a win. So the lesson here for the time being, is to avoid using gparted to resize partitions, only use it to create them. Proof of this, is my success a short while ago, in resurrecting an old 8gb Silicon Power stick that was giving me all sorts of trouble, including hanging and running slow.This was always a slow stick when new, but it is now quite snappy and useful. I agree that the system appears to get confused with 2 instances of casper-rw and lack of space in the fat32 part to initially set it all up. The gparted method, by firstly creating a fat32 WITH nominal persistence space AND naming the ext2 part AFTER, seems to do the trick. I think we are in agreement now, judging from both our experiences. Indeed, the snappiness of menus, updates, installs and usage is on a par with an installed system. Have installed many new programs on these sticks and all are quick. So Unetbootin is smart enough to use the balance of the partition for persistence. This worked and the final persistence file came out as 157.3Mb, which was deleted after naming the ext2 partition. I made a fat32 of 1.25Gb and set Unetbootin to create a persistence of 200Mb. Unetbootin, on the other hand allows any persistence size from zero. In some cases booted fine, but resulted in stuttering, hanging or just plain painfully slow. That is, if the pre-built fat32 is say 1.8GB, the stick will finish, but with a fatal error and won't boot properly. The fat32 partition imho, must need some wiggle room to organise the install before finishing off with the ext2 partition labeling and deletion of the original casper-rw partition.Īlso Startup Disk Creator only allows a minimum of 1GB persistence and crashes if this amount is not available. Have stopped using Startup Disk Creator, as it also seems to be part of the problem, together with the Gparted resizing glitch. So, the command you'd need to write with the latter would be something like “tazusb gen-iso2usb /media/disk/slitaz.Have now successfully made 3rd live USB with LL2.4. If the source file is found on an external hard disk, mention the folder in which the media's files are outputted to - check this with PCManFM (in practice the folder can be something like /media/disk). If it is located at /home/tux (while running slitaz from a non-live version), write “tazusb gen-iso2usb /home/tux/slitaz.iso /dev/sdxx”. Note that the /dev/sdxx part of the command above specifies the location to where you need to write the iso's files to it is not the source media where the iso is on ! With the iso file as install source option, you should hence specify the exact location where the slitaz iso source file is located. Iso file as install source # tazusb gen-iso2usb slitaz.iso /dev/sdxx LiveCD as install source # tazusb gen-liveusb /dev/sdxx Verify the install target, format will delete everything. ![]() Download > Burn > Boot a SliTaz ISO image
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |