You are not logged in.
I am going to be following this closely, it's inspired me to restart my tribute build; full disclosure, for the rough start I did use the last KDE build as a spring board. Either way, the kernel has humbled me again and dinit has proved both insanely quick and straight forward but unforgiving. So massive kudos and a serious thank you.
Offline
Grahamps, thank you for your support.
Online
Posted right there few mins ago on your Mx Linux forum post and the devuanusers.com post too. All the best of luck man.
Can't wait for a distro on X Libre with any init plus sysd shim and MX Tools or Tweaks And Sonic DE (Plasma 6 fork) with X Server support since Plasma 6.8 will be wayland only and this Sonic DE will like Plasma 6 with that X server support.
I am in "do one thing well" team.
Offline
I found an interesting feature of this distribution - the installer refuses to see the second disk. Both disks are SSDs. Why?
Last edited by Devarch (2026-05-03 20:55:34)
Offline
Gazelle Installer? I have never had problems with it, and I have not changed the default settings. Maybe your SSD is not visible in Live, look before installing it in Gparted and try to mount it manually.
Last edited by Valera (2026-05-04 05:01:54)
Online
Maybe your SSD is not visible in Live, look before installing it in Gparted and try to mount it manually.
The installer works as expected when I use a Ventoy flash drive. The aforementioned strange behavior only occurs when booting the Live system from this second SSD using Ventoy. In such cases, I see all partitions on the first drive and only Ventoy-related partitions on the second. As a result, I am unable to install the distribution to the second drive.
Offline
You can't install that particular distro to the same drive you are booting from in ventoy. I have had that in MX Linux since even the file managers don't let us access that drive either.
Offline
You can't install that particular distro to the same drive you are booting from in ventoy. I have had that in MX Linux since even the file managers don't let us access that drive either.
Thanks for info. Anyway it's over - kernel panic after update, not this distro fault but ceres one.
My experience: MX_Devuan_KDE_dinit is great but as it's based on unstable it does not survive un update ![]()
Offline
Configure Timeshift to take one snapshot per week. I have not had any problems after updates.
Online
Configure Timeshift to take one snapshot per week. I have not had any problems after updates.I've reinstalled MXD again and had no issue with today' s update.
I've few questions about MXD and dinit (I'm new in dinit)
1. The distro has no doas preinstalled but I see preconfigured doas.conf in /etc/
2. I created ufw in /etc/dinit.d:
type = scripted
command = /usr/sbin/ufw enable
stop-command = /usr/sbin/ufw disable
restart = falseand not sure if I need depends-on, before, logfile? Also the service strarts but ufw is not enabled after reboot.
3. Service rc-local was in place already:
type = scripted
command = /usr/bin/sh /etc/dinit.d/scripts/rc-local.sh start
stop-command = /usr/bin/sh /etc/dinit.d/scripts/rc-local.sh stop
depends-on = login.targetit' s enabled and started but rc.local is ignored. What can be wrong?
4. It seems that bluetooth is installed:
dpkg -l | grep blue
ii bluetooth 5.85-4 all Bluetooth support (metapackage)
ii bluez 5.85-4 amd64 Bluetooth tools and daemons
ii bluez-alsa-utils 4.3.1-3.1+b1 amd64 Bluetooth Audio ALSA Backend (utils)
ii bluez-firmware 1.2-13 all Firmware for Bluetooth devices
ii libasound2-plugin-bluez:amd64 4.3.1-3.1+b1 amd64 Bluetooth Audio ALSA Backend (plugins)
ii libbluetooth3:amd64 5.85-4 amd64 Library to use the BlueZ Linux Bluetooth stack
ii libkf6bluezqt-data 6.23.0-2 all data files for bluez-qt
ii libkf6bluezqt6:amd64 6.23.0-2 amd64 Qt wrapper for bluez
ii papirus-mxblue 25.06.02mx25 all papirus blue folders with tabs for MX
ii qml6-module-org-kde-bluezqt:amd64 6.23.0-2 amd64 QML wrapper for bluezbut I don' t see any traces of bluetooth to set it up.
Last edited by Devarch (Yesterday 21:33:50)
Offline
ufw
type = scripted
command = /usr/sbin/ufw enable
stop-command = /usr/sbin/ufw disable
depends-on = mount-all
logfile = /tmp/ufw.logbluetoothd
type = process
command = /usr/libexec/bluetooth/bluetoothd
depends-on = dbussudo dinit-check ufw
sudo dinit-check bluetoothd
if OK, then
sudo dinitctl enable ufw
sudo dinitctl enable bluetoothd
Last edited by Valera (Today 05:08:48)
Online