Slitaz rolling (or 5.0 RC2) updates and applications are gone after reboot

SliTaz Forum » English Support » Live and installation

Slitaz rolling (or 5.0 RC2) updates and applications are gone after reboot

(6 posts) (3 voices)

Started 9 years ago by jujunet
Latest reply from mojo
This topic is resolved

Tags:

No tags yet.

jujunet

offline
Member

Hello,

I have installed Slitaz on the USB key with the following command :
"tazusb gen-iso2usb /home/slitaz-rolling.iso"
the "home" parameter is correctly set with the partition UUID to save the data in correct location (USB partition).
The partition that host the system is ext3

I have installed firefox (official) and made a slitaz modules upgrade.
and before shutdown the system I made a tazusb writefs (with compression none).
the file /boot/rootfs.gz is updated.

But after the reboot, application and updates are gone.
System status is back like after the first install.

Is someone has already encountered that ? how can I fix this issue : keep applications and updates ?

Thanks

Jules.

Posted 9 years ago #
az_ua

offline
Moderator

tazusb writefs only creates /rootfs.gz in RAM.
You have to replace file written while tazusb gen-iso2usb by this new one.

Posted 9 years ago #
jujunet

offline
Member

Hello,

Thanks for you feddback.
the file rootfs.gz written by the [code]tazusb writefs[/code] is located in the /home/boot of the Slitaz system. (in boot directory of the usb key when the system is off)

It seems that the rootfs.gz is not loaded at startup.

How to force this file loading a boot ?

Thnaks.

Jules

Posted 9 years ago #
mojo

offline
Key Master

If your using the syslinux bootloader:
Modify /home/boot/extlinux/extlinux.cfg to boot rootfs.gz packed by tazusb writefs.

Info: http://forum.slitaz.org/topic/slitaz-40-liveusb-writefs#post-9261

@az_ua
rootfs.gz remains at / on ramfs if /home is not mounted to a writable partition
tazusb:
mv /rootfs.gz /home/boot/.
else
gettext "rootfs.gz is located in /"; echo ""

Posted 9 years ago #
jujunet

offline
Member

Thank you Mojo.
it is exactly what I was searching.

I prefer the "packages" solution instead of packed "rootfs" solution because I can keep hand on what it is installed on the system. (even if the solution is a little more slower at boot).

With the "package" solution I have seen that:
- at boot when applications are installed, it tries to get module update before the network is initialized
- some updates are not taken into account if tazpkz are copied in package (syslinux, syslinux-extra, slitaz-boot-scripts)

Thanks

Posted 9 years ago #
mojo

offline
Key Master

- at boot when applications are installed, it tries to get module update before the network is initialized

Tazpkg package script is trying to auto install the depends for the tazpkg it is currently installing. We don't want the depends tazpkgs downloaded from the internet, we already put them in /home/boot/packages folder and they will be installed before the loop script is done.
http://hg.slitaz.org/slitaz-boot-scripts/file/d51fd6bbb28e/etc/init.d/bootopts.sh#l133

- some updates are not taken into account if tazpkz are copied in package (syslinux, syslinux-extra, slitaz-boot-scripts)

The root filesystem must be mounted before packages and files can be written to it.
Therefore it is not possible to modify or replace the boot scripts or files if they are required to mount the filesystem using this method. If files are in a subfolder of /home such as syslinux or the kernel which are in /home/boot modified/added files and folders are saved by being written to the mounted writable partition designated in kernel line by home=

Posted 9 years ago #

RSS feed for this topic

Reply

You must log in to post.