1 (edited by stuu 2026-08-30 16:24:49)

Topic: How to setup rEFInd?

Hello! How to install rEFInd on Hyperbola? After formatting the /dev/sda using cfdisk, I enter the following:

mkfs.vfat /dev/sda1
mkdir /boot/efi
mount /dev/sda1 /boot/efi
mkfs.ext4 /dev/sda2
mount /dev/sda2 /home
mkfs.ext4 /dev/sda3
mount /dev/sda3 /root
mkswap /dev/sda4
swapon /dev/sda4
mkfs.ext4 /dev/sda5
mount /dev/sda5 /

pacstrap /mnt base base-devel
genfstab -U /mnt >> /mnt/etc/fstab
arch-chroot /mnt /bin/sh
nano /etc/fstab
ln -sf /usr/share/zoneinfo/*/* /etc/localtime
hwclock --systohc
nano /etc/locale.conf
nano /etc/locale.gen
locale-gen
nano /etc/hostname
nano /etc/hosts
passwd

Now I need to install the refind and probably efibootmgr packages, but then what? If I simply enter refind-install the kernel will not start (which is logical).

2

Re: How to setup rEFInd?

Please refer here: https://wiki.archlinux.org/title/REFInd
Otherwise I recommend not using refind but grub instead.

Human being in favor with clear principles and so also for freedom in soft- and hardware!

Certainly anyone who has the power to make you believe absurdities has the power to make you commit injustices: For a life of every being full with peace and kindness, including diversity and freedom. Capitalism is destroying our minds, the planet itself and the universe in the end!

3

Re: How to setup rEFInd?

Okay, thanks.

4 (edited by stuu 2026-08-31 08:24:56)

Re: How to setup rEFInd?

And... Is it possible, using some option, to overwrite files if I initially compiled, say, evilwm from the source code, and now decided to install it from the repositories via hyperman (pacman)? I'm getting a similar error:

error: failed to commit transaction (conflicting files)
evilwm: /usr/bin/evilwm exists in filesystem
evilwm: /usr/share/evilwm exists in filesystem
evilwm: /usr/share/man/man1/evilwm.1 exists in filesystem
Errors occurred, no packages were upgraded.

5

Re: How to setup rEFInd?

We do no longer provide a package for evilwm upcoming.
Besides that: You should ALWAYS be very sure when you modify your root-filesystem without any package-management.

At that point you run out of responsibility from our side and your side also. The better option is always then to build your own packaging-script:  https://wiki.hyperbola.info/doku.php?id … e_creation

Also: Please stay on-topic for your own thread and do not mix different parts into it. Understandable to approach this pragmatic, but imagine how this looks for others when you first start asking about refind and than later go on with evilwm in the same thread. smile

Human being in favor with clear principles and so also for freedom in soft- and hardware!

Certainly anyone who has the power to make you believe absurdities has the power to make you commit injustices: For a life of every being full with peace and kindness, including diversity and freedom. Capitalism is destroying our minds, the planet itself and the universe in the end!

6 (edited by stuu Yesterday 14:25:01)

Re: How to setup rEFInd?

I did not ask a question specifically about evilwm and about support for this package in the future. I just gave evilwm as an example. In general, this problem happened to me when I switched (using the hyperman package manager) from hyperrc to runit and again to hyperrc, for personal needs. Due to the installation failure I removed hyperrc (using a USB disk with Hyperbola ISO) and went back to runit, however if I type 'doas pacman -S openrc openrc-sysvcompat' I get the same error I gave before. But... your answer is intended to apply to this remark. You are right.

[ you made a typo in the word 'refind' - refid smile ]

7

Re: How to setup rEFInd?

Thanks, correcting typo-problems.

Sure, if you mind to grant generic insights. But let us keep the point on-topic and better open a more generic point as openrc and runit have surely crossovers: You canot keep rests of both init-systems on the same installation. For example the commands reboot and poweroff will be linking different at least and mixing them will have conflicts. But that is different handled as alike doing something with root-access, example:

doas make install

That implies a clear installation within your root-system throughout after the build-time and therefore trigger the install-command also with all consequences. The package-manager is doing that different and handling conflicts also. So I recommend clearly to orient on building own packages.

You maybe able to use the option --force enforcing the installation, alike:

doas pacman -S --force <package-name>

Also you maybe cleanup the files manually with a removal.

Human being in favor with clear principles and so also for freedom in soft- and hardware!

Certainly anyone who has the power to make you believe absurdities has the power to make you commit injustices: For a life of every being full with peace and kindness, including diversity and freedom. Capitalism is destroying our minds, the planet itself and the universe in the end!