Then you need to broaden your horizons and try Gentoo and see how far you get with “no-hands-on” approach!!!
2 Likes
You are far from being an ordinary user, Daniel. Trades people make good computer users… my family were blacksmiths.
I think trades poeple are trained to think out a problem rather than follow a book of rules.
In all education one first has to learn a heap of facts, and then secondly learn how to apply them. Computer education is no different… struggling users are of two types… either they dont want to learn anything or they have never been shown how to apply knowledge.
‘How to’ documents are no substitute for the understanding that comes with proper education. They are a substitute for thinking it out for yourself.
5 Likes
And this is not arcane… how?
Thing with the Linux CLI vs the Windows CLI is that the Linux CLI is actually well documented. For this knowledge regarding Windows you need to look exactly where?
It’s actually quite possible to become an advanced CLI user in Linux, while it’s neigh impossible to do the same with Windows, exactly because the documentation is nowhere to be found.
2 Likes
And that is why I document all commands, Linux and Windows!!!
1 Like
I dont think i am capable now of doing that in windows and really cannot see why I would.. if I try really hard could guess some lines but nothing worth doing. Perhaps chkdsk but not sure it would work.
1 Like
Same. The only thing I can do is winget update and wsl enter.
1 Like
I stopped using Windows a long time ago. Too buggy, unstable and malware.
I stopped using the Linux CLI a while ago, but, if need be, I can quickly find my way. There’s good documentation out there and the manual pages are frequently helpful enough.
Systemd is more of an issue, though. I find those unit files more complicated than the simple bash scripts of runit in Void Linux. On top of that systemd is littered with solutions looking for a problem; journald is an example of that, and a bad one at that.
I have never tried s6 or s6-66. So, I’m curious: what do people think of them?
2 Likes
s6-66 is definitely a contender to replace systemd in complicated server systems. It has all the functionality of systemd without those abhorrent invasive parts like journals.
Dinit is simpler than runit. It has config files instead of scripts… and all its configs are in one place, not spread all over /etc and /var. I would say dinit is the choice for home systems. To try dinit use Artix or Chimera.
2 Likes
Could you post an example of a dinit config file?
1 Like
From my Artix installation, the config file for sshd
trinity:[nevj]:/etc/dinit.d$ cat sshd
type = process
command = /usr/bin/sshd -D
smooth-recovery = true
depends-on = ssh-keygen
depends-on = network.target
before = login.target
The config files are all in one directory
trinity:[nevj]:/etc/dinit.d$ ls -F
acpid cupsd 'getty@tty4' lvm2 rpcbind
avahi-daemon dbus 'getty@tty5' lvm-monitor rsync
bluetoothd dbus-pre 'getty@tty6' lvmpolld sshd
boot.d/ dhcpcd git lvmpolld-pre ssh-keygen
config/ dmeventd git-pre mdadm statd
connmand elogind haveged metalog wpa_supplicant
cronie 'getty@tty1' lightdm mount.d/
cryptsetup 'getty@tty2' lightdm-pre nfs-server
cryptsetup-early 'getty@tty3' logind ntpd
The two subdirectories boot.d and mount.d contain links to things that must start at boot time. The config directory contains more .conf files for things like consoles and network.
That is all. No links except those special ones in boot.d and mount.d.
Another example config file for bluetoothd
trinity:[nevj]:/etc/dinit.d$ cat bluetoothd
type = process
command = /usr/lib/dinit/dbus-wait-for -s -f 4 -n org.bluez /usr/lib/bluetooth/bluetoothd
smooth-recovery = true
logfile = /var/log/dinit/bluetoothd.log
depends-on = dbus
depends-on = local.target
before = login.target
ready-notification = pipefd:4
Most of them just give the command to start the daemon, where the logfile is, and any dependencies.
In Artix , you would rarely have to write a config file… its packages install the config file if they are for a daemon needing a config file.
system/openssh 10.0p1-4 [installed]
SSH protocol implementation for remote login, command execution and file
transfer
system/openssh-dinit 20230906-3 (dinit-system) [installed]
dinit service scripts for openssh
There are the 2 packages for openssh. The dinit config files are a separate package from the binaries.
The only thing you see running is dinit and the daemons
trinity:[nevj]:/etc/dinit.d$ ps ax | grep dinit
1 ? S 0:00 /usr/bin/dinit
The init process is called dinit, not init.
There are no supervisory processes like in runit.
You can have user-controlled services in dinit. The config files for these are in $HOME/.config/dinit.d.
There is also /lib/dinit.d which seems to contain templates.
Here is where dinit comes from
3 Likes
That’s simple. I do appreciate that it’s simple to discern what’s what. You don’t need a manual page to understand what’s happening.
If I ever distrohop again, I think I’ll head over to Artix with dinit.
2 Likes
There may be other distros offering dinit soon.
I would bet on Antix or MX. Less likely Void or Gentoo.
and beware
It is one thing to offer dinit
It is another thing to configure all your packages to support it.
2 Likes