Hello.
I am trying to install SliTaz on a hard disk installed in AlphaOS, but I can not do it the way I'm doing it.
My question is this:
Should I install SliTaz on a different partition? I can not copy the files to a folder on the same partition as Alphaos frugal and have two systems on the same partition? And so to be able to start with one and other.
From already thank you very much.

AlphaOS frugal + Slitaz?
(13 posts) (3 voices)-
Posted 11 years ago #
-
Slitaz can be installed to same partition as another linux.
For frugal install add a boot entry to grub menu.lst with the path to slitaz kernel and rootfs.gz.Installation docs:
http://doc.slitaz.org/en:handbook:installation
http://doc.slitaz.org/en:guides:frugal
http://doc.slitaz.org/en:guides:uncommoninstPosted 11 years ago # -
/ in ramdisk => http://doc.slitaz.org/en:guides:frugal
/ on hard disk => http://doc.slitaz.org/en:guides:uncommoninst#subdirectory-install-in-a-posix-filesystem ( or http://doc.slitaz.org/en:guides:uncommoninst#loop-install )Posted 11 years ago # -
I do not understand the second part of the instructions. The preinit.iso part.
I must put a copy of slitaz-I cooking.iso to boot directory? And then edit menu.lst?Posted 11 years ago # -
A script is run to mount the hard disk into a subdir or a loop file. The kernel can't to that alone.
With slitaz 4.0, http://mirror.slitaz.org/iso/4.0/flavors/slitaz-4.0-preinit.iso has this tools (and the rootfs4.gz in slitaz-4.0.iso too).
With the cooking, the kernel has an embedded rootfs to handle a subdir or a loop file. The preinit.iso is no more necessary for a subdir or a loop file. You can use the following grub config :
title SliTaz cooking
kernel /path/in/AlphaOS/of/bzImage mount=/dev/hda1 subroot=var/slitazThe SliTaz root filesystem will be in AlphaOS /var/slitaz directory.
SliTaz will not see AlphaOS tree until you mount it (# mount /dev/hda1 /mnt)Posted 11 years ago # -
I could not do it. I get the following error:
cp: cant create mnt/var/slitaz/dev/shm/libt etc...
No such file or directory
swuich to root: "cant execute" "/var/slitaz/dev/shm" No such file or directory.
This is my entry menu.lst:title Slitaz (sda1/slitaz)
uuid 14d1443c-f22df-44yf-3409-495c9156c4cb
kernel /slitaz/bzImage mount=/dev/hda1 subroot=var/slitaz
initrd /slitaz/rootfs.gzPosted 11 years ago # -
Assuming you are using the cooking version, can you retry with this entry in menu.lst:
title Slitaz (sda1/slitaz)
uuid 14d1443c-f22df-44yf-3409-495c9156c4cb
kernel /slitaz/bzImage mount=UUID=14d1443c-f22df-44yf-3409-495c9156c4cb subroot=var/slitazOf course the slitaz rootfs has been installed in /var/slitaz
# for i in $(ls -r /path/to/roofs*.gz); do unlzma < $i | ( cd /var/slitaz ; cpio -idmu ); done
Posted 11 years ago # -
Thanks for the help.
Still does not work.
What it means "Of course the slitaz rootfs has been installed in /var/slitaz"
=initrd /slitaz/rootfs.gz
or
=initrd /var/slitaz/rootfs.gz
in the menu.lst entry?Posted 11 years ago # -
It means 'You have extracted the rootfs*gz files in /var/slitaz' or 'ls -l /var/slitaz/bin/busybox' gives no error.
If not do 'for i in $(ls -r /path/to/roofs*.gz); do unlzma < $i | ( cd /var/slitaz ; cpio -idmu ); done'. (/path/to/roofs*.gz is likely /mnt/cdrom/boot/rootfs*.gz)
There *no* line starting with initrd in menu.lst anymore with cooking.
Posted 11 years ago # -
bzimage also has to be in var/slitaz or going elsewhere?
Posted 11 years ago # -
No. bzImage is anywhere you want. Only Grub must load it.
Posted 11 years ago # -
Slitaz usb no detect partitions in the hardisk
Posted 11 years ago # -
So these would be the command I run:
mkdir /mnt/var/slitaz
unlzma -c /media/cdrom/boot/rootfs.gz | ( cd /mnt/var/slitaz ; cpio -idmu )
And add the entry to grub
Other than that, I should not copy or do anything with any file?
I must not copy rooftz.gz to var / slitaz?
The problem does not recognize partitions from USB still exists.
ThanksPosted 11 years ago #
Reply
You must log in to post.