Downloading TRIOS-RC23.iso to take a look at it...
Specifically the back end stuff (Installer, /etc/skel, etc etc)
Great, VastOne. :)
DE is xfce 4.11/4.12
Installer is a python-written modular installer, based on https://github.com/semplice/linstaller (https://github.com/semplice/linstaller)
https://gitlab.com/trios-linux/trios-installer (https://gitlab.com/trios-linux/trios-installer)
^ Looks good and plays well... a pretty good thought out distro
I have looked at the linstaller several times but could not quite get the heads up on it as there was little or no documentation on it and no good references.. I can see now how trios is using it as reference and build upon that
Will keep you updated ... gonna start on it tomorrow
Hey guys & gals,
I'm Filip, one of TRIOS developers.
Droping in quickly to thank @Misko for recommending TRIOS & Semplice/our installer and also to give @VastOne a couple of heads-up's on the installer.
If you use our version ( git or packages, no difference ), expect atleast two problems ( from the top of my head, there might be more ):
1. Installer uses a list of packages that are to be removed from the installed system, which we do not ship with it ( 'cause it would be a pain to rebuild the entire installer just to update it, so we get it in via skeleton ).
It's specified in /etc/linstaller/trios-base and resides in the same dir, although it can be anywhere. See here (https://gitlab.com/trios-linux/trios-installer/blob/master/config/trios-base#L22)
So either provide the file ( same format as live-build package lists, one package per line ), or remove it from *-base config.
2. If you attempt to install on an UEFI machine, it will try to setup refind and crash ( we use a separate script for that, also not included :D ).
So, until I get around making things more friendly for everyone, commenting out the entire "refind_install" (https://gitlab.com/trios-linux/trios-installer/blob/master/linstaller/modules/bootloader/inst/__init__.py#L216-223) function and it's call (https://gitlab.com/trios-linux/trios-installer/blob/master/linstaller/modules/bootloader/inst/__init__.py#L267) should be enough.
BIOS machines are ofc unaffected.
If I missed something, or if you have any questions or issues, I'll be glad to help/answer. :)
Now to minimize a bit the ammount of off topic for a first post... :D
(http://www.zimagez.com/miniature/screenshot-01272016-122628am.png) (http://www.zimagez.com/zimage/screenshot-01272016-122628am.php)
Hello Filip and welcome to our corner of the Linux Eco...
Great spin you all have going on with TRIOS, I am impressed with what I have seen... there are several things that I have seen and will join your forum to point out as well. Before we settled on FluxBox I was totally enamored with XFCE and that was the default on VSIDO... I do miss it though
There is one glaring issue I am facing now with just getting either one of the Linstallers working... the debian python-t9n issue
Specifically the error message is:
ImportError: No module named t9n.library
Any search for the exact message leaves nothing, a search for debian python-t9n finds only references to semplice and it's builds but nothing concrete
There is nothing in debian land I can find so how did you guys solve this? I cannot find the package python-t9n for download or build anywhere
Thanks for the heads up on what is there and not there.. I have installed yours and can follow it's paths and find where everything is at.. My process is simple, I take it a step at a time on a LiveCD of VSIDO until I get it working.. every installer in the past has resulted in a MOUNTAIN of dependencies we want nothing to do with here
Thanks
Thank you for a warm welcome!
Yeah, XFCE is great. IMO mostly because it more or less has everything that other DE's have, yet it's utterly stable and keeps itself out of the way.
You simply use it, without thinking much about it. :)
Flux is also great, allthough I've found PekWM to suite me better, mostly because I get around it's configuration a lot easier and to some degree it's "autoproperties" feature.
Besides that, AFAIK they are the only light wm's that support tabbing in titlebar, which is beyond awesome, especially on a low resolution screen.
@py-t9n
It's a part of "keeptalking" program ( also from Semplice ). Keeptalking is a stand-alone i18n/time-zone/kb-layout settings manager, and also a installer module.
Either build it from git, or just get the packages from our repo.
https://gitlab.com/trios-linux/keeptalking
http://www.mirror.org.rs/trios/mia/pool/main/k/keeptalking/
Also, keep in mind that it's pretty much abandoned upstream and partially broken ( so we forked and fixed it ). It's replaced by keptalking2, which is ok, however it relies a bit to much on systemd, dbus, runs as a service etc ( unnecessary stuff for what it does, IMO )....
:)
Quote from: VastOne on January 27, 2016, 12:49:59 AM
ImportError: No module named t9n.library
Any search for the exact message leaves nothing, a search for debian python-t9n finds only references to semplice and it's builds but nothing concrete.
There is nothing in debian land I can find so how did you guys solve this? I cannot find the package python-t9n for download or build anywhere.
You only found it in Semplice repo cause it comes from Semplice. Linstaller was created by Eugenio for Semplice. Here is the link to the module,
https://github.com/semplice/keeptalking/tree/master/t9n
Eugenio is a cool kid, I'm sure he will be happy to help with Linstaller.
Cheers!!!
filip won ;)
Quote from: hakerdefo on January 27, 2016, 01:35:17 PM
...
Eugenio is a cool kid, I'm sure he will be happy to help with Linstaller.
Cheers!!!
He helped us a lot with the first steps, and was quick to reply and solve a couple of issues we reported.
Cool kid indeed! :)
Quote from: PackRat on January 26, 2016, 12:25:15 AM
@misko - thanks.
Xmonad -
You are welcome. Nice desktop you have there.
@VastOne I sent Filip a message and he registered on the forum to help. Such a friendly fellow. :)
I hope the installer will work for you.
@filip hello there. Thanks for taking a time to help here. :)
@jedi you are an artist. Thumbs up
Thank you misko, hakerdefo and filip
Thanks for the information and paths you took to get there...
What exactly is the KeepTalking program in reference to linstaller?
I did grab your TRIOS debs of the t9n library and will let you all know how it goes
Thank you...
@Misko:
Friendliness is one of the major reasons why I got into linux/foss anyway, so it's only natural to "act" the same. :)
After all, everything in our world mostly revolves around community, so being friendly, sticking together and cooperating is a must IMO ( especially with the lastest "trends" of doing the exact oposite ).
Quote from: VastOne on January 27, 2016, 02:35:13 PM
...
What exactly is the KeepTalking program in reference to linstaller?
I did grab your TRIOS debs of the t9n library and will let you all know how it goes
Thank you...
It's a module that provides installer with a Locale/TimeZone/KB Layout ( GUI ) frontend, and a backend which applies the chosen settings to the installed system. :)
While at it, I forgot to mention that currently you can only choose
one KB layout, which is applied system-wide ( it's written to /etc/default/keyboard ).
So, anyone who uses a
non-latin KB should be carefull, since there might be issues later, with for example typing terminal commands, tty etc.
It's ofc easy to fix, but for someone who doesn't know what's going on, it might be a serious pain.
Once I have time, I'll try to improve keeptalking to allow choosing multiple, and a default layout. :)
One more note about installer. The CLI front-end is quite behind GTK, not recieving much care from Eugenio nor us, so while it mostly works fine ( BIOS only IIRC ), it's something to keep in mind. :)
Quote from: filip on January 27, 2016, 03:04:25 PM
@Misko:
Friendliness is one of the major reasons why I got into linux/foss anyway, so it's only natural to "act" the same. :)
After all, everything in our world mostly revolves around community, so being friendly, sticking together and cooperating is a must IMO ( especially with the lastest "trends" of doing the exact oposite ).
One more note about installer. The CLI front-end is quite behind GTK, not recieving much care from Eugenio nor us, so while it mostly works fine ( BIOS only IIRC ), it's something to keep in mind. :)
Thank you Filip ... I got into doing all of this for the same reasons to give what I know and can
I have everything working in order to load the installer (modules) thanks for the debs on t9n and keeptalking that made it very easy
As I continue, I seem to be hitting the gtk issues.. These are the errors now
vsido@vsido:~$ sudo linstaller -c=trios -f=glade start
/usr/share/linstaller/linstaller/services/glade/__init__.py:28: PyGIWarning: Gtk was imported without specifying a version first. Use gi.require_version('Gtk', '3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk, GObject, Gdk
(linstaller:7222): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:3922:29: Junk at end of value
(linstaller:7222): Gtk-WARNING **: Theme parsing error: unity.css:111:9: 'shade' is not a valid property name
(linstaller:7222): Gtk-CRITICAL **: gtk_box_pack: assertion '_gtk_widget_get_parent (child) == NULL' failed
(linstaller:7222): Gtk-CRITICAL **: gtk_box_reorder_child: assertion 'old_link != NULL' failed
W: Module path /usr/share/linstaller/linstaller/core/../modules/language/front/glade/module.glade does not exist! Skipping...
W: Module path /usr/share/linstaller/linstaller/core/../modules/timezone/front/glade/module.glade does not exist! Skipping...
(linstaller:7222): Gtk-CRITICAL **: gtk_tree_model_get_column_type: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed
(linstaller:7222): Gtk-CRITICAL **: gtk_combo_box_set_active_id: assertion 'gtk_tree_model_get_column_type (model, column) == G_TYPE_STRING' failed
(linstaller:7222): Gtk-WARNING **: Overriding tab label for notebook
<type 'exceptions.KeyError'>
Traceback (most recent call last):
File "/usr/bin/linstaller", line 436, in <module>
res = loop_modules()
File "/usr/bin/linstaller", line 175, in loop_modules
res = launch_module(module, main_settings["special"].split(" ") + main_settings["special_workspace"])
File "/usr/bin/linstaller", line 66, in launch_module
res = modclass.start()
File "/usr/share/linstaller/linstaller/modules/language/front/__init__.py", line 17, in start
return module.Module.start(self)
File "/usr/share/linstaller/linstaller/core/module.py", line 73, in start
obj.do_frontend_change(self.frnt)
File "/usr/share/linstaller/linstaller/core/service.py", line 90, in do_frontend_change
self.on_frontend_change()
File "/usr/share/linstaller/linstaller/services/glade/__init__.py", line 174, in on_frontend_change
self.current_frontend.objects = self.modules_objects[self.current_module.package.replace("linstaller.modules.","")]
KeyError: 'language.front'
(linstaller:7222): Gtk-CRITICAL **: gtk_main_quit: assertion 'main_loops != NULL' failed
Is there something specific to a python gtk3 / glade need that I have not seen?
BTW Filip, I love that avatar!
8)
This is for my notes and a placeholder as much as anything.. a guide for the steps I have taken to convert the TRIOS Installer into a viable VSIDO installer
Starting all of this on the latest ISO of x64 VSIDO in a VirtualBox LiveCD session
Download and install the TRIOS Linstaller (https://github.com/trios-linux/trios-installer) unpack and run
sudo python2.7 setup.py install
sudo ln -s /usr/share/linstaller/linstaller.py /usr/bin/linstaller
sudo apt-get install notify2
download and dpkg -i the following 3 files from the trios mirror site (http://www.mirror.org.rs/trios/mia/pool/main/k/keeptalking/)
sudo dpkg -i keeptalking_6.0.2.1~trios3_all.deb
sudo dpkg -i python-keeptalking_6.0.2.1~trios3_all.deb
sudo dpkg -i python-t9n_6.0.2.1~trios3_all.deb
W: Module path /usr/share/linstaller/linstaller/core/../modules/language/front/glade/module.glade does not exist! Skipping...
W: Module path /usr/share/linstaller/linstaller/core/../modules/timezone/front/glade/module.glade does not exist! Skipping...
This is wierd, it shouldn't be looking for modules at .../linstaller/core/../modules/module_name, but in ../linstaller/modules/module_name.
Might be a setup.py issue, although looking at it shows no obvious fault.
I'll investigate further, but in the mean time, I think the best way would be to use installer packages from our repo, or even better clone the git and build them.
Quickest way:
git clone https://gitlab.com/trios-linux/trios-installer.git && cd trios-installer
sudo apt-get install debhelper dh-python dpkg-dev devscripts && dpkg-buildpackage -uc -us
sudo debi # to install the built pkgs
If packages work, then it must be something related to setup.py.
Btw, GTK errors are safe to ignore, as long as there are no problems ( crashing, missing widgets etc... ). They are mostly caused by the "crazy" Gnome crew and constant non-backward compatible changes they make in gtk3...
@avatar:
Thanks! :)
Here is a paste of the build following Filip instructions from his last post (http://hastebin.com/alafomihin.md)
As you can see everything built as it should and I do have all of the debs
Initial tests showing a dependency on bricks for the modules-base deb... I am researching and following up on that now
Quote from: VastOne on January 27, 2016, 09:55:04 PM
Here is a paste of the build following Filip instructions from his last post (http://hastebin.com/alafomihin.md)
As you can see everything built as it should and I do have all of the debs
Initial tests showing a dependency on bricks for the modules-base deb... I am researching and following up on that now
A dozen dependancies are missing, but I've managed to do it :)
(http://i.imgur.com/r9zByTbl.png)
sudo apt update
sudo apt-get install debhelper dh-python dpkg-dev devscripts git
Now we need to get keeptalking
But first keeptalking dependancies python-all and screen
sudo apt install python-all screen
git clone https://gitlab.com/trios-linux/keeptalking.git
cd keeptalking
dpkg-buildpackage -uc -us
sudo debi
cd ..
Next bricks
git clone https://gitlab.com/trios-linux/bricks.git
cd bricks
dpkg-buildpackage -uc -us
sudo debi
cd ..
trios installer has a few dependancies (depends on keeptalking and bricks also)
sudo apt install python-notify2 python-progressbar python-parted imvirt cryptsetup fatresize hfsprogs pastebinit reiser4progs
git clone https://gitlab.com/trios-linux/trios-installer.git
cd trios-installer
dpkg-buildpackage -uc -us
sudo debi
And we run with
linstaller_crash_wrapper.sh -c=trios -f=glade start
^ thats cool... Thanks for assisting with this misko, I do appreciate it
Quote from: VastOne on January 27, 2016, 10:23:44 PM
^ thats cool... Thanks for assisting with this misko, I do appreciate it
Don't mention it. :)
Installer looks good on VSIDO 8)
^ I am following your excellent instructions and moving right along... Just about finished for an install test... once that is completed ok, I will then put the VSIDO branding on it and release it for testing
Again, thank you and Filip... It has been too long since we have had this kind of collaborations and I am damned glad it is happening
And now in the final stages of installing VSIDO not TRIOS.... ;D
(http://www.zimagez.com/miniature/screenshot2016-01-2716-51-56.php)
(http://www.zimagez.com/zimage/screenshot2016-01-2716-51-56.php)
Installation complete... will have to adjust just a few things, but all in all the start is here.. now if I can take the debs created and install them on the build systems and configure for the main work will be done.
Outstanding work and help from Filip and misko, the VSIDO nation is eternally grateful!
Quote from: VastOne on January 27, 2016, 10:56:52 PM
Installation complete... will have to adjust just a few things, but all in all the start is here.. now if I can take the debs created and install them on the build systems and configure for the main work will be done.
Cool. 8)
As Filip said, don't forget about refind function and call, also the packages that are removed http://vsido.org/index.php?topic=1124.msg12591#msg12591 (http://vsido.org/index.php?topic=1124.msg12591#msg12591)
Quote from: VastOne on January 27, 2016, 10:56:52 PM
Outstanding work and help from Filip and misko, the VSIDO nation is eternally grateful!
I'm just glad we have a good collaboration. That is something that I want to see more often in the linux/foss universe.
Best regards,
Miško
And just like that VSIDO has an alternative and new installer capabilities ...
(http://www.zimagez.com/miniature/screenshot2016-01-2803-14-26.png) (http://www.zimagez.com/zimage/screenshot2016-01-2803-14-26.php)
This is setup and functional on both x32 and x64 ISO's and will be made available very soon for testing
Note the time of the install... Less than 4 minutes, I can live with that
The VSIDO Branding was actually just a matter of changing a couple of files ... I really do not care for any color or icon changes, the default suites me fine
I have to work on the network functions.. for whatever reasons this installer is not bringing over or setting up the correct /etc/network/interfaces files that we depend on... not sure why this is as the installer should just be worried about unsquashing and setting up user/locale/grub and move on...
running sudo ceni and reconfiguring does the trick .. and all that does is create the file that should be /etc/network/interfaces
Any thoughts on this one Filip or Miško
I found the 'why' to the network issue in the network module in
/usr/share/linstaller/linstaller/modules/network/inst/_init_.py
I'll decode and let you know the results.. I already see some things commented out that may be the issue
I also wanted to point out one thing I saw... On one screen during the install there is something like
"Designed for smart people ..."
But it says
"Designed for smart pepole ..."
Not sure if that is the exact message but it is the exact error
Edit - This is on the partitioner during manual partitioning
'Powerful tools for Powerful Pepole'
I was able to solve it by adding to
/usr/share/linstaller/linstaller/modules/network/inst/_init_.py
The complete modified file can be seen here (http://hastebin.com/berimogeno.py)
The area I specifically changed was this
making this
auto lo
iface lo inet loopback
""")
this
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
""")
in the Configure loopback section
First install with the x32 bit test... 3:01 install time, fastest ever
scrot or it did not happen?
(http://www.zimagez.com/miniature/screenshot2016-01-2811-21-44.png) (http://www.zimagez.com/zimage/screenshot2016-01-2811-21-44.php)
FYI... I am finishing the build of the x64 now... once I test it I will release these as tests for anyone who can to try the new installer and leave feedback
Quote from: VastOne on January 28, 2016, 11:25:23 AM
First install with the x32 bit test... 3:01 install time, fastest ever
scrot or it did not happen?
The 'Golden Install' of VSIDO! I'm thinking that will be a long time standing record right there. Congrats on the new installer. I agree with misko, it is the spirit of the Linux/FOSS universe that makes it so great!
All right I have mucked with php code enough this morning and failed so...
Here is the link to Mega Cloud that will get you the files (https://mega.nz/#F!4ApEyCLK!w1sOvQmEM8v54AL3PFkVHw)
Good luck testing, fair warning this is test material... I have seen grub fail on two installs (greb restore menu instead of grub) but on a reinstall doing the exact same thing it worked the second time
Granted this could have been this users error (me, NO) since it was and is new to me too and the fatigue factors involved doing it over and over and over
Try it all, critique... let's see what we got
Thanks to all who has helped on this
Downloaded 64bit iso and tested in virtualbox.
Installed ok and reboted. On reboot there was no network connection until sudo ceni.
Ceni added enp0s3 at the end of /etc/network/interfaces.
cat /etc/network/interfaces
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
allow-hotplug enp0s3
iface enp0s3 inet dhcp
^ I saw that on one occasion during the testing but not ever again
This is one (along with the grub issue) that is perplexing to me... I know for a fact that neither has ever happened with the normal VSIDO installer, and if you were to install again using the standard installer you would get the correct network setup
grub issues on the other hand is an issue I think where an update-grub either is not setup to run or has failed to run. these are also fairly easy to identify and/or correct
Both installers are using the same squashed system so it is mind boggling to me how one installer completely misses and does not seem to have what it should have in config settings
Misko, would you please tab into edit mode on the grub screen on the new installation of vsido and verify that net.ifnames=0 is in fact on the linux/boot/vmlinuz line?
I'll take closer looks at the modules to see if I can spot what is going on
Quote from: VastOne on January 27, 2016, 10:56:52 PM
Installation complete... will have to adjust just a few things, but all in all the start is here.. now if I can take the debs created and install them on the build systems and configure for the main work will be done.
Outstanding work and help from Filip and misko, the VSIDO nation is eternally grateful!
Great news! I'm glad it works! :)
@Network:
I'm not really in a deep know-how on the topic, since in case of TRIOS, wicd or NM always worked, so we never really touched the network module.
On the other hand, on my old machine I'm using dhcp only ( no NM of any kind ), which worked for me ever since I can remember...
Anyway, what is obvious is that you guys need the "interfaces" file copied from the live/squashfs, instead of a generic one written by the installer.
So in the nutshell, the only thing I could do ( in future though ), is to make it a preseedable option, which would allow you to just specify it in "/etc/linstaler/vsido-base.conf".
Something like:
[module:network]
auto_gen_interfaces = FalseBtw, many things can be preseeded and tweaked in that way. See here for more info. (http://semplice-linux.org/doku/semplice:users:linstaller:preseeds)
Quote from: VastOne on January 28, 2016, 07:49:40 PM
grub issues on the other hand is an issue I think where an update-grub either is not setup to run or has failed to run. these are also fairly easy to identify and/or correct
Either, as you said "update-grub" doesn't run, or grub is not installed at all.
Anyway, log would help a lot ( see bellow ). :)
Also, while it's probably not the cause, it's worth mentioning...
We had a great pain with GRUB and partitioning, caused by thunar-volman automounting partitions. It prevents the installer from formating them, and "os-prober" from mounting them for scanning ( resulting in missing entries in grub menu, for all existing systems whose root partitions were auto mounted ).
It is fixed on the GRUB/os-prober side in testing branch, so you may try that one as well:
https://gitlab.com/trios-linux/trios-installer/commit/2a74e21b97853be43db0f5d2322f90100851af03
https://gitlab.com/trios-linux/trios-installer/commit/056cb73b38576604756fcc314b2a48a335acf39e
... or ignore it, if you don't have some kind of automounter.
Some more stuff worth mentioning/explaining:1. Bricks module:Like "keeptalking", Bricks is a standalone application and also a installer module, used for adding or removing Semplice "features".
Those "features" are kind of a specially crafted meta packages, that compared to regular ones allow you to install or remove any package that it depends on or recommends.
If you're familiar with Arch/Pacman package groups, it's kinda same ( and probably the reason why it was, I'll hazard a guess, easily integrated with Antergos ).
In Semplice, it allows a user to choose to install or omit stuff like Bluetooth support, Printing etc... ( scr*w the words, here's the pic (http://postimg.org/image/g2wmxb8sj/) )
TRIOS & installer wise -- we're not using it, since it needs to be overhauled so that it can be safely used with regular Debian meta packages ( like task-xyz-desktop ).
Overhaul is on a TODO list, but in the meantime we will almost certanly remove it from the installer dependencies ( it's artificial anyway, since it is not used ). I'll let you know when it's done, so you can remove bricks packages ( if you choose to, ofc ). :)
2. Log:During install process, it's written to "/var/log/linstaller/linstaller_latest.log".
If there are no crashes ( there never are :D :D ), "end" module copies it on the installed system at "/var/log/installation.log". :)
Btw, might be usefull to you as well. This is how I usually do a test/debug install run:
# Terminal 1:
sudo linstaller -f=glade start
# Terminal 2:
tail -f /var/log/linstaller/linstaller_latest.log3. "supportrepo" module:In short, you put* some packages on ISO image in "/support" dir which "supportrepo" sets up as a temporary apt repository, so apt can fetch and install those packages later ( usually in "bootloader" or "debian" modules ).
Usefull for offline installation, (or) when you need to make sure that specific packages are always available.
More importantly, it
must be enabled for UEFI support, if "grub-efi" is to be used, otherwise GRUB installation will fail in offline mode, or if repository fails.
I'll write more on that topic in a future post ( this one is allready long enough :D ).
* If you're using "live-build", easiest way is to just drop them in "*/config/includes.binary/support".
Quote from: VastOne on January 28, 2016, 07:49:40 PM
Misko, would you please tab into edit mode on the grub screen on the new installation of vsido and verify that net.ifnames=0 is in fact on the linux/boot/vmlinuz line?
Sure. Here we go...
There is no net.ifnames=0 in linux /boot/vmlinuz line.
^ That is a lot of great information... I will use it all! ???
The frustrating thing is the inconsistency... I have now done at least 25 installs testing things over and over, and have had two failures. Once was what Misko described with eth0 not being setup... I have forced systemd to accept the old linux standards of wlan0 and eth0 as described here (https://forum.manjaro.org/index.php?topic=8778.0), this is hardcoded so unless there is a brand new install of grub going on it makes no sense how this could change. The other was no grub at all and a grub rescue menu on boot...
On BOTH of these, I immediately reinstalled doing the same exact procedure and could not reproduce it, nor have I been able to reproduce it in any of the installations today, approximately 20 more
With us living in the land of SID we do in fact have the latest versions of os-prober and have not had any issues with it with the two original installers
I will keep this going and post anything I find as well
Thanks for the tips and insights..
Quote from: misko_2083 on January 28, 2016, 08:46:22 PM
Quote from: VastOne on January 28, 2016, 07:49:40 PM
Misko, would you please tab into edit mode on the grub screen on the new installation of vsido and verify that net.ifnames=0 is in fact on the linux/boot/vmlinuz line?
Sure. Here we go...
There is no net.ifnames=0 in linux /boot/vmlinuz line.
Could you also check on the live-cd? Before the live-cd loads, please tab and edit and confirm that it is or is not on the same line
Thanks mate
Quote from: VastOne on January 28, 2016, 08:50:23 PM
Could you also check on the live-cd? Before the live-cd loads, please tab and edit and confirm that it is or is not on the same line
Thanks mate
It's right there on live-cd.
^ During the partitioning, did you do the basics or did you have it auto setup everything?
Edit -
I just did let the installer auto configure and I did get the same issue, no eth0 but enp0s3
I have been able to replicate the issue to make it fail and leave you at a grub-rescue prompt...
If your mba (sda) does not have a boot flag setup on it, the installer does not provide it .. I was experimenting with manual partitioning and noticed on these failures that there was no boot flag setup
Once I did that, grub set up fine and the boot was good.. so in short if you have no boot flag setup, expect failure
I have no clue as to what is causing this... I thought I had it nailed down but I am getting grub_rescue prompt all the time ... it's as if the install of grub is completely missing
Should anyone experience the grub-rescue and wants/needs to restore and boot to it, this is the best procedure IMO
Quote(From within grub-rescue mode)
Command: ls
It will list all your drives and partitions, like:
(hd0) (hd0,msdos2) (hd0,msdos1)
If you don't know your Ubuntu boot partition, check them one by one:
ls (hd0,msdos2)/
ls (hd0,msdos1)/
When you hit the right one, you'll get a line mentioning "lost+found" / /boot /etc /usr and so on
Assuming (hd0,msdos2) is the right partition:
set prefix=(hd0,2)/boot/grub
set root=(hd0,2)
insmod normal
normal
This will now bring you to a VSIDO grub screen
Now you'll be able to boot into VSIDO. Once you do, execute the following commands:
sudo update-grub
sudo grub-install /dev/sda
reboot and you will find the partition you just installed as well
Quote from: filip on January 28, 2016, 08:30:20 PM
2. Log:
During install process, it's written to "/var/log/linstaller/linstaller_latest.log".
If there are no crashes ( there never are :D :D ), "end" module copies it on the installed system at "/var/log/installation.log". :)
Btw, might be usefull to you as well. This is how I usually do a test/debug install run:
# Terminal 1:
sudo linstaller -f=glade start
# Terminal 2:
tail -f /var/log/linstaller/linstaller_latest.log
I will be running this and returning the output here shortly...
VSIDO linstaller_latest.log on hastebin (http://hastebin.com/xikacicewa.vhdl)
Also an image of what I am installing to via the Manual Partition Manager
(http://www.zimagez.com/miniature/screenshot2016-01-2903-57-54.png) (http://www.zimagez.com/zimage/screenshot2016-01-2903-57-54.php)
I do see errors around the grub install portion in the log. This time I did not get a grub_rescue menu as I thought I might... I got the grub menu from the secondary sdb partition... I ran sudo update-grub there and it found the new install cleanly and I booted to it with no issues with eth0 and wlan0, the network was setup and functioning as it should
So obviously the installation to the mbr is failing on some installs, several in a row now for me
And with that I will get some much needed rest...
Judging from the log, GRUB is installed to the mbr and updated. However "refind" installation failed, allthough it doesn't explain the issue, since it's the last step in the process ( install grub --> update-grub --> install refind )...
@MBR location:
Linstaller uses a "grub-mkdevicemap" to find out which drive is first, so the issue here might be that "sdX" it finds is not the primary boot drive set in BIOS.
But let's just eliminate "refind" first, see how it goes, and if needed dig further from there. :)
This could very well have something to do with VirtualBox... I have come to this conclusion because I have seen some very strange uuid and partition mount behavior in the past from these virtual-box build platforms I use
Like these issues I am seeing with linstaller, the uuid/mount issues have been random as well
I am going to test the install on some metal machines I have to see if I can replicate it there
Regarding the grub issue, and after correcting an issue within VirtualBox ... I am no longer able to recreate the grub-rescue problem.
I am also not seeing issues installing to metal drives ...
I will now move onto logging what is happening when you go with default settings and the eth0/wlan0 settings are not applied correctly
Here is the log. (http://hastebin.com/sotumutefu) I am able to recreate this issue every time by choosing and excepting the 'default' partition setup
For whatever reasons, this grub install is not implementing the default setup of net.ifnames=0 that is there on the livecd session and is default within the VSIDO squashfs
I can recreate it every time.. If this issue is solved, I believe we can use this installer
Edit -
Confirmed that by manually editing and adding net.ifnames=0 to the grub boot line on startup does work as it should creating eth0/wlan0
Looking at the post installation, the correct parameters for net.ifnames=0 are setup within /boot/grub/grub.cfg file so there appears to be no logic as to why it is not applied during the setup of grub
Looking at the installation, the correct parameters for net.ifnames=0 ARE NOT setup within /boot/grub/grub.cfg for the partition that was built during the install, checking uuid's confirmed this ... so in the creation of grub.cfg, the settings of net.ifnames=0 is not applied to the install during the 'easy' option of installing to partitions
^ @log refind isn't a big issue here
commenting out that line (https://gitlab.com/trios-linux/trios-installer/blob/master/linstaller/modules/bootloader/inst/glade/__init__.py) containing refind, that are used to display a message update a progress bar fixes that.
I think this here might be an issue:
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
Quote from: VastOne on January 29, 2016, 04:07:18 PM
Here is the log. (http://hastebin.com/sotumutefu) I am able to recreate this issue every time by choosing and excepting the 'default' partition setup
For whatever reasons, this grub install is not implementing the default setup of net.ifnames=0 that is there on the livecd session and is default within the VSIDO squashfs
I can recreate it every time.. If this issue is solved, I believe we can use this installer
Found it. :)
Line 189
https://gitlab.com/trios-linux/trios-installer/blob/master/linstaller/modules/bootloader/inst/__init__.py (https://gitlab.com/trios-linux/trios-installer/blob/master/linstaller/modules/bootloader/inst/__init__.py)
need to change that from
sys.stdout.write("GRUB_CMDLINE_LINUX_DEFAULT=\"quiet resume=%s\"\n" % swap)to
sys.stdout.write("GRUB_CMDLINE_LINUX_DEFAULT=\"net.ifnames=0 quiet resume=%s\"\n" % swap)And it should work. The function changes /etc/default/grub
Edit:
Tested and it worked here. :D
Also here:
https://gitlab.com/trios-linux/trios-installer/blob/master/linstaller/modules/bootloader/inst/glade/__init__.py (https://gitlab.com/trios-linux/trios-installer/blob/master/linstaller/modules/bootloader/inst/glade/__init__.py)
I've commented out lines # 53, 54, and 55 and refind error isn't in the installation log after the install.
^ These collaborations are what FOSS should be all about... I cannot tell you and Filip how damned happy it makes me to work with you.
The fact that we have an installer that is now fully functional with VSIDO is besides the point, the friendship and trust developed here is for a lifetime
Great work!
VSIDO Nation Salutes You
(http://vignette4.wikia.nocookie.net/memoryalpha/images/5/52/Spock_performing_Vulcan_salute.jpg/revision/latest?cb=20090320072701&path-prefix=en)
@Misko:
Good find & quick fix! :)
@all:
I'll include a "custom_kernel_args" seed, that can be used to add any kind of argument(s) to "GRUB_CMDLINE_LINUX".
So, in this case you would just add to "visudo-base":
[module:bootloader]
bootloader = grub
custom_kernel_args = net.ifnames=0You could also add multiple, space separated args ( no quotes! ):
custom_kernel_args = net.ifnames=0 god.mode=True enable.bugs=False...without worrying that it'll get overwriten on update. :)
I'm currently testing, although it looks good so far:
[trios-user@TRIOS][~]$ cat /linstaller/target/etc/default/grub | grep "GRUB_CMDLINE_LINUX="
GRUB_CMDLINE_LINUX="init=/sbin/openrc test=entry blah=0"
[trios-user@TRIOS][/linstaller/target/etc/default]$( ^rebooting excluded :D )
Once I'm sure that there are no regressions, I'll push it to testing branch @git ( might take a bit of time, since a full install is needed for every test run ). :)
Quote from: VastOne on January 29, 2016, 08:37:31 PM
^ These collaborations are what FOSS should be all about... I cannot tell you and Filip how damned happy it makes me to work with you.
The fact that we have an installer that is now fully functional with VSIDO is besides the point, the friendship and trust developed here is for a lifetime
Great work!
VSIDO Nation Salutes You
(http://vignette4.wikia.nocookie.net/memoryalpha/images/5/52/Spock_performing_Vulcan_salute.jpg/revision/latest?cb=20090320072701&path-prefix=en)
In that name (http://www.en.kolobok.us/smiles/big_standart/drinks.gif)
^ Fantastic... Let me know when they are there and I can begin the testing. Also keep in mind I am available at any time for any type of testing your team may need. I do not know code as well as you all but I can track down issues and troubleshoot as well as anyone... though Miska is incredible and tough to beat! :)
And by the way ...
a 2:50 install of a fully functional Linux Distro is incredible IMO
(http://www.zimagez.com/miniature/screenshot2016-01-2821-58-56.png) (http://www.zimagez.com/zimage/screenshot2016-01-2821-58-56.php)
Both the x32 and x64 ISO's have been built and tested with the changes made and both function as they should with eth0 and wlan0 as the default no matter what method you choose to install
I will post these ISO's shortly for testing
and did I say 2:50?
I meant 2:36
(http://www.zimagez.com/miniature/screenshot2016-01-2900-47-52.png) (http://www.zimagez.com/zimage/screenshot2016-01-2900-47-52.php)
To whomever resized the Spock Images saluting...
Thank you! 8)
I have done a makeover on the Download Page (http://vsido.org/template/index.html) that now reflects the VSIDO Test ISO Downloads (http://www.nixnut.com/vsido/test/.index.php)
Please grab the latest version of the ISO's that is specifically for testing a new installer
If you find the tint2 all wacky when you first boot to a live-cd log out and back in using a password of live. This brings you back in clean and tint2 is where it should be
This is due to some recent changes to X11 and should be corrected soon...
Quote from: VastOne on January 29, 2016, 09:56:05 PM
^ Fantastic... Let me know when they are there and I can begin the testing. Also keep in mind I am available at any time for any type of testing your team may need. I do not know code as well as you all but I can track down issues and troubleshoot as well as anyone... though Miska is incredible and tough to beat! :)
And by the way ...
a 2:50 install of a fully functional Linux Distro is incredible IMO
(http://www.zimagez.com/miniature/screenshot2016-01-2821-58-56.png) (http://www.zimagez.com/zimage/screenshot2016-01-2821-58-56.php)
Should be good to go. :)
More details in commit message:
https://gitlab.com/trios-linux/trios-installer/commit/eed7c7a9f86cf1184e25e30cf0f0736da7f57660
(http://www.zimagez.com/miniature/screenshot-01302016-035253pm.php) (http://www.zimagez.com/zimage/screenshot-01302016-035253pm.php)
@testing:Tnx! :)
I'll let you know if/when help is needed.
Although right now, "trios-info" tool could use some wider testing, and besides that, you may find it usefull.
It's a system information tool, with CLI & GTK interfaces that can also generate nifty system reports ( hardware, repo's, install log etc ) which can be saved to file and/or uploaded to pastebin.
CLI variant can also take screenshots of itself and upload them to imgr, and also works in TTY ( very usefull when someone has X or VGA issues since it provides an easy way to upload system/hw info ).
https://gitlab.com/trios-linux/trios-info
@speed:Mostly comes from the fact that squashfs is decompressed directly onto target partition, instead of mounting it separately and copying file by file ( like LMDE installer does, for example ). :)
Though there's nothing wrong with LMDE's approach, it's just slower ( on hdd's atleast ).
Quote from: VastOne on January 30, 2016, 02:28:42 AM
I have done a makeover on the Download Page (http://vsido.org/template/index.html) that now reflects the VSIDO Test ISO Downloads (http://www.nixnut.com/vsido/test/.index.php)
Please grab the latest version of the ISO's that is specifically for testing a new installer
If you find the tint2 all wacky when you first boot to a live-cd log out and back in using a password of live. This brings you back in clean and tint2 is where it should be
This is due to some recent changes to X11 and should be corrected soon...
Downloading. :)
Btw, don't tell me that X11 issue comes from the fact that it's compiled with systemd support, which landed in Sid recently ( if I'm not mistaken )? ???
^ triosinfo is a sweet little tool.
Are python3 and python3-gobject the only dependencies needed for full functionality?
(http://en.zimagez.com/miniature/trios-gtk.png) (http://en.zimagez.com/zimage/trios-gtk.php)
Quote from: filip on January 30, 2016, 02:57:29 PM
Should be good to go. :)
More details in commit message:
https://gitlab.com/trios-linux/trios-installer/commit/eed7c7a9f86cf1184e25e30cf0f0736da7f57660
Btw, don't tell me that X11 issue comes from the fact that it's compiled with systemd support, which landed in Sid recently ( if I'm not mistaken )? ???
Great work on getting the changes out so quickly .. I will grab those and test
The X11 / Tint2 issue is related only to VirtualBox... any mass changes to X and there is a few days for the devs to catch up on V-Box environments .. Not a systemd issue yet
What will you do when X is consumed by systemd? I see all hell breaking loose if that happens
As RatMan said, triosinfo is a great tool
@PackRat... pastebinit is also a requirement in order to pastebin it... (terrible I know) ???
@Filip... Where should reports be sent? I have a crash using triosinfo
(http://www.zimagez.com/miniature/screenshot2016-01-3009-49-11.php)
(http://www.zimagez.com/zimage/screenshot2016-01-3009-49-11.php)
Works perfectly for Full System Report but crashes hard when using the Hardware Report from Detailed Report Menu
trinfo-gtk
(trinfo-gtk:30444): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:3922:29: Junk at end of value
(trinfo-gtk:30444): Gtk-WARNING **: Theme parsing error: unity.css:111:9: 'shade' is not a valid property name
**
Gtk:ERROR:/build/gtk+3.0-SLiI62/gtk+3.0-3.18.6/./gtk/gtkcssinheritvalue.c:33:gtk_css_value_inherit_free: code should not be reached
**
Gtk:ERROR:/build/gtk+3.0-SLiI62/gtk
Found and fixed a bug present in testing branch ( I've missed a parentheses in one place, causing partition scaning to hang ).
So as usuall, clone testing --> rebuild the packages. :)
@PackRat:
For the basics, yes ( excluding pastebining, screenshot upload, and Detailed report ).
For a full monty, you need:
scrot fbcat python3-requests inxi xdotool
:)
EDIT:
And "pastebinit", I forgot it. :D Thanks VastOne for reminding. :)
Quote from: VastOne on January 30, 2016, 03:51:30 PM
@PackRat... pastebinit is also a requirement in order to pastebin it... (terrible I know) ???
@Filip... Where should reports be sent? I have a crash using triosinfo
(http://www.zimagez.com/miniature/screenshot2016-01-3009-49-11.php)
(http://www.zimagez.com/zimage/screenshot2016-01-3009-49-11.php)
Works perfectly for Full System Report but crashes hard when using the Hardware Report from Detailed Report Menu
trinfo-gtk
(trinfo-gtk:30444): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:3922:29: Junk at end of value
(trinfo-gtk:30444): Gtk-WARNING **: Theme parsing error: unity.css:111:9: 'shade' is not a valid property name
**
Gtk:ERROR:/build/gtk+3.0-SLiI62/gtk+3.0-3.18.6/./gtk/gtkcssinheritvalue.c:33:gtk_css_value_inherit_free: code should not be reached
**
Gtk:ERROR:/build/gtk+3.0-SLiI62/gtk
It's best to open a issue on GitLab ( you need to be registered first ).
Here: https://gitlab.com/trios-linux/trios-info/issues
@Crash:
Either gtk (css) causes it, or it's threading that's misbehaving. I'll look into it. :)
Though one information would help. Does it crash each and every time, or randomly ( if randomly, then it's likelly to be threading issue )?
Installed the dependencies; no crashes for either report.
RE - Memory reporting; looks to me like it is reporting the free memory, not the used:
(http://en.zimagez.com/miniature/trios-info.png) (http://en.zimagez.com/zimage/trios-info.php)
Quote from: VastOne on January 30, 2016, 03:33:26 PM
The X11 / Tint2 issue is related only to VirtualBox... any mass changes to X and there is a few days for the devs to catch up on V-Box environments .. Not a systemd issue yet
What will you do when X is consumed by systemd? I see all hell breaking loose if that happens
As RatMan said, triosinfo is a great tool
Good :D :D
@X:
Well, it's unlikelly since it needs to run on BSDs, OpenSolaris/Indiana and such, so sysd will probably remain an optional feature. :)
Besides that it still is a pain for everyone not using systemd, since it forces you to rebuild X packages for your self, and maintain them ( and there is allready a longish list )....
@PackRat:
Ahh, forgot about that. I've spotted it some time ago on Manjaro ( changes in the "free" output layout are the cause ), but forgot to fix it.
Will do in the next couple of days... :)
Quote from: VastOne on January 29, 2016, 09:56:05 PM
^ Fantastic... Let me know when they are there and I can begin the testing. Also keep in mind I am available at any time for any type of testing your team may need. I do not know code as well as you all but I can track down issues and troubleshoot as well as anyone... though Misko is incredible and tough to beat! :)
I was just lucky. :D
@Mr. Spock "Live long and prosper." ;D
@trinfo-gtk
@PackRat thank you for reporting @memory info
@Disk info That needs a fix too now it says "200G MB"
@Filip nice @args. Easier to do it in *-base, turning refind part the same way could be usefull
Quote from: filip on January 30, 2016, 04:42:57 PM
It's best to open a issue on GitLab ( you need to be registered first ).
Here: https://gitlab.com/trios-linux/trios-info/issues
@Crash:
Either gtk (css) causes it, or it's threading that's misbehaving. I'll look into it. :)
Though one information would help. Does it crash each and every time, or randomly ( if randomly, then it's likelly to be threading issue )?
I did register and submit this as an issue and yes it does happen every single time I run it.. it seems to make it to the very end and crashes
Edit -
I notice the same thing on memory...
Quote from: PackRat on January 30, 2016, 04:58:02 PM
RE - Memory reporting; looks to me like it is reporting the free memory, not the used:
Quote from: misko_2083 on January 30, 2016, 05:04:19 PM
Quote from: VastOne on January 29, 2016, 09:56:05 PM
^ Fantastic... Let me know when they are there and I can begin the testing. Also keep in mind I am available at any time for any type of testing your team may need. I do not know code as well as you all but I can track down issues and troubleshoot as well as anyone... though Misko is incredible and tough to beat! :)
I was just lucky. :D
@Mr. Spock "Live long and prosper." ;D
@trinfo-gtk
@PackRat thank you for reporting @memory info
@Disk info That needs a fix too now it says "200G MB"
@Filip nice @args. Easier to do it in *-base, turning refind part the same way could be usefull
@trinfo
Fixed both RAM & Disk usage. :)
As usual, pull latest version from git.
@refind:
Indeed. I'll see what I can do. :)
Quote from: VastOne on January 30, 2016, 09:43:01 PM
Quote from: filip on January 30, 2016, 04:42:57 PM
It's best to open a issue on GitLab ( you need to be registered first ).
Here: https://gitlab.com/trios-linux/trios-info/issues
@Crash:
Either gtk (css) causes it, or it's threading that's misbehaving. I'll look into it. :)
Though one information would help. Does it crash each and every time, or randomly ( if randomly, then it's likelly to be threading issue )?
I did register and submit this as an issue and yes it does happen every single time I run it.. it seems to make it to the very end and crashes
Edit -
I notice the same thing on memory...
Tnx! :)
Btw, I forgot to mention, you can also report (any) issues on our forums, if you prefer it that way or find it easier over git ( although GitLab makes it a bit easier for us to track them ).
I like git... ;D
Issue is resolved as my flaky gtk theme was the culprit
Quote from: VastOne on January 30, 2016, 10:52:25 PM
I like git... ;D
Issue is resolved as my flaky gtk theme was the culprit
@git:
Even better. :)
@themes:
I certanly don't expect you to change theme over trios-info issue itself, however if you do so and given the fact that you seem to like them Dark ones, to maybe ease the search I can recommend two:
Arc (https://github.com/horst3180/arc-theme)
and Vertex (http://gnome-look.org/content/show.php/?content=166318)
Both are maintained and support gtk 3.18 ( Arc for 3.20 is also being worked on ). :)
^ Both of those are good choices, thank you...
They remind me a bit too much of the #! themes and their OpenBox colors.. (I detest OpenBox..)
I like the Dorian themes as they seem to match this web site colors perfectly.. It is a symbiance I have always enjoyed and these themes have never been an issue until today.. :)
Quote from: VastOne on January 30, 2016, 10:52:25 PM
I like git... ;D
+ 1000
trinfo and trinfo-git are working as advertised.
Quote from: filip on January 30, 2016, 11:30:33 PM
Quote from: VastOne on January 30, 2016, 10:52:25 PM
I like git... ;D
Issue is resolved as my flaky gtk theme was the culprit
@git:
Even better. :)
@themes:
I certanly don't expect you to change theme over trios-info issue itself, however if you do so and given the fact that you seem to like them Dark ones, to maybe ease the search I can recommend two:
Arc (https://github.com/horst3180/arc-theme)
and Vertex (http://gnome-look.org/content/show.php/?content=166318)
Both are maintained and support gtk 3.18 ( Arc for 3.20 is also being worked on ). :)
With the latest git version, I am no longer crashing on the Hardware Report or any report or anywhere ... ;D
Quote from: VastOne on January 31, 2016, 03:15:08 PM
With the latest git version, I am no longer crashing on the Hardware Report or any report or anywhere ... ;D
I sometimes get a segmentation fault (say 30% of the time) if I start trinfo-gtk from a terminal (sakura); if I start it from fbrun no issues.
I resolved the tint2 wackiness with a neat little setting I found about restarting fluxbox (https://pseudoscripter.wordpress.com/2015/05/07/restart-fluxbox-off-the-command-line/)
This is now setup on the ISO's and tested and works
Important heads-up.
I've commited a fix for a nasty bug introduced in a recent commit ( "mkfs" detection ), which caused installer to freeze completely if user tried to edit a partition which contains a file system whose "mkfs" was not found.
What happens is that installer tries to preset a format box to the file system that partition in question allready contains ( when you edit an existing "ext4" partition, format box gets preset to "ext4" ).
So, instead of trying to preset an non-supported FS ( and turn into ice cube along the way ), it first checks to see whether or not that particular FS is supported ( meaning that "mkfs" for that FS exists ).
So, new ( still testing ) version is released (https://gitlab.com/trios-linux/trios-installer/commit/5848e9069a4c90cff5d9ecbc2b201d6904498da0).
Also, issues with xfs & reiserfs are now fixed.
Update at will. :)
For detailed changelog see here (https://gitlab.com/trios-linux/trios-installer/blob/5848e9069a4c90cff5d9ecbc2b201d6904498da0/debian/changelog) ( versions "mia6" and "mia7" are new ).
Cheers! :)
I have built those and am now using them ... testing them so far all looks good
@filip, love your avatar!!! 8)
Another update ( "mia8-dev" ):
- Added "--quet" argument to "mkfs.jfs", which prevents it from hanging when formating partitions which allready have an FS ( otherwise mkfs would ask for confirmation, which cannot be provided through installer ).
- Fixed (https://gitlab.com/trios-linux/trios-installer/commit/8ff6bd6b9fa5be57363dac3d4b639579a4f167ca) mount options for all FS's, so no more failed mounting ( btrfs, jfs and xfs in particullar ).
So, right now all supported file systems ( exluding ntfs, fat & hfs+ ) are fully usable for a root partition ( both formating and mounting ). :)
Upgrade is strongly recommended for anyone planning to use btrfs, jfs or xfs for root ( otherwise, no rush ). :)
Quote from: jedi on February 04, 2016, 02:15:42 AM
@filip, love your avatar!!! 8)
Thanks jedi! :)
Quote from: filip on February 04, 2016, 11:29:15 PM
Another update ( "mia8-dev" ):
- Added "--quet" argument to "mkfs.jfs", which prevents it from hanging when formating partitions which allready have an FS ( otherwise mkfs would ask for confirmation, which cannot be provided through installer ).
- Fixed (https://gitlab.com/trios-linux/trios-installer/commit/8ff6bd6b9fa5be57363dac3d4b639579a4f167ca) mount options for all FS's, so no more failed mounting ( btrfs, jfs and xfs in particullar ).
So, right now all supported file systems ( exluding ntfs, fat & hfs+ ) are fully usable for a root partition ( both formating and mounting ). :)
Upgrade is strongly recommended for anyone planning to use btrfs, jfs or xfs for root ( otherwise, no rush ). :)
Updated to the mia8 levels... quite nice, the notify function has greatly improved where there is a notify now on every function. Great job
(http://www.zimagez.com/miniature/screenshot2016-02-0419-45-16.png) (http://www.zimagez.com/zimage/screenshot2016-02-0419-45-16.php)
2 minute 13 second install (2:13)
Once the gcc5 madness clears out and we lose the 125 MiB of baggage that is hanging around it (gcc4, gcc3) I believe I can hit a 1:59 install