Foreword

After waiting out on Devuan to mature for some time, I decided I'd try to make a relatively barebones systemd-free OS on top of Devuan. In trying to at least reasonably certify that the walking DNS remote code execution backdoor that only the NSA could love was gone, I stumbled across this thread invoking a bash script that helped identify processes relying on systemd (or what was left of it), and much to my surprise even my ripped out installation had 72 registries.

'Not to worry', I thought to myself 'I'll just get rid of the software components that directly and indirectly rely on systemd and install ones that don't'. Problem: I found even the kernel image (dependent on udev) relied on systemd. And after doing an initial package list search, I found to my horror that a lot of things Red Hat(e) had tinkered with, including lvm2 (responsible for disc encryption, I believe, now who could possibly want a remote code execution backdoor to have access to that?) were carriers of the systemd disease. 'I'm sorry, but it's xfterminal'

I decide what I needed to do was simply identify systemd using packages. I documented 42. Seemed a bit low. I did a manual scan. I estimated hundreds, if not thousands of packages via indirect dependencies. What to do? I decided I'd create a register documenting packages that rely on systemd so eager beavers like me would be able to shun it if they wanted to. I was lazy, so what was a guy to do?

The steps used

1) I first modified a relatively default devuan installation to include non-free and contrib, and made the insane decision of also sticking in a Debian repository (simply so I could make life harder for myself with even more systemd packages). Apt-get update was, of course, run.

2) I then ran the dpkg query command that pulled every available package name and descriptor from said setup. 3.2mb. 45970 packages or thereabouts Zoiks.

3) I threw it over to my main system to run in python and split on spaces, extracting the first term, and then converting each and every package into an apt-cache depends command which fed out into a text file named after the package. Sure, CPU inefficient, but I was doing lazy coding. I also filtered out the blatantly systemd package names at this stage to feed into a blacklist for later (no point getting the dependencies of a systemd item to see if it's systemd related).

4) After several hours (of running the massive 45970 or so entry of depends commands as a bash script), I got an entire directory of every package imaginable. Properties said it only took up a few mere megabytes, but in truth it was hogging over half a gigabyte due to all the separate files. There was a reason for this.

5) I opened the directory, and spat out it's contents from ls into a text file, meaning I had a list of every file.

6) I fed this list back into another python program who parsed the first word in the file (package name) and captured every dependency (note, it ignores recommends and suggests). Each dependency was put into square brackets after the first package name. Example:

0ad-data-common  [ttf-dejavu-core] [ttf-freefont] [tex-gyre]

This was stored in a line delimited list, so each package name was first, then it's dependencies in brackets. The dependencies list was 3.8mb in size. You can see a copy of it here on this 6 month expiring paste bin (a reupload to a permanent source would be appreciated).

7) Packages that apparently had no dependencies were stripped out, viewable here, which amounted to over 4000 packages. Mostly documentation and useless stuff, though.

8) I constructed a blacklist file from the extracted systemd dependencies, plus the packages I detected with the code found at the other thread link (along with said packages also mentioned at said link). This would be the 'seeder' file for detecting indirect dependencies.

9) I built a basic python program that converted the blacklist items into the square bracket dependency format (note: ignores optional dependencies placed in angular brackets) which populated a unique list item with the terms to detect. The program would then iterate over the list doing scans for packages dependent on systemd, adding it to the detection list and making a note to repeat the scan from the beginning once it completes it's current scan. It then compares every line (containing package name and dependencies) and identifies packages indirectly relating to systemd.

10) Because I know people won't necessarily trust the output from someone because they say so, I made a human readable output list as well, which mentions how a package is related to systemd (note, the program only detects the first systemd association and ignores others). So it'll say [<package name>] via [<dependency>], for example: "[isight-firmware-tools] via [udev]". You can then manually trace it back with Ctrl+F (not efficient, but at least traceable).

The program:

I know the list isn't complete, isn't perfect, and yes it is based on a Debian and Devuan repository hybrid plus user insights, but I figured I'd post it up for other people:

Raw dependencies data:
Dependencies.txt (subject to expiry, 6 months)
NoDependencies.txt

Program stuff itself:

HasDependencies.txt (subject to expiry, 6 months)
Blacklist.txt
DetectSystemD2.py

Excuse the sloppy code, it was only built to give me a rough overview of what I'm dealing with

And finally the (easily non-comprehensive) list:

Because the program is very basic, it cannot identify alternative or optional dependencies or close associations (some I had to add to the initial blacklist myself), so this isn't a definite list, feel free to take the datasets, modify it etc (doesn't have to just detect systemd, you can modify the blacklist to detect whatever). Note, this includes the surrogate libsystemd0.

Has, relies on or references systemd

I personally think the list looks a bit too small, so any suggestions for improvements welcomed (feel free to take or tinker with the code).

Hope it helps someone.

I recently bought a (cheap) compute stick and thought I'd install linux on it. It is an ideacentre stick 300, with quad core bay-trail atom, 2G ram and 32G flash. Not really that powerful, but at roughly the price of a raspberry pi, I gave it a go. I'm a long term linux user, and use devuan at work, so devuan was my first choice. The live usb booted even with the odd 32bit EFI / 64 bit OS combination. The only issue was that the intel SST drivers didn't work with the stock 4.9 kernel.

A bit of research turned up that the baytrail atom chip received proper support in later kernels. With 4.9, most things worked, except audio (HDMI), and built in WiFi. A quick backport later and 4.19 was installed and everything is working. I ended up not using the built in WiFi as it is quite poor - so a USB dongle I had was used instead. Combined with a wireless keyboard and a 24 inch HDMI monitor I had, and the system was up and running.

Now it is not a powerhouse by any means, but it is surprisingly usable. I credit devuan for getting the most out of the hardware with no or little overheads. I suppose I wanted to post in case anyone else had one of these devices and was having problems. A quick search didn't turn up anything. I've installed a few things like stellarium (which works surprisingly well), and a few plugins for firefox to enable streaming video from my subscribed service. In fact everything I have tried works well - just don't try to compile your own kernel.....

I am writing this on the "toy". Anyway, if anybody has a compute stick stuck in a cupboard, get it out and install devuan.

Runit is designed to work with daemons that stay in the foreground, so that the daemon may be supervised easily. Many daemons do try and run in the background but there is often an option that can be given to tell it to run in the foreground. Thus ntpd can use the -n (--nofork) option to run in the foreground.

Occasionally, there is a daemon which only runs in the background. I have found noip2 which updates my dynamic IP address. I have not found a way to tell it to run in the foreground. There are one or two things which you can do to handle this.

Runit comes with a program to change the process status (chpst).
This has a number of things it can do, such as changing the user or group it runs as.
The options which are useful here are -l & -L which can open a lock file for writing and obtain an exclusive lock on it, creating the file if necessary. -l will wait for the file to become available, while -L will fail immediately if it is not available.

The file /etc/sv/noip2/run looks like this :-

The echo message is logged if logging has been set up.

The daemon noip2 is run by chpst with an exclusive lock on the file /etc/sv/noip2/supervise/runlock

The second instance of chpst is ready to run the command true and waits for the lock file to become available, i.e. when noip2 stops running. When the lock file becomes available the command true will be run, which returns immediately and runit becomes aware that noip2 is no longer running and can take the appropriate actions.

But what happens if we want to stop the daemon? If

sv down noip2

is run then runit will stop the waiting chpst process, but not noip2.
After it has stopped chpst it will then look for the file finish and run it if it exists.
As we know the name of the lock file, we can find the PID of the process which has it open, using lsof, which may need installing.

apt install lsof

We can find the processes which have the lock file open :-

lsof /run/runit/supervise/noip2/runlock

COMMAND  PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
chpst   2006   root    3w   REG   0,23        0 1738 /run/runit/supervise/noip2/runlock
noip2   2051 nobody    3w   REG   0,23        0 1738 /run/runit/supervise/noip2/runlock

We could find the PID of the daemon by looking through the output for the process run by nobody
and then printing the second field :-

PID=`lsof /run/runit/supervise/noip2/runlock | grep nobody | awk '{ print $2 }' -`

although awk can do the search as well :-

PID=`lsof /run/runit/supervise/noip2/runlock | awk '/nobody/ { print $2 }' -`

However, a study of the lsof man page shows that there are lots of options available and the -t option just prints out the PIDs

lsof -t /run/runit/supervise/noip2/runlock

2006
2051

Also, there is the -c option which can select the process of a particular command or filter out processes of certain commands with the negation ^. In this case we don't want the chpst process.

lsof -t -c ^chpst /run/runit/supervise/noip2/runlock

2051

which can be incorporated into the file /etc/sv/noip2/finish :-

This seems to work nicely. With run and finish set up the daemon can be started, supervised and stopped.

So I decided to try using a devuan base again for my custom gaming computer
in the past i've had trouble getting custom kernels to work with devuan
which is usually what causes me to jump into other distros
cause custom kernel patches allow for pretty extreme performance enhancements
but after reading some comments from my old post about installing a custom kernel
I decided to jump back into devuan and see if I can turn it into the Ultimate Gaming system

...

I decided to upload my install notes in case it may be helpful to others later on

I keep notes on an old backup drive to help remember all the nuances at a later date

I'm building a system for high performance general/desktop/gaming usage

and am working towards it with Crowz->Devuan-Daedalus base

to get the best possible performance linux has to offer right now

System specs...

I have a custom built gaming computer with mostly the latest hardware/features

i7 cpu
rtx graphics card
16gb ddr4 ram
water cooling, giant rainbow fans, nvme hard drive
gaming monitor, mouse/keyboard
I use a wifi card, even though ethernet is ideal

usually my install notes are a lot simpler/cleaner but I decided to add details
to help explain the whole process, and my thinking along the way

##### Crowz-Devuan-Daedalus ROOT Only Ultimate-Linux Hyper Drive Gaming Install Notes

## I started with crowz to provide a super lightweight base system
## and to take advantage of it's calamares installer to quickly
## install a base system on an f2fs partition for my ssd drive

## Crowz Live CD location

https://sourceforge.net/projects/crowz/files/

## the proper method for making a USB to install the ISO with...

## I always use gparted to prepare the USB for an iso

sudo apt install gparted

## in gparted make sure to select the correct drive to work on,
## or you'll lose your data
## for me the USB is registered by the operating system as "sdb"
## then inside gparted -> select the usb drive in the dropdown menu
##-> select Device -> create new partition table -> select gpt
## then right click the device or look in partition menu
## and format the drive as fat32

## then after the drive is formatted correctly I use DD, and
## finally sync to write the iso to the usb
## after installing linux perhaps hundreds of times, this
## is the method I have developed out of habit, and failing
## to do these exact steps, will lead to corrupt installs/iso's
## that can be difficult to troubleshoot

sudo dd if=crowz.5.0...iso of=/dev/sdb bs=1M status=progress; sync

## Booting the Crowz-Devuan Live CD

## (I used the open box version of crowz)

## user//pass for crowz to login is crowzlive//live
## (lower case l in the password)
## have to install in bios mode NOT uefi mode
## by choosing usb:usb NOT usb:uefi
## in boot menu to use calamares to install on f2fs
## for hyper speed
##
## in order to get crowz to boot
## i had to go down to "(failsafe)"
## in the live cd's grub menu and hit tab to edit the command line
## used to boot the live cd... editing everything out except for
## vmlinuz... components vga=normal initrd...
##I had to use the failsafe menu entry to edit because the default
## live menu entry couldn't be edited, and that was the only way
## I could get the system to boot. i.e. allowing the kernel
## to automatically configure things on it's own by deleting
## the default commands on the grub menu options

## after it finally boots
## user//pass for crowz to login is crowzlive//live
## and you use startx to start the graphical desktop environment

startx

## then inside crowz I had to use some skillfull
## clicking to wrangle the network connections icon
## to connect to the internet
## opened a terminal to install f2fs-tools after updating
## the package database to do so....

sudo apt update && sudo apt install f2fs-tools -y

## then after installing f2fs-tools it's time to install
## crowz-devuan
## right click the desktop or open the file manager
## navigate to -> applications -> system tools
## which are inside the file manager as opposed to an app menu
## and double click the installer (have to double click pretty fast)
## to run calamares

## selecting the target drive for installation
## manual partitionning
## create new partition table -> gpt
## create 8 mb parition -> unformatted -> with bios/grub flag
## create 2048 mb -> linux swap -> swap
## create desired size (i left some space for future dual boots
## cause linux gaming doesnt require the hundreds and hundreds of gigabytes
## that windows gaming does) (made my root around 500 gb...)
## create a 500 gb -> f2fs -> root parition -> mounted on /

## make sure the bootloader is installed onto /dev/nvme0n1
## which is the actual device as a whole and not a partition on it
## which is indicated by a little dropdown menu on the very bottom
## of the screen. (should be the default setting)
##
## and because I initialized the installer after booting the live cd
## in bios mode , and NOT uefi mode
## the installation works perfectly and I have an f2fs formatted ssd drive
## which is the fastest anyone can possibly get right now : D

## then the restart button in crowz didn't work(like many things in crowz, but that is a good thing)
## because of it's minimal approach it is as fast as a lightning bolt)
## so I had to manually restart with...

sudo shutdown -r now

## Made a root account in crowz

sudo passwd root

## installed xfce (which enables running the entire operating system,
## including the graphical environment as a root user. (open box would crash)

sudo tasksel

## restarted

sudo shutdown -r now

## logged into xfce as root to start building on the crowz-devuan foundation
## my ideal gaming system

## with an f2fs partition you have to disable the file system check called fsck
## in the file system table called /etc/fstab

## and with the ultimate gaming computer you have to disable all automation anyways
## this is just the first step of many which also turn off automation

nano -w /etc/fstab

## then inside nano I unchecked the option that automatically invokes fsck
## at some future interval when I would bootup which would break my system
## and make it unbootable with an f2fs parition.... to make it look like

UUID=d88643b9-552k-4b21-8409-61caxe156bcf /              f2fs    defaults,lazytime 0 0

## [cntrl] + o , [enter]
## to save the file
## [cntrl] + x
## to exit nano

## then editing grub adding commands to default command line

mousepad /etc/default/grub

cpufreq.default_governor=performance mitigations=off rootwait

## make sure to save the file... I use rootwait with an nvme drive
## which is helpful to prevent lockups, that can happen depending
## on the configuration which changes over time
## I also use mitigations=off which is absolutely essential
## for getting the maximum performance in FPS gaming, other
## kinds of gaming it's not necessarry, but when every frame counts,
## and you need the best possible performance you need mitigations=off
## and ideally, like in my setup, to use the root account for everything

## update grub

update-grub

## add 32bit library support, and do first basic system upgrade

dpkg --add-architecture i386

apt update && apt upgrade -y

## reboot due to kernel upgrade from first upgrade

shutdown -r now

## always logging in as root manually
## the plan with this system is to install/use everything as root
## and apply unique workarounds to deal with the integrity/security of my system
## to get the highest gaming performance any linux system can offer right now

## installing graphics drivers

## the graphics drivers don't install exactly like they would on debian
## but it's essentially the exact same procedure with a few extra steps

apt install nvidia-driver

apt install nvidia-driver-libs:i386 nvidia-settings

apt install nvidia-vulkan-icd nvidia-vulkan-icd:i386

apt install libvulkan1

sudo reboot

## preparing the make the first backup, which when I stopped
## to make these notes too

sudo apt install ggparted timeshift lynx okular
apt install okular-extra-backends unrar

apt install wine winetricks gamemode lutris steam -y

apt install gufw

apt install vlc

## some simple hacks to run programs as root
## quoted directly from those websites...

## simple hack to allow vlc to run as root
## to play background music while you run circles
## around people in online gaming, and make them look silly

This is what worked for me. No compilation required.

sed -i 's/geteuid/getppid/' /usr/bin/vlc

Using VLC media player 2.0.3 Twoflower on a Raspberry Pi.

Explanation: The initialization script check if the UID is equals to zero. Zero is reserved for the root user. Using sed to replace geteuid for getppid fools the initialization script because it is always > 0.

While running the VLC as root is not recommended, it works. Be aware of the risks and obviously do not do it for production environments.

For Freebsd and other finicky unices and macos use the proper full syntax:

sed -i '' 's/geteuid/getppid/' /usr/local/bin/vlc

## simple hack for steam to run as root

OMG.

    Open /usr/bin/steam
    Comment or delete such lines:
    if [ "$(id -u)" == "0" ]; then
    show_message --error $"Cannot run as root user"
    exit 1
    fi

## I didnt have to apply this hack actually
## I think because I installed steam logged
## into the desktop environment under the root account...

## at this point I have a perfect base for
## my Ultimate-Linux Hyper Drive Gaming system
## and have little left to do other than basic desktop tweaks
## installing a custom kernel, and more system tweaks to
## get even more performance

## Generally the older kernels (i can't remember the versioning schemes,
## but basically the point upgrades stable distributions like devuan/debian use
## are actually faster, so you want to focus on those, and the same is true
## for drivers. Newer isn't actually faster, or better for performance...
## I actually miss the bullseye kernel/nvidia driver combo
## which is like versions 5.10 and 425 because they perform very well
## compared to the newer stuff

## first I will try using the basic liquorix kernel with my Crowz-Devuan Hybrid build
## which has patches for gaming, and later I will attempt to install a custom gaming
## kernel, or the patches for it using some guides online

## installing Devuan using the Crowz live cd actually made for the leanest
## base system anyone can possibly get right now, that is satisfactory for gaming,
## and after installing xfce, logging into it, the system is only using around 686-700 mb
## of ram, which is extremely impressive. This equates to faster system response time
## which is necessary for competitive gaming

## I also decided to stick with alsa for sound instead of getting pulesudio, as per
## advice on the devuan forum, alsa by itself is sufficient/ has very low performance overhead,
## which is ideal for my use case

## Using the root account for everything literally doubles my download speed, and
## system response time across the board. Everything is faster, more efficient,
## and super speedy. As I'm writing these notes im getting 200 MB/s download speed
## on my wifi, downloading the first game I will be testing the system with, which
## is literally double the speed I have ever gotten in a regular user account.
## As a regular user this download might of taken an hour and a half, whereas
## under the root account I've got the game up and running in less than 20 minutes.

## And this is essentially how using the root account is going to benefit all of the
## system operations compared to a regular user account. Everything will be twice
## as fast, including beating people up on online gaming ;D

## with f2fs, devuan, some basic system tweaks for performance,
## on top of my mid-range gaming setup
## my computer is literally as fast as a lightning bolt,
## This setup is literally like hyper-drive, file system operations are instantaneous
## and everything else is close behind instantaneous performance : D

## So like I usually do with debian
## I install a liquorix kernel, which is easy with it.
## On arch linux I would jump right into xanmod installed from aur
## or start compiling a custom tkg-kernel, but this process doesn't
## work as simply with debian, but anyways I will try to get these
## higher performance alternatives working later

https://liquorix.net/

## I think liquorix has f-sync patched into it
## which can be a major performance improvement,
## if it does, it is satisfactory as the main kernel
## to use for gaming, and I wont need to attempt to compile
## my own with custom patches

curl -s 'https://liquorix.net/install-liquorix.sh' | sudo bash

## the download -> install script
## for liquorix kernel fails with these error messages

E: The repository 'https://liquorix.net/debian n/a Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

## which is fixed by going into directory...

cd /etc/apt/sources.list.d

## and editing the sources adding in -> bookworm -> instead of "n/a"
## to look like this...

deb [arch=amd64 signed-by=/etc/apt/keyrings/liquorix-keyring.gpg] https://liquorix.net/debian bookworm main
deb-src [arch=amd64 signed-by=/etc/apt/keyrings/liquorix-keyring.gpg] https://liquorix.net/debian bookworm main

## update the package database

apt update

## and ran an apt search to pick out a kernel
## from my newly added liquorix repositories

apt update

## and installed a new custom liquorix kernel

apt install linux-image-liquorix-amd64

## reboot

shutdown -r now

## it seems like liquorix has 6.4 and 6.6 kernels
## and devuan has 6.1 by default, which could be a problem
## if certain programs are designed to only work with older kernels

## and upon first reboot
## it seems liquorix isn't working and it's not clear why
## but it looks like a variety of programs are running into each other
## locking up the system
## so I reboot into devuan's default kernel
## using the advanced options from grub menu to select it

## at this point it's going to take some troubleshooting
## and tinkering around to tweak the system for even more
## performance, but with this basic setup
## I am already in a great position to start gaming

## using cat /proc/cpuinfo and grep
## to see if performance mode in grub is applying to the kernel

root@ity:~# cat /proc/cpuinfo | grep MHz
cpu MHz        : 800.000
cpu MHz        : 800.000
cpu MHz        : 800.000
cpu MHz        : 800.000
cpu MHz        : 800.000
cpu MHz        : 800.000
cpu MHz        : 800.000
cpu MHz        : 800.000

## and it isn't

## looking for commands to alter the cpu mode
## I noticed some people metioning services altering
## the cpu_freq mode and decided to investigate it

root@ity:~# service --status-all
[ ? ]  alsa-utils
[ - ]  anacron
[ + ]  apparmor
[ - ]  bootlogd
[ - ]  bootlogs
[ - ]  bootmisc.sh
[ - ]  brightness
[ - ]  checkfs.sh
[ - ]  checkroot-bootclean.sh
[ - ]  checkroot.sh
[ + ]  connman
[ ? ]  cpufrequtils
[ + ]  cron
[ + ]  dbus
[ + ]  elogind
[ + ]  eudev
[ - ]  hostname.sh
[ ? ]  hwclock.sh
[ - ]  killprocs
[ ? ]  kmod
[ - ]  live-config
[ - ]  lm-sensors
[ ? ]  loadcpufreq
[ ? ]  mount-configfs
[ - ]  mountall-bootclean.sh
[ - ]  mountall.sh
[ - ]  mountdevsubfs.sh
[ - ]  mountkernfs.sh
[ - ]  mountnfs-bootclean.sh
[ - ]  mountnfs.sh
[ ? ]  networking
[ + ]  ntpsec
[ - ]  procps
[ - ]  rc.local
[ - ]  rmnologin
[ - ]  rsync
[ + ]  rsyslog
[ - ]  sendsigs
[ + ]  slim
[ - ]  stop-bootlogd
[ - ]  stop-bootlogd-single
[ - ]  sudo
[ + ]  ufw
[ - ]  umountfs
[ - ]  umountnfs.sh
[ - ]  umountroot
[ - ]  urandom
[ + ]  uuidd
[ - ]  x11-common

## looking in /etc/init.d
## I see the cpufrequtils init config

## and edit the line to default to performance mode and reboot

## to see if it alters the situation

root@ity:~#  cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
performance powersave

## editing /etc/init.d/cpufrequtils

mousepad /etc/init.d/cpufrequtils

ENABLE="true"
GOVERNOR="performance"

## I'm not really used to dealing with services in non-systemd or openrc systems
## so I'll have to learn more about devuans way of doing things

## I went back and tried editing the file again like this
## after first reboot it wasnt working...

mousepad /etc/init.d/cpufrequtils

ENABLE="true"
GOVERNOR="performance"
MAX_SPEED="3600000"
MIN_SPEED="3600000"

## I had to find out the min and max cpu frequency values using...

cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq
cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_min_freq

reboot

## and upon rebooting again I noticed the system is working
## as fast as a lightning bolt which makes me smile really widely : D D

## and checking the reported cpu frequencies reported by the kernel
## I see now everything is working appropriately, and I'm locked in at 3.6GHz
## for gaming : D

root@ity:~# cat /proc/cpuinfo | grep MHz
cpu MHz        : 3600.000
cpu MHz        : 3600.000
cpu MHz        : 3600.000
cpu MHz        : 3600.000
cpu MHz        : 3600.000
cpu MHz        : 3600.000
cpu MHz        : 3600.000
cpu MHz        : 3600.000

## at this point I remembered trying to use the liquorix kernel before
## and it seemed to run startup programs out of sync with each other creating
## a lockup scenario, and failing to get to the desktop envrionment, so I decided
## to reboot into it to see if locking down the cpu frequency altered the situation

## this time the system booted up properly, without programs running into each other
## and overlapping, but I got stuck at a login terminal, instead of booting
## into my desktop environment which is always what happens when I try to
## install custom kernels on devuan... : ' (

## anyways I will figure it out eventually and get it working

## when I tweak things some more and get more time to test different configurations
## I might update the post

## edit... 6 hours later

## okay I think I have it figured out now
## now here's some random notes with no explanation

init─┬─accounts-daemon───3*[{accounts-daemon}]
     ├─connmand
     ├─console-kit-dae───5*[{console-kit-dae}]
     ├─cron
     ├─2*[dbus-daemon]
     ├─dbus-launch
     ├─dunst───3*[{dunst}]
     ├─elogind-daemon
     ├─6*[getty]
     ├─gpg-agent
     ├─ntpd
     ├─polkitd───3*[{polkitd}]
     ├─rsyslogd───3*[{rsyslogd}]
     ├─slim─┬─Xorg───{Xorg}
     │      └─ck-launch-sessi───xfce4-session─┬─Thunar───3*[{Thunar}]
     │                                        ├─xfce4-panel─┬─panel-14-action──+++
     │                                        │             ├─panel-6-systray──+++
     │                                        │             ├─panel-8-pulseau──+++
     │                                        │             ├─xfce4-terminal─┬─+
     │                                        │             │                └─+
     │                                        │             └─3*[{xfce4-panel}]
     │                                        ├─xfdesktop───3*[{xfdesktop}]
     │                                        ├─xfsettingsd───2*[{xfsettingsd}]
     │                                        ├─xfwm4───2*[{xfwm4}]
     │                                        └─3*[{xfce4-session}]
     ├─udevd───udevd
     ├─upowerd───3*[{upowerd}]
     ├─uuidd
     ├─wpa_supplicant
     └─xfconfd───3*[{xfconfd}]
root@ity:~#

"/home/xfin/.local/share/xorg/Xorg.0.log"

[    25.469] (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
[    25.469] (EE) NVIDIA:     system's kernel log for additional error messages and
[    25.469] (EE) NVIDIA:     consult the NVIDIA README for details.
[    25.469] (EE) No devices detected.
[    25.469] (EE)
Fatal server error:
[    25.469] (EE) no screens found(EE)
[    25.469] (EE)
Please consult the The X.Org Foundation support
     at http://wiki.x.org

apt-get --reinstall install nvidia-driver

https://github.com/Frogging-Family/linux-tkg

https://github.com/Frogging-Family/nvidia-all

## apt install makepkg

dkms: autoinstall for kernel 6.6.2-1-liquorix-amd64 was skipped since the kernel headers for this kernel do not seem to be installed.

root@ity:~/nvidia-all# apt install linux-headers-liquorix-amd64 linux-image-liquorix-amd64

Building module:
Cleaning build area...
env NV_VERBOSE=1 make -j8 modules KERNEL_UNAME=6.6.2-1-liquorix-amd64........(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.6.2-1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/525.125.06/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.6.2-1-liquorix-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.6.2-1-liquorix-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.6.2-1-liquorix-amd64 (--configure):
installed linux-headers-6.6.2-1-liquorix-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-liquorix-amd64:
linux-headers-liquorix-amd64 depends on linux-headers-6.6.2-1-liquorix-amd64 (= 6.6-2.1~bookworm); however:
  Package linux-headers-6.6.2-1-liquorix-amd64 is not configured yet.

dpkg: error processing package linux-headers-liquorix-amd64 (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.36-9+deb12u3) ...
Errors were encountered while processing:
linux-headers-6.6.2-1-liquorix-amd64
linux-headers-liquorix-amd64

root@ity:~/nvidia-all# sudo apt install  linux-headers-6.6.2-1-liquorix-amd64

https://wiki.debian.org/NvidiaGraphicsDrivers

Before installing the drivers, you must obtain the proper kernel headers for the NVIDIA driver to build with.

apt install linux-headers-liquorix-amd64

https://dev1galaxy.org/viewtopic.php?id=5415

https://dev1galaxy.org/viewtopic.php?id=564

ls

~/linux-tkg/linux-src-git
-> Configuration done.
-> Installing udev rule for winesync
-> Adding winesync to '/etc/modules-load.d' for auto-loading by systemd - Password prompt incoming!
-> Enabled ccache
-> Building kernel DEB packages
  UPD     include/config/kernel.release
make clean
sh ./scripts/package/mkdebian
Using default distribution of 'unstable' in the changelog
Install lsb-release or set $KDEB_CHANGELOG_DIST explicitly
  TAR     linux-upstream.tar.gz
origversion=$(dpkg-parsechangelog -SVersion |sed 's/-[^-]*$//');\
    mv linux-upstream.tar.gz ../linux-upstream_${origversion}.orig.tar.gz
Can't locate Term/ANSIColor.pm in @INC (you may need to install the Term::ANSIColor module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl) at /usr/share/perl5/Dpkg/ErrorHandling.pm line 71.
dpkg-buildpackage -r"fakeroot -u" -a$(cat debian/arch)  -i.git -us -uc
Can't locate File/Copy.pm in @INC (you may need to install the File::Copy module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 /usr/local/lib/site_perl) at /usr/bin/dpkg-buildpackage line 28.
BEGIN failed--compilation aborted at /usr/bin/dpkg-buildpackage line 28.
make[1]: *** [scripts/Makefile.package:80: deb-pkg] Error 2
make: *** [Makefile:1656: deb-pkg] Error 2
-> exit cleanup done

Term::ANSIColor was first included with Perl in Perl 5.6.0.

root@ity:/etc# perl -v

This is perl 5, version 36, subversion 0 (v5.36.0)

## I figured out that the NVIDIA kernel module didn't appear to be loading properly
## with the liquorix kernel, so I figured that I didn't install it properly, so I reloaded my timeshift
## backup in order to make a clean slate with devuan in order to try to get it working again

## then I installed first the liquorix-headers file from it's repository
## which failed to build the kernel modules
## then the liquorix kernel, and then some other stuff I can't remember
## all of which failed

## then I tried using the tkg-linux source files and tkg-nvidia source files
## to build a custom kernel, which I think failed because in devuan there is
## only perl version 3.36 and it expects version 3.6

## that all comprised maybe 3-4 hours after 2 hours of reading documentation
## and doing basic configurations all over the place

## so i think I'm on the right track though and am toying with
## the idea of using a how-to on the forum for building a kernel on devuan
## as a point of reference for getting a custom-gaming kernel working on here

https://dev1galaxy.org/viewtopic.php?id=564

## and maybe if I update some packages from debians bookworm repository
## I can get the tkg-linux scripts to work which have all of that built in, but
## expect package versions to be more up-to-date like arch linux

## I think a lot of the problems I have been running into have revolved
## around versioning/dependency errors that are mismatched between
## all the various distros/development cycles/and development projects

## but based on my extensive experience, having tested and worked with
## basically 80% of all the linux distros over the years I think im on the right
## track with using Crowz->Devuan-Daedalus for literally the Ultimate Linux Hyper Drive Gaming System
## right now my system is already so lightning fast I want to skip all the technical work
## and just put it to work running circles around all those snarky windows users in some online games

## Based on my experience I think there is no better alternative to get the highest possible performance
## for linux gaming right now, I just have to work out more technical details, get more experience using devuan
## to fully unlock it's potential

## edit 12 hours after installation

## I finally got a custom gaming kernel working

## I figured out after endless trial and error, and alternate configurations

## You need an equal kernel version to what devuan is using

## and you need to install the kernel headers first(I think?)
## or nvidia's module wont properly build, or it's some other problem,
## I don't know because i keep getting the same error messages now,
## and the same exact error messages apparently represent completely different problems!
## but hey that is linux, it's totally insane...

## to install the xanmod kernel for devuan I had to...
## quoted mostly from the xanmod website...

1. Register the PGP key:

wget -qO - https://dl.xanmod.org/archive.key | sudo gpg --dearmor -o /usr/share/keyrings/xanmod-archive-keyring.gpg

2. Add the repository:

echo 'deb [signed-by=/usr/share/keyrings/xanmod-archive-keyring.gpg] http://deb.xanmod.org releases main' | sudo tee /etc/apt/sources.list.d/xanmod-release.list

##. Then update

apt update

## Then use apt search to find the right kernel for your system
##  (turn on unlimited scrolling in your terminal program)
## or like apt search xanmod | grep 6.1

apt search xanmod

### Then install

apt  install linux-headers-6.1.35-x64v3-xanmod1 linux-image-6.1.35-x64v3-xanmod1

## my cpu architecture is x86_64 v3 for other people it would be different....but what is also important
## is that I picked out a kernel version next to what devuan is using i.e. 6.1
## so my graphics driver could properly build against it,
## anyways it's a real ugly duckling this devuan system, it's going to take a lot of love to clean it up and
## tweak it out, but this is the absolute leanest and meanest Linux gaming system in the entire linux Universe
## she sits at 487 MB of RAM usage after login, with no apps open, in the xfce desktop environment
## which is literally almost exactly two times
## less than all of the competitors I have tried out.

## This system with Xanmod -> Crowz-Devuan -> on top of an ssd with F2FS
## and some mid range gaming hardware is literally screaming fast,
## and runs like a super car, I can barely control, it's so sensitive, and powerful