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!
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".
auto_gen_interfaces = False
Btw, many things can be preseeded and tweaked in that way. See here for more info.
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/2a74e21b97853be43db0f5d2322f90100851af03https://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:3. "supportrepo" module:
sudo linstaller -f=glade start
# Terminal 2:
tail -f /var/log/linstaller/linstaller_latest.log
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".