SliTaz Forum
You are not logged in.
Thx Aleksej but sorry to say that it not workin ... i did delete the packages one by one using this iso
http://pizza.slitaz.me/?id=20150315-5401
your iso is smaller than mine ...what method do you use to create this iso?
In my custom iso after installing others packages that i save in my flash and run 'startx' and then it workin but your version say cannot open application.conf something like that ...so i copy applications.conf from workin iso to yours then it workin but then i get something like uuid error when try opening firefox ... it not happen with other app 'alsamixer'...
thnx in advance.
Offline
Now its workin haha ...gogling about that uuid error then found this
http://www.torkwrench.com/2011/12/16/d-bus-library-appears-to-be-incorrectly-set-up-failed-to-read-machine-uuid-failed-to-open-varlibdbusmachine-id/
i just run the code then viola that solve my firefox problem to start ... thanks Aleksej for the real smallest version.
Offline
Hi apache,
Thank you for dbus-uuidgen hint, I'll try to implement it later.
Sorry, I haven't enough time to describe you process creating custom ISO. Only in short.
My host machine running SliTaz Rolling, and I use latest tazpkg.
1. [c]mkdir -p /tmp/packages[/c]
2. Download specified packages to [c]/tmp/packages[/c]
3. Generate rootfs: for each package run command:
[c]# tazpkg -i /tmp/package/.......tazpkg --root=/tmp/rootfs --nodeps[/c]
4. Clean rootfs: remove package cache and clean /var/lib/tazpkg (leave only 'installed*', 'blocked-packages.list', 'mirror', 'mirrors').
5. Compress rootfs:
[c]cd /tmp/rootfs; find | sed 's|^./||' | busybox cpio -F /tmp/rootfs.cpio -H newc -o[/c]
[c]lzma e /tmp/rootfs.cpio /tmp/rootfs.gz[/c]
6. Get regular SliTaz-4 ISO, open it in the ISO Master; remove original rootfs.gz, put there new rootfs.gz, save ISO image.
Offline
Thanks again it will useful for next time i want create custom iso but for now i just use your iso.
And about that uuid error i add the code in autostart.sh so i dont need to run it manually.
Offline
Bump;
Hello guyz my base rootfs have 4 packages install;
busybox
glibc-base
slitaz-base-files
slitaz-boot-scripts
I want to ask here it is possible to exclude any one of those packages from the rootfs to save more byte for my rootfs and then it can be extract/install it during boot time?
Thanks in advance.
Offline
I don't quite understand how useful it would be. Indeed, they are mandatory, for sure. So you will always have to extract them at boot from your boot device. So you will never save space nor boot time. What do you think?
Offline
Keeping only needed files for machine to boot is my goal... it not taking much time to extract them btw.If you know which one can be remove let me know yea.
Offline
As I said, you need all of them for a working machine. So why strip them off rootfs if only to have to extract them every time?
Have a look at the receipt of these packages ( http://pkgs.slitaz.org ), you'll find they cannot be removed (strangely enough there is no rule to prevent this for slitaz-boot-scripts, but this package holds /etc/init.d/rcS which is the main boot script!).
BTW, you don't have tazpkg listed. How do you install packages during boot? Did you copy the "install" code from tazpkg to a custom boot script?
P.-S.: if you like, you may be able to remove /parts/ of these packages, e.g. docs and localization files from slitaz-base-files. Be aware that deleted files will come back if you upgrade the package, though.
Offline
I know all those packages are must include but is it all of the files really needed for boot time? example i remove boot-script then slitaz cannot boot coz unknown partition.
I copy tazpkg to base first then install others packages easy 
I use slitaz as live so no need to worry about update files etc.
Offline
Let's see the file lists on pkgs.slitaz.org...
- busybox: everything in bin/ dirs is links to busybox, so they take almost no space (this is counted in bytes, literally). You could remove /usr/share/applications/*, /var/www/httpd/404.html. In /etc/init.d, you have to choose on your own, I can't know which services you need (do not remove httpd, tazpanel relies on it; or you don't want tazpanel either?)
- glibc-base: maybe you can remove /usr/share/i18n/locales. As for libraries (the .so files), this is too much work for me to do it for you, but here's a procedure: for each executable file in your system, run [c]ldd[/c] on it. E.g.: [c]ldd /bin/busybox[/c]. This will list needed libs, which you cannot remove. Note that in the file list there are "doubles" like /lib/libdl-2.14.1.so and /lib/libdl.so.2; the second one is a simple link.
- slitaz-base-files: not sure about /etc contents; maybe /etc/motd (146 bytes). Maybe /usr/bin/*. httphelper? Dunno. Probably /usr/share/*. Maybe /var/www if you don't use tazpanel.
- slitaz-boot-scripts: README, desktop file, maybe /usr/share/slitaz/network.conf_migration .
Don't hesitate to do your own tests! As long as you keep a working ISO by your side...
Offline
[ Generated in 0.014 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]