About installers

rations · 2026-02-17 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 (2026-02-17 16:55:07)

steve_v · 2026-02-17 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 (2026-02-17 04:23:30)

rations · Yesterday 16:15:22

@fsmithred chat bots added removeuser.conf this removed the live user on the installed system and left only the user created using the installer. Chat bots also added a shell process to remove everything Calamares and refracta snap shot installed.

fsmithred · Yesterday 16:46:44

@rations:

Yesterday I tried again using your modules and configs instead of my minimally edited debian files. It works. (replaced the user with what was entered in the installer)

One point (not the only) that I'm confused about is grub. I changed one line in the bootloader module so that it would boot efi or bios, and I'm wondering how it does that. Is a network connection required for that to succeed? My iso has grub-efi-amd64 installed, but I did a bios install and it got grub-pc from somewhere. (either network or it found the deb package that I put in the root of the squashed filesystem)

I'm going to keep playing with this, but it's probably going to go slowly. I have too much other stuff to do. Thanks for this contribution. I now have less hate for calamares. Maybe there can eventually be a calamares-settings-devuan package.

Devarch · Today 10:53:43

My argument is (and always has been) that refracta-installer needs a consistent UI

refracta-installer is half-garbage. No correct FDE support in 2026, seriously?! UI is not a problem here.

Last edited by Devarch (Today 11:04:08)

greenjeans · Today 15:07:54

refracta-installer is half-garbage.

Oh bullshit.

Starting to be amazed here at all the supposedly tech-savvy people who seem to need an installer app to hold their hands through the process.

rations · Today 15:31:24

@fsmithred If you ran the install-packages.sh it has grub-pc included in it, if you didn't I'm not sure. I've finished with this now. It was good fun. I've added the updated tar file on sourceforge and there's a build-readme as well. https://sourceforge.net/projects/unoffi … box/files/

I set it up to use the username and password of the machine taking the snapshot. So for example I can setup a system the way I want with a username live password live (it uses place_holder for whatever anyone wants to use), install the required packages for refracta and calamares, then from refracta-calamares-setup run scripts/install-config.sh, then run scripts/build-iso.sh and it's all done.

Calamares removes itself once it's finished the installation from the live usb. I also configured calamares to keep home/$USER/.config and home/$USER/.local, this can be added to or removed.

Anyone can change the logo, images for slideshow, number of images used, name of the installer or iso etc. And again CHAT BOTS have been used to write the scripts.

Refracta snapshot made this really easy so thanks again.

fsmithred · Today 16:34:50

FYI, refractainstaller had FDE before debian-installer did.

In my last build, I copied all of the user's home to /etc/skel and uncommented the appropriate line in the modules. It worked - it kept all the user configs and changed the user name.

And no, I didn't run the scripts. I'll have to try a no-network install to see what happens.

dzz · Today 18:33:24

I'm confused about is grub. I changed one line in the bootloader module so that it would boot efi or bios, and I'm wondering how it does that. Is a network connection required for that to succeed? My iso has grub-efi-amd64 installed, but I did a bios install and it got grub-pc from somewhere. (either network or it found the deb package that I put in the root of the squashed filesystem)

Am I missing something, or are not all the required grub files in the grub2-common and grub*-bin packages (which can all co-exist on efi or bios systems)?

The currently-running laptop here is bios only.. grub-efi is a dummy, grub-pc is absent and I don't see why grub-efi-amd64 is of any use:

$ dpkg -l|grep grub
ii  grub-common                            2.06-13+deb12u1                         amd64        GRand Unified Bootloader (common files)
ii  grub-efi                               2.06-13+deb12u1                         amd64        GRand Unified Bootloader, version 2 (dummy package)
ii  grub-efi-amd64                         2.06-13+deb12u1                         amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 version)
ii  grub-efi-amd64-bin                     2.06-13+deb12u1                         amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
ii  grub-efi-ia32-bin                      2.06-13+deb12u1                         amd64        GRand Unified Bootloader, version 2 (EFI-IA32 modules)
ii  grub-pc-bin                            2.06-13+deb12u1                         amd64        GRand Unified Bootloader, version 2 (PC/BIOS modules)
ii  grub2-common                           2.06-13+deb12u1                         amd64        GRand Unified Bootloader (common files for version 2)

$ dpkg -S /usr/sbin/grub-install
grub2-common: /usr/sbin/grub-install

$ dpkg -S /usr/sbin/update-grub
grub2-common: /usr/sbin/update-grub

Last edited by dzz (Today 18:36:57)

fsmithred · Today 18:48:08

I thought you need to have the right package, grub-pc or grub-efi-amd64 to install the bootloader correctly, so I always make sure I have the right one before any grub-install happens. Two days ago, I did a bios install with grub-efi-amd64 installed and I rebooted to a grub rescue prompt. But that was with a misconfigured calamares, so maybe it doesn't count.

Looking at the files that grub-efi-amd64 provides, I have no idea what it does. Looks like nothing. The script gathers information for a bug report.

$ apt-file list grub-efi-amd64
grub-efi-amd64: /usr/share/bug/grub-efi-amd64/presubj
grub-efi-amd64: /usr/share/bug/grub-efi-amd64/script
grub-efi-amd64: /usr/share/doc/grub-efi-amd64

dzz · Today 19:07:54

I did a bios install with grub-efi-amd64 installed and I rebooted to a grub rescue prompt

Maybe grub-pc-bin was absent? It doesn't conflict.

Last edited by dzz (Today 19:09:01)

fsmithred · Today 19:16:52

grub-pc-bin was there. I normally include that and even the ia32-bin package, just in case someone needs it. (old macbook pro)

The officially official Devuan Forum!

#26 2026-02-17 01:30:10

Re: About installers

#27 2026-02-17 02:42:57

Re: About installers

#28 Yesterday 16:15:22

Re: About installers

#29 Yesterday 16:46:44

Re: About installers

#30 Today 10:53:43

Re: About installers

#31 Today 15:07:54

Re: About installers

#32 Today 15:31:24

Re: About installers

#33 Today 16:34:50

Re: About installers

#34 Today 18:33:24

Re: About installers

#35 Today 18:48:08

Re: About installers

#36 Today 19:07:54

Re: About installers

#37 Today 19:16:52

Re: About installers

Board footer