About installers

rations · Today 01:30:10

@greenjeans Possibly, they tried installing on a new desktop and an old laptop. I did tell them this and to look in the bios for options to disable anything UEFI boot, secure boot. If you used something simple like calamares, with a good cleanup script all the crap it installs could be removed leaving vuudo just the way you intended it to be.

@fsmithred When I used refractasnapshot I had the user set to human and EFI enabled. When I used the live usb the user name and password were the same as the user name and password from the machine that took the snapshot. Starting calamares it always asked for user name and password and that was the one from the machine that took the snapshot. I tried getting the chat bots to make calamares start with out putting in a user name and password but it didn't work so I just moved on using the one from the machine that took the snapshot.

During the install process with the calamares gui I put in user name test and password 1234 and when booting into the installed system it logged in with test and 1234. I did not install any of these cracklib_runtime and reinstall libcrack2. I am not a dev but I'm sure you don't have to do this "I would need to rearrange the build process of the iso to do it the debian-live way". All i know is it works with what you already have.

Grub was the final hurdle I had before the installer finished with out error. If you look at the bootloader.conf I used it's in the tar file on sourceforge I will not post it here given the love for ai slop. But this worked. I would suggest looking at all the module files in refracta-calamares-setup/config/etc/calamares they follow what the calamares source code says. When I boot the installed system I get a blue screen with the Devuan logo Devuan GNU/Linux, Advanced options for Devuan GNU/Linux and booting in countdown.
.
You guys make great stuff and with windows 11 people are trying out your work and want to use it. If you want people to use your work try and think like them and not a dev

.Edit. I only checked the user name and password I used in the Calamares installer and the installed system logs in with both that and the user name and password from the machine that created the snapshot

Last edited by rations (Today 16:55:07)

steve_v · Today 02:42:57

greenjeans wrote:

In the end it sounds like you're making an argument that Refracta-Installer needs a better GUI? While at the same time eschewing GUI's in general

My argument is (and always has been) that refracta-installer needs a consistent UI, with a real workflow that supports such elementary principles as going back a step or cleanly aborting an install.
Whether it's GUI, TUI, or CLI isn't the point, the point is that as it stands it's an incoherent mess of random dialogs and terminal windows with completely inconsistent behaviour and no mechanism for maintaining coherent state or running steps in anything but one narrow linear order.

For example: Most of the process is random yad dialogs, then suddenly up pops a terminal window with a TUI debconf prompt. If I abort that prompt, I expect an option to do it again, go back a step, or abort the install... But instead we're back to yad and the script continues with missing configuration as if nothing happened.

GUI or TUI, scripts and yad or debian tooling... Pick one and stick with it for the whole process.

Last edited by steve_v (Today 04:23:30)

The officially official Devuan Forum!

#26 Today 01:30:10

Re: About installers

#27 Today 02:42:57

Re: About installers

Board footer