SliTaz Forum
You are not logged in.
Pages: 1
hi all,
my first post here 
ok im trying to use slitaz on a 500Mhz thinclient. the problem is the flashdisk installed is 128mb and not replaceable! so thats also why i did choose for slitaz 
i am trying to hack the rootfs.gz but something so far so good. but now i wanted to add packages to the extracted rootfs dir. i did notice the option --root= can i use this option to point to my hacked/rootfs dir so that when i boot form the compressed rootfs.gz with my packages installed ?
i did try this once but after compiling the rootfs.gz the system wants booting anymore 
Offline
as my first post is a pretty mess (dont know why) i wil explane it again (because the edit button is not there anymore) and add some stuff i figured out!
im trying to extract the rootfs the install a few packages with tazpkg pkgname --root=/tmp/hacked/
but when i am trying to boot from my new compressed file i some weird stuff on screen and the system hangs (no kernel panic message is displayed)
i figured out that this is not happening with all the added packages!!
compressed with x11vnc or synergyc there semes to be nothing wrong.
when compressing with enna and mplayer (plus deps) it crashes.
Offline
Hi Try gzip compression instead of lzma.
Offline
i did not try that. but it is strange that it only happens with enna or mplayer.
im recompressing the stuff with only mplayer to hopefully discard that one.
when that is tested im going to use the gzip as compression =]
tanx for the reply
edit:
compressed with mplayer installed the system was not bootable
doing a quick check with only enna. and then last check with gzip
[c]EDIT[/c]
omg you are awnsome. gzip did indead fix the problem. is there a goot explanation why lmza does not deal well with certain packages?
Offline
Hi,
Wich packages repository are you using ? I have moved away enna from cooking a few weeks ago since it build is buggy.
And how exactly are you recompressing the rootfs. Do you use SliTaz tools such as tazlito ?
Offline
hi pankso,
i am using the stable version of the live disk. (3.0) because the new version seems to have dropped support for the AMD geode chipset. im going to try to get the cooking version to work when my first stable build is completed and ready for use.
to decompress and compress im useng the documentation of hacking slitaz.
something like (zcat rootfs.gz 2>/dev/null || lzma d rootfs.gz -so) | cpio -id
for decompressing
find . -print | cpio -o -H newc | lzma e -si -so > ../rootfs.gz
for lzma (which gives me problems with enna and mplayer)
find . -print | cpio -o -H newc | gzip -9 > ../rootfs.gz
for gzip (which runs fines with enna en mplayer yesterday)
for now i will use gzip instead of lzma, gzip uses more space but decompresses al lot faster then lzma in my experience. so less space more boot pleasure
Offline
Hi,
Yes for sure gzip is faster! You said "new version seems to have dropped support for the AMD geode chipset". Latest cooking 20110531 ? If you boot you got kernel panic ? If it's a screen problem you realy should try the ISO I did yesterday with Xorg light:
http://mirror.slitaz.org/iso/undigest/slitaz-xorg-light.iso
Offline
ok i will try to boot coocked version again in a few minutes to se wat is realy going on.
and for sure i will try you xorg-light.iso
edit:
did not try the coocked but instead i used your xorg-light version. but im pretty sure they generate the same problem.
i have uploaded the xorg logs because i cant make a thing out of it.
i also used tazx but then i get an other warning:
number of screens does not match created devices
Offline
uploaded the logs:
and also i need to say that i was wrong about slitaz dropped support for geode.
i noticed the drivers where loading while booting (my bad)
Offline
Pages: 1
[ Generated in 0.019 seconds, 11 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]