You are not logged in.
The kernel panic issues from previous posts appears to be corrected with tazusb rootfs.gz, but tazpanel doesn't start AFTER a tazusb writefs operation. Tazpanel can be made to run again by two step stop/start of the service. However, '/etc/init.d/tazpanel restart' does not work.
Also, boot log shows an error starting the message bus daemon:
[c]DBUS... Failed to start message bus: The pid file "/var/run/dbus/pid" exists, if the message bus is not running, remove this file[/c]
edit: I forgot to mention that this occurs with the latest bootscripts package pulled, and no other packages installed beyond core.
Offline
This fix excludes pids from list of contents copied from running filesystem to new rootfs.gz
Same issue with [c]tazusb writefs[/c] and [c]tazlito writeiso[/c]
Add whats in bold below
tazusb version 4.2.4 line 477
tazlito version 5.2.2 line 2293
[c]find bin etc init sbin var dev lib root usr home[/c] ! -iname *pid[c]>/tmp/list[/c]
Offline
Thanks mojo. Confirmed fix for tasusb. Shall I post the bug or will you push the fix on hg?
I did not add the home directory to the file list like you illustrate above, however. Besides user files, That would add the /home/boot menu and thus build rootfs.gz and previous.gz into the archive, wouldn't it?
Offline
Ah, nevermind, I see a fix has been posted (http://hg.slitaz.org/tazusb/rev/0ffa8faa4b1a). Thank you again.
Offline
[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]