SliTaz SliTaz Forum

You are not logged in.

#1 2016-11-08 16:36:44

rayshadowsun
Member
Registered: 2016-11-08
Posts: 4

Why does "tazusb writefs" insist on putting "rootfs.gz" in " / " and n

Hi, I've been trying and trying for days now to understand why "tazusb" keeps insisting on putting newly created rootfs.gz files in the " / " directory which is part of the rootfs it did just copied. I've read plenty on this forum, the old forum, wiki and so on. But I can't figure it out my self. 

I have set "home=/dev/sda5" in my grub.conf (I'm using grub2win), I've tried using the partitions UUID but no change. The home is however set correctly it seems because my changes to files in my home directory is saved even if I don't do "tazusb writefs" ANd the bootlog says that home is set to "/dev/sda5" and that home is mounted there.

I wan't tazusb to put the newly created rootfs.gz in "/home/boot/ and also to rename the previous one. Like it's suppose to do.

I'm storing my kernel (64-bit) and rootfs.gz files in "/home/boot/" on "/dev/sda5" which is as you understand the 5th partition on my main SSD. I've formatted it to ext4 and the table is GPT. I've tried with ext3 filesystem but no change.

Is this simply because it's a "hard drive" and not a USB-stick? If so can I fool "tazusb" to believe it's a USB-stick? Maybe it's because it's gpt and not mbr?

Well any help is welcome!

PS. tanks to the people behind Slitaz, it's grate!

Offline

#2 2016-11-08 16:39:09

rayshadowsun
Member
Registered: 2016-11-08
Posts: 4

Re: Why does "tazusb writefs" insist on putting "rootfs.gz" in " / " and n

From my grub.conf

"######################################################################################################

#  Menu Entry 1       Slitaz rolling core64 modded

#

menuentry   'Slitaz rolling core64 modded'   --class other   --class icon-linux   --class custom_001  {

#

# start-custom-code

set root=hd0,5

linux /boot/bzImage64 rw root=/dev/null home=/dev/sda5 vga=normal lang=en_US kmap=se

initrd /boot/rootfs.gz

# end-custom-code"

Bootlog:

ln: /dev/cdrom: File exists

Switching / to tmpfs...

                                                                      [ Done ]

Processing: /etc/init.d/rcS...

Mounting proc filesystem on /proc                                     [ Done ]

Mounting devtmpfs filesystem on: /dev                                 [ Done ]

Starting udev daemon...

Udevadm requesting events from the Kernel...

Udevadm waiting for the event queue to finish...

Remounting rootfs read/write...

Mounting filesystems in fstab...

Searching for early boot options...                                   [ Done ]

Cleaning up the system...                                             [ Done ]

Mounting usbfs filesystem on: /proc/bus/usb                           [ Done ]

Starting system log daemon: syslogd...                                [ Done ]

Starting kernel log daemon: klogd...                                  [ Done ]

Triggering udev events: --action=add                                  [ Done ]

Processing: /etc/init.d/bootopts.sh

Checking for SliTaz cmdline options...

Home has been specified to /dev/sda5...

Mounting /home on /dev/sda5...

Setting system locale to: en_US.UTF-8                                 [ Done ]

Setting system keymap to: se...                                       [ Done ]

Processing: /etc/init.d/system.sh

Setting system locale: en_US.UTF-8                                    [ Done ]

Loading console keymap: se                                            cannot open file se

[ Done ]

Activating swap memory...                                             [ Done ]

Starting TazPanel web server on port 82...[ Done ]

alsactl: init:1758: No soundcards found...

Processing: /etc/init.d/network.sh

Loading network settings from /etc/network.conf

Setting hostname to: slitaz                                           [ Done ]

Configuring loopback...                                               [ Done ]

Starting udhcpc client on: eth0...

udhcpc (v1.23.2) started

Sending discover...

Sending select for 192.168.1.168...

Lease of 192.168.1.168 obtained, lease time 7200

deleting routers

adding dns 8.8.4.4

adding dns 8.8.8.8

Processing: /etc/init.d/local.sh

Starting X environment...

Starting message bus daemon: DBUS...                                  [ Done ]

Starting all daemons...

Setting up kernel security rules... [ Done ]

WARNING: IPtables rules are disabled

httpd is already active.

Starting ntpd daemon: ntpd...                                         [ Done ]

Welcome to your box

Offline

#3 2016-11-08 18:43:16

az_ua
Moderator
Registered: 2014-05-02
Posts: 284

Re: Why does "tazusb writefs" insist on putting "rootfs.gz" in " / " and n

Seems "Usage" shown by tazusb command is outdated, try

[c]tazusb writefs none /path[/c]

or

[c]tazusb writefs lzma /path[/c]

And do NOT try gzip, it have bugs, you've been warned.

> " / " directory which is part of the rootfs it did just copied

No, it is not part of it:

http://hg.slitaz.org/tazusb/file/5ddaf19fb1af/tazusb#l486

Offline

#4 2016-11-09 05:29:49

rayshadowsun
Member
Registered: 2016-11-08
Posts: 4

Re: Why does "tazusb writefs" insist on putting "rootfs.gz" in " / " and n

Thanks az_ua!

I see, good, I was hoping for such a function I will use it.

If there is a way to make "lines 523-534" in tazusb to work that would be more comfy for me.

Do you know or have any idea as to why it's not working? I guess you'd need more info, but I don't know what logs or screenshots you'd want so please tell me if there's anything you need.

Would be swell to get that function working.

Offline

#5 2016-11-10 10:03:14

kultex
Administrator
Registered: 2011-03-28
Posts: 1,175

Re: Why does "tazusb writefs" insist on putting "rootfs.gz" in " / " and n

thats something maybe to think - if you run SliTaz in Ram (what I do - from hd, not usb) and you run tazusb, you run quick out of mem and you end up with a corrupted rootfs.gz.

So I changed in my tazusb the default place to /home/tux/rootfs.gz - because my /home directory has enough GB to take the rootfs.gz. Maybe this should be changed, because when you are a SliTAz beginner, its hard to understand.

you find the tazusb script in /usr/bin and can easy change it wit leafpad as root

Offline

#6 2016-11-11 07:47:39

rayshadowsun
Member
Registered: 2016-11-08
Posts: 4

Re: Why does "tazusb writefs" insist on putting "rootfs.gz" in " / " and n

Thank you Kultex, I'll take a look at the script.

I've done a "normal" install to harfdrive so I can experiment without forgetting to make a new rootfs and losing my "progress" tongue. When I'm done and happy with my setup I'll make a frugal install of it I think.

As az_ua said "tazusb usage" is outdated so changing the script for a new version is a good idea imo.

Thanks again, I really love this distro it fits my needs perfectly and it's so damn amazilngly fast!

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.020 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]