@kultex & other: I'm sorry for my lack of experience here. I have searched my
slitaz 4 installation for tazinstall and found nothing; same with
I tried to review
http://doc.slitaz.org/en:guides:start and found nothing conclusive enough for me to follow.
What I do have found is some clue in
Frugal Install to Windows Partition guide. There, under the title
Tuning the boot process, you can read
title SliTaz cooking
map (hd0,0)/boot/slitaz-cooking.iso (hd1)
kernel (hd1)/boot/bzImage rw root=/dev/null vga=extended lang=fr_FR kmap=fr-latin1 laptop autologin config=/dev/hda1,boot/slitaz.sh
According to it, I could prepare a script with some automated actions to accomplish once the system is loaded.
Would it be a good place to place orders needed to get the system automatically installed in the target computer(s)?
According to my former experience (not with slitaz), once the system autologs in and is ready to execute a script (/boot/slitaz.h, as in the example?), I could execute dd on the target disk with something like:
sudo dd if=/path_to_image/target_image.img of=/dev/sda
sudo rebbot now
and the image would get transferred to the target support, making it bootable in the process (assuming the target_image.img file was obtained out from a bootable disk). Would this work on our slitaz installation? In case it would, I would just launch a LiveUSB from the BIOS and that script would both load our image on the target system and reboot the system out of it.
Of course, I should fight potential dissimilarities between different CompactFlash devices, bringing to differences between dd input file size and output file size. When the second is larger than the first one, the only drawback is a small waste of bytes. When the input file is larger than the available space, a full disk problem occurs, isn't it?
Where do you recommend me to read more on this subject (with slitaz always in mind)?