SliTaz Forum
You are not logged in.
Pages: 1
So the rootfs.gz is now saved in /
Will this new file be the one booted from if I reboot? (I'm not used to it being saved there).
Also where is the Boot directory for making changes to Isolinux/syslinux.cfg for changing boot options?
And how do I run Pcmanfm in SU mode?
I think once I know these things I'll be able to get on with the rest ... 
Offline
Will this new file be the one booted from if I reboot?
Likely, no.
There's some rules (I forgot about) when it appears in the /. But seems you have a little of RAM. And I believe this file will gone after reboot if you will not save it manually...
Also where is the Boot directory
It depends. I have so called "full install", and the boot directory is precise at [c]/boot[/c].
And how do I run Pcmanfm in SU mode?
Go to directory where you want to open PCManFM as root super user. Right-click mouse on the free space, select something like "Open as root" (I don't know the precise wording, because I don't use English, but Russian). Then enter root's password, and voila!
Offline
I have lots of RAM (4GB).
There is no /boot directory in my usb install ... 
How do I save the rootfs.gz file manually and then use it after reboot?
I have found the "Open folder as root" in the right-click menu though .... that was the last place I would have looked ...
Offline
I have lots of RAM (4GB).
Sorry, I have not used boot from USB flash for a very long time, about 5-6 years, and forgot the details...
Sorry again, I can't understand the background of your problem. You have similar messages in few forum topics, but I can't get the whole situation. So let me assume the following:
[*]You make the bootable USB flash;
[*]You boot SliTaz using this bootable flash;
[*]Then you, very likely, change some options and/or install some packages, so you need to save the current state.
[*]You use tazusb to make the rootfs.gz. And this rootfs.gz is appeared on the root of your file system.
I looking the tazusb sources: http://hg.slitaz.org/tazusb/file/tip/tazusb
Your situation is described on the lines 523-537.
So, if you have /home/boot/bzImage while you booting your bootable USB flash, then the new rootfs.gz will be moved to /home/boot/rootfs.gz.
If you haven't /home/boot/bzImage, so the question: how you booted without it?
Offline
If the config file of the Live is syslinux.cfg, the stick is formated FAT16 or 32 -> SliTaz is running in RAM only.
You have to copy manually your new rootfs in /boot of the stick. Don't hesitate to rename the existing rootfs before so you can boot from it modifying the command line at boot screen in case something goes wrong with the new rootfs.
Offline
Ok first .... I was keeping all this in the one related thread but was told by a moderator (totoetsasoeur) to make separate threads ... I know it's more confusing but that's what I was told to do.
@Aleksej ... yes that is the problem ... I DON'T have a /home/boot ... all that is in /home is /home/tux ... nothing else ... even with "show hidden files" ticked too.
The only place I have a /boot is /usr/share/boot.
I'm familiar now with the file system after using and customising 4 since it came out .... I run 4 from an identical flash drive.
But I'm stumped with 5 ... so much trouble trying to install it too USB.
What is the recommended method for installation to USB for the latest rolling core? There has to be an easier way ... I've been at this for about 10 hours now ... tried every method and application I could find from Linux and Win7 and kept getting the three errors detailed in this thread:
http://forum.slitaz.org/topic/slitaz-live-flash-drive-usb-installation-fails
@Ceel ... I would if I could find it ...
Offline
@TracE,
No offense, but you can not expect efficient help if you keep messing around. I know it is difficult and frustrating to keep trying when getting errors for hours...
The topic you are referring to, is about installing a live version from windows
http://forum.slitaz.org/topic/slitaz-live-flash-drive-usb-installation-fails
I advised you to make separate topics because I deeply think this is the only way to clarify the situation, get efficient help and improve slitaz.
Here again, I mean in this topic, you are asking more than one question. Why don't you give/write the steps to reproduce and the error you get?
Don't get me wrong, I just wanna help.
Happy slitaz.
Offline
@TraceE
If your stick is FAT, you'll find syslinux.cfg in the /boot directory of the stick.
Open the file manager, click on the device corresponding at the stick, right click on /boot, open as root to modify files
or
in a terminal as root
[c]mount /dev/sda1 /mnt[/c] (this supposes your stick is detected as sda)
[c]leafpad /mnt/boot/syslinux/syslinux.cfg &[/c] if you need to edit the file.
Offline
Nobody is messing around ... Aleksej is finding it difficult to follow (post#4) as he thinks I am spreading it out over multiple posts and totoetsasoeur is telling me to start different threads so I am never going to keep everybody happy but I am not messing around.
totoetsasoeur ... I actually followed your original post to install from windows and got the same errors under the same circumstances. Apart from when I used Win32 Disk Imager this installed and boots perfectly but I have no /home/boot directory and any further rootfs.gz files created with tazusb writefs appear in / and do not persist to next boot. I cannot find a /boot directory anywhere apart from /usr/share/boot but that does not contain the original rootfs.gz.
I also followed the advised Slitaz wiki method for installing from Slitaz using an .iso (formatting flash drive to ext3, tazusb gen-iso2usb and using the correct path to file and destination) but that failed everytime as it was always looking for some files from a live cdrom (which of course wasn't there) and resulted in boot loops.
The solution that works for you (changing .iso to .exe and following correct instructions) produces a black screen with flashing cursor for me.
I checked and the .iso md5 matches so is not corrupt.
I'd actually be really happy with the way it works now if I could only find a way of adding the applications I want and saving. I don't need permanent persistence ... I just need to be able to add the applications I use often ....
If you give me specific instructions I will follow them and report back results ...
Offline
@Ceel ... The "stick" does not show up in the file manager. It would normally be identified as sdb1.
When I open Gparted for a look at the "stick" ... I get this Libparted error: "Invalid partition table - recursive partition on /dev/sdb" and the "stick" shows as Unallocated. I am guessing this is why I can't find/see /home/boot.
Does that help in any way?
Some more info .... this was installed with Win32 Disk Imager (the only windows app I could get to install it) and the "stick" was formatted fat32 before installation.
Offline
@TraceE
I guess the problem comes from Win32 Disk Imager. Maybe you can overwrite your Live and do a new one?
[*]Boot from the stick.
[*]Download the last SliTaz core ISO.
[*]Open a terminal as root and format the stick:
[c]tazusb format[/c]
[*]type [c]list[/c] to be sure your stick is really sdb1; then enter the device [c]/dev/sdb1[/c] and hit [Enter] (for a stick choose ext2 format).
[*]Create the live:
[c]tazusb gen-iso2usb path/to/slitaz-rolling-core.iso /dev/sdb1[/c]
You have now a LiveUSB with persistence in /home and you can access to extlinux.conf (not syslinux.cfg because the Live is formated EXT2) in /home/boot/extlinux.
Offline
Hi Ceel ... I have tried that a few times already as detailed in the earlier post above:
"I also followed the advised Slitaz wiki method for installing from Slitaz 4 using an .iso (formatting flash drive to ext3, tazusb gen-iso2usb and using the correct path to file and destination) but that failed everytime as it was always looking for some files from a live cdrom (which of course wasn't there) and resulted in boot loops."
Every time it looks for a live cd even though I am using the correct command.
Do you think changing the format to ext2 will change this?
What I am in the middle of doing right now is trying what bellard has suggested to totoetsasoeur (change .iso to .exe and install from windows) ... this failed for me before but I can't remember the error so I'm doing it again and will report back on the other thread ...
Offline
it was always looking for some files from a live cdrom
Strange. Sure you used [c]tazusb gen-iso2usb[/c]? Maybe you confused with [c]tazusb gen-liveusb[/c]?
Offline
I tried it carefully several times to make sure that I was using the correct commands.
Offline
Just did it again:
tux@slitaz:~$ su
Password:
root@slitaz:/home/tux# tazusb gen-iso2usb /home/tux/slitaz-rolling-core.iso /dev
/sdc1
Copy ISO file to SliTaz LiveUSB media
===============================================================================
Mounting slitaz-rolling-core.iso...
Installing a new MBR to: /dev/sdc [ OK ]
Setting /dev/sdc1 as bootable... [ OK ]
Mounting USB target device...
Copying needed files from cdrom... [ OK ]
Installing bootloader: extlinux
/media/flash/boot/extlinux is device /dev/sdc1
cp: can't stat '/media/cdrom/boot/isolinux/*.txt': No such file or directory
cp: can't stat '/media/cdrom/boot/isolinux/*.kbd': No such file or directory
===============================================================================
Do you want to exit Tazusb or reboot system (Exit/reboot) ?
On rebooting I get the error:
Syslinux 4.05 EDD 2011-12-09 copyright (c) 1994=2011 H. Peter Anvin et al
vesamenu.c32: not a com32R image
Boot:
And this just repeats down the screen every few seconds.
Offline
Ok I have resolved this now ... I fixed the above error by using 7zip to extract c32box.c32 and vesamenu.c32 as advised by others on another thread.
Thanks to all for your suggestions and time though ...
I have read that this error was happening because I have used an older distro (Slitaz 4 stable from 2012) to make the USB install as it contains and obsolete version of extlinux.bin?
Offline
c32 compressed files support was introduced Tue Dec 29 08:59:31 2015 +0100
http://hg.slitaz.org/wok/rev/ef4ed701a27f
Offline
Pages: 1
[ Generated in 0.018 seconds, 7 queries executed - Memory usage: 1.57 MiB (Peak: 1.77 MiB) ]