You are not logged in.
Hello!
I bring a question that not involves old hardware. I hope that does not cause problems.

I made a live usb. Everything works perfectly OK.
Curious, because I saw several ways in the boot menu, looked at the boot folder and noticed four rootfs and soon realized its purpose.
Now came a strange idea. Can I create the same system to make a rootfs for nVidia, one for Radeon, for intel Grafics and, finally, a generic?
Space is no problem. I like SliTaz is light and practical. But in my spare time always has a game through wine ... And there are machines with different GPU.
I was thinking of mounting the following structure:
1) ati-rootfs
2) NGV-rootfs
3) intel-rootfs
4) generic-rootfs
5) programs-rootfs
It is possible with this structure, for example, have in the "ati-rootfs" just enough to load X with support for radeon cards, and then load it with "programs-rootfs" where would the wine with the games?
I saw this dieia because the structure of "appends" in file "/home/boot/EXTLINUX/extlinux.conf"
that is made to load multiple "rootfs" s together.
* I need help to find your way and I'm not so advanced user. If possible I am willing to do but count on the help of the community.

Thank you,
Rodrigo Boechat
Offline
'tazlito merge' can help: http://hg.slitaz.org/tazlito/raw-file/tip/doc/tazlito.en.html#merge
1. Build any rootfs
1.1. Build generic-rootfs
1.2. Based on generic-rootfs build ati-rootfs. Idem for NGV-rootfs, intel-rootfs and programs-rootfs (for generic cards)
1.3. Build programs-iso from programs-rootfs (tazlito want an ISO)
2. Merge it with dummy RAM sizes
2.1. 'tazlito merge 300M programs-iso 200M ati-rootfs 100M generic-rootfs', rename it to ati.iso
2.2. 'tazlito merge 300M programs-iso 200M NGV-rootfs 100M generic-rootfs', rename it to NGV.iso
2.3. 'tazlito merge 300M programs-iso 200M intel-rootfs 100M generic-rootfs', rename it intel.iso
3. get back rootfs
3.1. 'mount -o loop,ro ati.iso /media/cdrom' copy /media/cdrom/boot/rootfs2.gz to ati-delta-rootfs
and /media/cdrom/boot/rootfs3.gz to programs-delta-rootfs
3.2. 'mount -o loop,ro NGV.iso /media/cdrom' copy /media/cdrom/boot/rootfs2.gz to NGV-delta-rootfs
3.3. 'mount -o loop,ro intel.iso /media/cdrom' copy /media/cdrom/boot/rootfs2.gz to intel-delta-rootfs
4. put it in your grub
Title Generic
kernel /path/to/bzImage args
initrd /path/to/generic-rootfs /path/to/programs-delta-rootfs
Title ati
kernel /path/to/bzImage args
initrd /path/to/generic-rootfs /path/to/ati-delta-rootfs /path/to/programs-delta-rootfs
...
NB: with syslinux/extlinux/isolinux/pxelinux use
append initrd=/path/to/generic-rootfs,/path/to/ati-delta-rootfs,/path/to/programs-delta-rootfs
Offline
Thanks for your explanations.
I'll try soon.
Rodrigo Boechat
Offline
Well I tested even without installing any video card and I'm an unexpected problem.
At home, I started with the LiveUSB normal and installed firefox, flash and Abiword. Here in my old machine I have a gforce, but not yet installed it yet.
I "wrote" the changes that I made about the liveusb default with the command:
tazusb writefs lzma
I chose to remove the selected resolution and the selected sound card, when I asked.
Then I added a menu entry for the liveusb boot with my changes.
On another machine with onboard video, trying to start the system with my changes, it fell into terminal and presented an error when I tried to manually run the "startx".
The same happened in reverse. In another machine I started live, I installed the same programs and "write" the changes in another rootfs.
The same problem happened here in my old machine. She did not start the rootfs created on another machine.
I reviewed all my procedure and I could not see where I went wrong.
The tazusb is prepared to work with SliTaz 4?
I did not fail to note that in version 3 this problem did not occur.

Could anyone help me?
Offline
[ Generated in 0.017 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]