SliTaz Forum
You are not logged in.
Pages: 1
hey guys,
im wondering what part of the filesystem tazusb writefs packs into the rootfs.gz file.
the issue im having:
ive use a rootfs.gz, uncompressed (loads faster). its around 444 mb, still using kernel 3.2.52
today i updated all of my packages (got the new kernel too) and shifted vmlinuz-3.2.71 to relace my bzImage
rebuilt rootfs.gz, but now its 487 mb of size. is it possible these 43 mb came solemnly through updates?
or is there some other part of the fs which gets included with tazusb (logs or similar), which could possibly have grown a lot since the last execution of tazusb?
thanks!
Offline
Hi K3nn3th,
Did you clean the cache after the update?
Offline
Also, updates may have pulled new packages as dependencies.
ive use a rootfs.gz, uncompressed (loads faster)
Not sure. Usually the bottleneck is the reading rate of the USB device. Note that uncompressing is much faster than compressing. But maybe you did some tests and measured the boot times?
If so, I would be glad to read them! (Specify what kind of device and computer you used.)
Offline
i am booting frugal installs from my hard drive in daily use, occasionally from a usb key.
my hdd-frugals should boot asap 
uncompressing the rootfs.gz file (gzip/lzma) takes longer than just shoving the contents of the archive stright into place.
im using a toshiba satellite t130-10g (been serving me well for years now!)
some of the stuff im doing (realtime audio manipulation using xwax/mixxx) runs faster with frugal installs, which i think makes sense regarding the difference in latency between hdd/ram
Offline
Yes, from an internal HDD it's faster.
(For your USB use you may want to try compressed rootfs there.)
Offline
Pages: 1
[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]