-This message have nothing to deal with flash, unlike previous posts (cause I'm not still here for now ... ).
-I'm talking about Linux slitaz 3.2-slitaz #4 SMP Mon Apr 15 14:33:16 CEST 2013 i686 GNU/Linux.
-I came across this whole thread, but I may forget some stuffs, and I'm sure I don't really understand some others...
So sorry if I just making disturbing wind.
I had uploaded slitaz-rolling, and burnt a CD of that iso;
I boot that CD, avoiding "locale problem" by choosing the last line in the first boot menu,
then the first line in the second boot menu.
Then, I made from that live session, with tazpanel, a working, bootable, just-awfull, slitaz-rolling, usb key.
(little win/gratefull dance).
Then, I ran a live session from that fresh USB,
on an HP thin client, so that it became a full pesonnal computer,
then I done tazpkg recharge,
then I done tazpkg up, for busybox and something like five others fresh packages.
And I report there :
boot log (http://dl.free.fr/pD4d5JUdT) with its hardware report (http://dl.free.fr/bwwTVhx4J),
and some (probably not enough precise, trying my best) observations:
-at boot menu, choosing locale will still not work, for FR, at least, for sure, make all get stucked to
sound-card 5% never ending search.
( I'm not able to make a new iso to add inside a "sleep 1" in /etc/init.d/system.sh as mentionned by Kultex)
-I havn't experienced issue with graphical hardware ;
those machines have an integrated video chip.
There is also a PCI port, I can make some tests with some old nvidia graphical card inside, if it is usefull.
-I wanted to tazpkg -gi dropbear, but it was already installed (cool!);
so I just started daemon, in root, doing :
# /etc/init.d/dropbear start
and I was able to see ( with top ) that it was running.
But, on the client side, I wasn't able to connect ;
I can't login as tux user, despite new re-generated fresh rsa key;
I tried as root too, but it didn't work, wich is a normal, security-related feature.
-I tried to make an install on hardware, from that live-session, with tazpanel,
but I'm always ending on the same error : hard disk can't be found,
but this is good labeling of the support, according to a check with fsdik -l,
and I havn't another choise in selection box !
I tried a lot of stuffs, formating before, and formating with the installation process, ext3 and ext4,
but I never been successfull : "the disk to write bootloader is not found".
I tried to run tazpanel with /dev/hda1 mounted, and also unmounted, before running tazpanel for install, too.
-I wish help pop-up/bubbles were here to help me discover new file manager interface,
but it's probably a locale related problem.
-screenshot utiliy works :-)
-yad "by default dialog", obtained by just typing yad then enter,
don't show its "bottle with green" window icon.
Of course, I agree this is a normal pre-release state, I'm not complaining :-)
I'm not able to elaborate fine testing process by myself, but I will be glad to try if you ask me.
Today they are 7 new packages ! Thanks to people working on that.
I hope something in the whole will be usefull :-)