SliTaz Forum

aledie

Member

Registered: 2018-02-21

Posts: 58

Rolling-core64 - rootfs.gz saved to / instead of /home/boot

Hello, a little inconvenience, with slitaz-rolling-core6.iso install (ext3 or ext4 partition on an usb), When using saving changes from desktop menu (lzma, haven't tried others), rootfs.gz is created in / (while I suppose it should be then automatically copied to /home/boot backing up and replacing the existing gz file, what doesn't happen). When using slitaz-rolling.iso (32 bit) install to the same usb partition, everything works just fine. Some bug in the script of 64bit Version!?

aledie

Member

Registered: 2018-02-21

Posts: 58

Re: Rolling-core64 - rootfs.gz saved to / instead of /home/boot

Hello, the same problem still exists:

-Installed latest Rolling-core64 iso with "Create a LiveUSB" to an ext2 (same result with ext4) partition.

-'tazusb writefs lzma' creates rootfs.gz file in '/' instead of '/home/boot/'

mojo

Administrator

Registered: 2011-03-29

Posts: 2,173

Re: Rolling-core64 - rootfs.gz saved to / instead of /home/boot

tazusb conditional fails for /home/boot/bzImage on 64bit kernel which has /home/boot/bzImage64

When conditional fails fresh rootfs.gz is written to /

Boot slitaz,open terminal,verify /home is mounted to flash drive:

[c]touch /home/boot/bzImage[/c]

Conditional should succeed and fresh rootfs.gz will be written to /home/boot

aledie

Member

Registered: 2018-02-21

Posts: 58

Re: Rolling-core64 - rootfs.gz saved to / instead of /home/boot

@mojo - thanks for the advise

Tried it - unfortunately doesn't work on core64 (also tried on 32 bit version - same).

I have a frugal install currently on a ext4 partition, booting with grub4dos 1.7.

Few weeks ago I also tried installing from inside slitaz to a Live USB (ext2-4, with same failure). I recall it all worked perfectly (at least on core32 I used then) before the switch to the new kernel half year ago.

Attach the complete screenshot of what i tried today, hope it may help to figure it out somehow.

[attachment=46668,2721]

mojo

Administrator

Registered: 2011-03-29

Posts: 2,173

Re: Rolling-core64 - rootfs.gz saved to / instead of /home/boot

@aledie

You entered the wrong command.

Type this and hit Enter:

[c]sudo touch /home/boot/bzImage[/c]

Before you run

[c]sudo tazusb writefs lzma[/c]

aledie

Member

Registered: 2018-02-21

Posts: 58

Re: Rolling-core64 - rootfs.gz saved to / instead of /home/boot

Thanks, mojo! it works now

my wrong earlier was to input actual kernel name used bzImage64.

Another way to fix the problem is just renaming the kernel (sudo mv /home/boot/bzImage64 /home/boot/bzImage) and editing bootloader's menu.lst.