yes, I did remember that unusual install method ( http://doc.slitaz.org/en:guides:uncommoninst#subdirectory-install-in-a-posix-filesystem ) as the frequenty of new Iso's of SliTaz is very high and the common new full install needs to format the small partition used by SliTaz on my HD.
a/ I have no experience with http://doc.slitaz.org/en:guides:uncommoninst#subdirectory-install-in-a-posix-filesystem
b/ I will store more than one, eventually one receipt only per subdiretory to separate the environments of the job so I don't have to install immediatelly all the parts of SliTaz if I only will test a new ISO...
Have you experience with that uncommon install method?
I have some question:
1. I would prefer to clearely separate both «clients» in the partition used. Can I proceed in the same form with the other file system. I will say: I would move my actual my actual file system for Debian9 RC2 or my actual file system for Kubuntu 17.04 (they are in two separate partitions now, but the second one is in the little partition, sda5, which I did name «chroot» because I will have a real separate «chroot» partition allthough it is also possible to chroot in a chroot subdir!) into each one subdir /Debian9RC2 or /Kubuntu1704.
Debian9 RC2 is actually in the sda5 (my «chroot»). What will happen, if I move it into my sda6, my unique big Linux partition (3/4 Terra byte)? Would I be able to continue to start it as proposed in http://doc.slitaz.org/en:guides:uncommoninst#subdirectory-install-in-a-posix-filesystem for Slitaz. What would happen with updates/upgrades?
Analog would I be very interessting to move all the system dir's from Kubuntu 17.04 from the root / into a subdir /Kubuntu1704 in the partition sd6 where it is already intalled, but else fully normal without some subdir "in front". Same questions!
2. I would clearely prefer don't to install, not like proposed, into a prexistent subdir «var» from used file system but in a clearly for SliTaz dedicated part of the partition that I would name /slitaz, and, in it, each separate each SliTaz installation as a own subdir, for ex. /slitaz/rolling-core64.iso170305 or /slitaz/slitaz-5.0-rc3-150520 instead of /var/slitaz working as "smudge" within my already installed Kubuntu 17.04 ...
How to adapt following boot text from above SliTaz wiki page:
title SliTaz cooking
map (hd0,0)/boot/slitaz-preinit.iso (hd1)
kernel (hd1)/boot/bzImage mount=/dev/hda1 subroot=var/slitaz
PS: during a certain time, I did do analog to this move all system directories with a "moving script" so that only one system is accessible in sda6. I works good enough for the major daily used system (it can be SliTaz or Debian or Ubuntu or Nutyx(LFS) etc.). But it does not be really adapted to the use of TWO main systems at the same time! I actually use more Debian9RC2 because it seems to work very good in a small SliTaz like installation but with LXQT and some part of KDE, especially Konqueror. The new Konqueror seems to be better and possibly soon a major browser again as it was in the past, as all the webkit and webengine world is derivated from it, I suppose (I don't will use some Mozilla: Mozilla handels now like a monopolist - it is not possible to avoid any more Firefox-ES! And the kind of management of the user data is in Mozilla very precary...). I did restart yesterday SliTaz, the new version named above in my exemple, in frugal install, that is the alternative way to test, but it is expensive of work, with LXQT, based on Qt3 :') and Qupzilla, old version 1.8.3 not able to support spell check as well as ibus-hangul :)) . All that were installed without problem (excepted time - not for every day!!!)! LXQT did start and it is really wonderfull also in SliTaz (if you are accostumed to use LXQT you never will see again some LXDE or some else. In my small Debian9RC2 install, a consciously minimal install, I did start after installing the base, with the xorg, menu and jwm, if not LXDE, it is really enough ;-) !, and continue with LXQT. All works properly but no modern browser as, like in SliTaz, Qupzilla is yet old version under 2.x, and Nano-Browser, the proposed exemple browser of webengine, is not available!