void-runit VS mdev-like-a-boss

It was merged in January but a release wasn't tagged until recently. I doubt anybody had systemd in mind when choosing the paths; the use of *.d names to describe directories that are "assembled" to form a cohesive configuration pre-dates systemd.

That's a neat change in the void-runit package! Unfortunately this not yet in the official runit-void package. The current version there does not have the shutdown.d folder, so currently I also don't see an easy way to handle this.

Did you edit https://github.com/void-linux/void-runit/blob/master/core-services/02-udev.sh with something like like mdevd -O 4 mdevd-coldplug? which initram if any?

By the way zzz is just a shell script. You can find it here: https://github.com/void-linux/void-runit/blob/master/zzz

and here is more bloated void-runit

Maybe this could be related: https://github.com/void-linux/void-runit/pull/81

Void Linux honors the cache file for boot-time imports. The pool holding any root will have already been imported by the initramfs, but other pools will not be imported by the initramfs unless automatic rootfs detection is used.

Runit has run levels. It scrapes the kernel command-line for a level that matches a service directory.

mdev-like-a-boss: https://github.com/slashbeast/mdev-like-a-boss

# Configuration based on 'mdev-like-a-boss'. # https://github.com/slashbeast/mdev-like-a-boss/blob/master/mdev.conf null root:root 666 @chmod 666 $MDEV zero root:root 666 full root:root 666 random root:root 444 urandom root:root 444 hwrandom root:root 444 grsec root:root 660 kmem root:root 640 mem root:root 640 port root:root 640 console root:tty 600 @chmod 600 $MDEV ptmx root:tty 666 pty.* root:tty 660 tty root:tty 666 tty[0-9]* root:tty 660 vcsa*[0-9]* root:tty 660 # Kernel based virtual machine. kvm root:kvm 660 vhost-net root:kvm 660 # Block devices. ram([0-9]*) root:disk 660 >rd/%1 loop([0-9]+) root:disk 660 >loop/%1 sr[0-9]* root:cdrom 660 @ln -sf $MDEV cdrom fd[0-9]* root:floppy 660 net/tun[0-9]* root:root 666 net/tap[0-9]* root:root 600 fuse root:root 666 agpgart root:root 660 >misc/ psaux root:root 660 >misc/ rtc root:root 664 >misc/ # Audio stuff. adsp root:audio 660 >sound/ audio root:audio 660 >sound/ dsp root:audio 660 >sound/ mixer root:audio 660 >sound/ sequencer.* root:audio 660 >sound/ snd/.* root:audio 660 # Raid controllers. cciss!(.*) root:disk 660 =cciss/%1 ida!(.*) root:disk 660 =ida/%1 rd!(.*) root:disk 660 =rd/%1 # Input stuff. SUBSYSTEM=input;.* root:input 660 # Video stuff. card[0-9] root:video 660 =dri/ vbi[0-9] root:video 660 >v4l/ video[0-9] root:video 660 >v4l/ dri/.* root:video 660 # Don't create old usbdev* devices. usbdev[0-9].[0-9]* root:root 660 ! # Stop creating x:x:x:x which looks like /dev/dm-*. [0-9]+\:[0-9]+\:[0-9]+\:[0-9]+ root:root 660 ! # /dev/cpu support. microcode root:root 600 =cpu/ cpu([0-9]+) root:root 600 =cpu/%1/cpuid msr([0-9]+) root:root 600 =cpu/%1/msr

As illiliti said, not using a device manager creates a lot of obstacles. There's a reason they were created. If your needs are simple (your USB devices rarely come unplugged, you only have one disk, etc.), you don't really need a device manager. I'm not *really* using one (I'm fiddling with `smdev` right now, and didn't use any device manager for several months last year). Setting /dev permissions is one of the more valuable parts a device manager provides. You might want to look at mdev like a boss or the Gentoo article for some information. If you don't understand what those articles are talking about, you have a fair bit more reading to do. I currently set my permissions on specific devices via a file in /etc/rc.d, but because /dev is populated in a volatile way some permissions aren't set while others are.