resolved
kultex
offlineKey Master
as root
tazlito writeiso lzma
take care, that you have a cd in the DVD or loop mount an iso to /media/cdrom
if you wanna use it on other PCs, you should empty /etc/udev/rules.d/persistent-net.rules
http://hg.slitaz.org/tazlito/raw-file/tip/doc/tazlito.en.html
arodulfo
offlineMember
@kultex: After reading your advise to kitty____, and reviewing tazlito usage and manual, I think tazlito writeiso seems to be the best approach for my group.
We are increasingly enjoying SliTaz capability to do what we need with quite low resources needed.
So, let's assume I have generated our particular iso, with all the SliTaz bells and whistles we need it to have (beyond the base install, I mean). Once tazlito ends creating rootfs.gz, it says:
When SliTaz is running in RAM the kernel and bootloader files are kept
on the cdrom. Please insert a LiveCD or loop mount the slitaz.iso to
/media/cdrom to let Tazlito copy the files.
----
ENTER to continue...I installed the system out of a LiveUSB and that's what I have inserted in a free USB port. I reviewed it, to check it was mounted and available and hit ENTER as requested, but I just got the prompt. I'm sure I did something wrong; the question is What?
Please help!
Thanks in advance, for your time and your help.
: How do I get from it to a bootable USB pendrive?
kultex
offlineKey Master
I have the same problem, as I run SliTAz always frugal from the harddisk
what I do:
the iso is not created, but you will finde in /home/sliTaz/ and somewhere down in another directory the created rootfs.gz
open the origila iso with isomaster - it on SliTaz change the rootfs.gz and thats it
sometimes there is an errorwhen you boot the CD, but then you have to redo it...
arodulfo
offlineMember
@kultex: Thanks a lot for your suggestion. I searched /home/slitaz tree branch and eventually located rootfs.gz under /home/slitaz/distro/rootcd/boot/. The, I managed to bring it from the system (so freeing some needed space) out to a PC, where I have isomaster installed.
Run isomaster, open slitaz 4.0 iso and found four rootfsx.gz files.
I explored it a bit and found the isolinux.cfg file, with lots of optional configuration setups for diverse scenarios.
With the new rootfs.gz in hand, what way I should follow to integrate it into the main iso?
I'd like to do respect it, if possible.
Please, advise
Thanks in advance
Kind regards,
kultex
offlineKey Master
take the justx iso - it has only one rootfs.gz
http://mirror.slitaz.org/iso/stable/flavors/slitaz-4.0-justx.iso
arodulfo
offlineMember
After some little review of isolinux.cfg, I understand choosing rootfsx.gz it is not a question of options but one of modularity. Depending on what level of completeness or proximity to the full install you want to be, you select just one of the four available archives (the smallest option) or all the four together (for the core slitaz install).
Assuming I have prepared my rootfs.gz out of a working system, I guess I should add a new option with just that file, so including the new image along the other four, not instead of them, right?
However, I'm a bit confused when it comes to optional details and smaller entries. How do I get to the point a new iso would complement what you, slitaz people, have done?
kultex
offlineKey Master
if you use the justx flaver, you dont have to change anything else - just change the rootfs.gz
mojo
offlineKey Master
rootfs4.gz =base
rootfs4.gz + rootfs3.gz=justx
rootfs4.gz + rootfs3.gz+rootfs2.gz=gtkonly
rootfs4.gz + rootfs3.gz+rootfs2.gz+rootfs1.gz=core
The version of the iso created is what your live system is running determined by either automatic system memory detection or manual selection from the orange boot menu.
arodulfo
offlineMember
@everybody: Thank you all for your contributions.
I have managed to create a new slitaz 4 ISO including my own combination of packages and settings.
Now, I wonder what is the best way (slitaz way) to automate the LiveCD- (or LiveUSB-) to-hard-disk installation process. For systems equal to each other, I would like to have an automated way to deploy the system with minimum or no user intervention.
Any suggestion here?
Thank you so much for your time and for your help.
Kind regards,
kultex
offlineKey Master
look at the tazinstall doku on the iso - you find it under documentation
creat your tazinstall.conf and I recomand in your case to use the isoinstall
thats it
arodulfo
offlineMember
@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 man tazinstall.
I tried to review http://doc.slitaz.org/en:start and 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)
map --hook
kernel (hd1)/boot/bzImage rw root=/dev/null vga=extended lang=fr_FR kmap=fr-latin1 laptop autologin config=/dev/hda1,boot/slitaz.sh
initrd (hd1)/boot/rootfs.gzAccording 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 nowand 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)?
arodulfo
offlineMember
More on the same issue.
Let's sketch the following scenario:
In the original system, namely a 2 GiB CompactFlash, we have a 1900 MiB partition and slitaz is installed there, with all our needed packages and settings.
The target system has a, say, 2000000000 bytes' CompactFlash.
I plan to use dd to get an image of our original system' CF.
I have already assumed it will copy all the partitioned space, plus the MBR and the partition table.
If I use dd to restore such an image, it will copy MBR and partition table back to their standard locations and will fully populate the new 1900 MiB partition with whatever the original system had there.
On reboot, the MBR and the partitioned data will be the same, even if the unused spaces in the original and in the target CFs are not exactly equal to each other, right?
So the system will behave as if I had cloned the original system, right?
Of course, I am assuming dd behaves here as it does in a full Debian system.
Does it?
You must log in to post.
