@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=0

You 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 )

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

In that name

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. 

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 = False

Btw, many things can be preseeded and tweaked in that way. See here for more info.

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 )

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 ), "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

3. "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  ).

* If you're using "live-build", easiest way is to just drop them in "*/config/includes.binary/support".

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!

@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: 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!

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 )....

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
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    ).
So, until I get around making things more friendly for everyone, commenting out the entire "refind_install" function and it's call 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...