Recent changes to pil

#19 SysVinit is used instead of OpenRC at install

2026-11-06T09:05:07.867000Z

Hi Peppermint OS,
The ticket can stay open..unfortunatelly. While my test on the VM somehow brought up OpenRC, I installed it now twice on a barebone and it only showed SysVinit again.
This was the most recent ISO -peppermint_devuan-amd64-2026-10-16.iso (I added the date).
Installed with BTRFS, but not the "erase all" pathway as in the VM but with "replace partition".

unrelated sidenote: It's nice to see BTRFS automatically adds some subvolumes, love it!

PepDev not activating OpenRC on barebone

2026-10-28T10:19:27.139000Z

Hi,

Installing Testversion peppermint_devuan-amd64-(2026-10-16), on an Asus book from 2022 as barebone, I found it doesn't activate OpenRC as it should
Setup : I installed in SSD with a pepvoid instance before into a new empty partition after, formatted it with BTRFS.

After install, "rc-service" or "rc-status" are "not found" in the CLI.
-There's no logging app for XFCE..Pulled some logs out of /var/log
-This is odd, as it worked in a VM (?)

-We had that before and it was fixed..one notable change- my VM runs on BIOS, while the ASUS uses UEFI.

Virt-Manager not working in Pep-Devuan-OpenRC VM

2026-10-28T09:23:20.030000Z

Hi,
Now as the Pep-Devuan-OpenRC instance is up, I found :
-When starting Pep-Dev in an VM with Virt-Manager, and then adding Virt-manager inside as well,
It cannot get a network connection
-Error report "Error, Network default is not active" and details:
Unable to complete install: 'Requested operation is not valid: network 'default' is not active'
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 71, in cb_wrapper
callback(asyncjob, *args, **kwargs)
~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/share/virt-manager/virtManager/createvm.py", line 2008, in _do_async_install
installer.start_install(guest, meter=meter)
~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
File "/usr/share/virt-manager/virtinst/install/installer.py", line 726, in start_install
domain = self._create_guest(
guest, meter, initial_xml, final_xml,
doboot, transient)
File "/usr/share/virt-manager/virtinst/install/installer.py", line 667, in _create_guest
domain = self.conn.createXML(initial_xml or final_xml, 0)
File "/usr/lib/python3/dist-packages/libvirt.py", line 4590, in createXML
raise libvirtError('virDomainCreateXML() failed')
libvirt.libvirtError: Requested operation is not valid: network 'default' is not active

So the virtual network adapter virbr0 cannot connect as eth0 (the virtual network adapter) is exclusively taken by the distro. When I compare this to a mint in the scenario, it's no problem to have virbr0 and eth0 jointly, virbris use the "NAT" Connection type in virtual-manager.
It seems, this is normally shared in VMs, but not in this case.

Relevancy: Many may test this distro in a VM including the capability to run VMs, so some relevancy for user acceptance midterm.

I will also test virtual-manager in a barebone situation, and add results here.

Exact iso: peppermint_devuan-amd64-21.10.26

Side notes:
-Libvirtd is enabled in the VM, checked with "rc-service --list"
-teststart with sudo rc-service libvirtd start to see if it already runs -it does.
-user rights where given before with "sudo usermod -aG libvirt "user" and all necessary dependencies installed

#19 SysVinit is used instead of OpenRC at install

2026-10-28T08:08:49.308000Z

Okay, counterchecked, and it looks fine- OpenRC is up and running..the ticket can be closed! Thank you for the fast reaction :)
best regards
Pius

#19 SysVinit is used instead of OpenRC at install

2026-10-21T20:06:09.424000Z

Tested under same conditions (VM, Virt-Manager/QEMU, 8GB RAM)
And could now install with OpenRC, got it confirmed after install. Awesome! :)
Super, thank for the fast fix and looking forward if I get a virt-manager inside up and running.

#19 SysVinit is used instead of OpenRC at install

2026-10-16T15:30:00.517000Z

Just a log update - A note to keep things organized - this is just info no action needed from the user

The additional pep-init-tool does work for runit and sysvint
However openrc is hardcoded to use x11-common this is the second reason why it will not fully load the LightDM login.

The fix for this is to add this script to etc/init.d

#!/sbin/openrc-run

description="Initialize X11 runtime directories"

depend() {
    after localmount
    before xdm lightdm gdm sddm
}

start() {
    ebegin "Setting up X11 common environment"
    mkdir -p /tmp/.X11-unix
    chmod 1777 /tmp/.X11-unix
    chown root:root /tmp/.X11-unix
    eend 0
}

This script will be in the OpenRC init install
It does two housekeeping jobs for OpenRC:

Satisfies OpenRC's Dependency Check it acts as the mock/compatibility service for x11-common so OpenRC and LightDM stop throwing errors during boot looking for that missing service name.
Sets Up the Runtime Environment it creates /tmp/.X11-unix with the exact permissions (1777) required for X11 sockets.

When LightDM starts up right after this script runs, it launches the X server and because we already installed the xlibre metapackage and its core components via APT, the system will naturally execute XLibre's binaries (/usr/bin/X or equivalent) rather than classic Xorg. This init script just ensures the system is ready for booting

Still working on the ISO compile will keep this ticket updated

#19 SysVinit is used instead of OpenRC at install

2026-10-14T14:57:36.636000Z

Awesome! I gladly join testing! I would be default do it on a VM..but if necessary, I have also a barebone at hand that I could overwrite..just it's a bit special, a 2-in-1 nonstandard laptop where actually not few distros failed to work.

#19 SysVinit is used instead of OpenRC at install

2026-10-14T14:54:32.110000Z

Just keeping a update log here..
Wrote in a new module named pep-init-tool into the calamares installer that makes sure to install the selected init the user picks...

This ISO will be uploaded for testing Friday. So far local testing has been successful.

#19 SysVinit is used instead of OpenRC at install

2026-10-13T14:09:18.948000Z

Thank you for this catch! again...
I was able to validate that this is a bug., I have a plan for a solution and will note in this string when it is implemented some time this week

#19 SysVinit is used instead of OpenRC at install

2026-10-13T01:10:53.319000Z

Thanks!
Just want to make sure you did get that from here right?
https://nightly.peppermintos.org/dev64/flagship/