eudev starts at boot; Xorg finds its input devices through it

udevd and a one-shot trigger run from schinit, 10-schos.conf no longer lists
event0/event1, and the docs say what udev covers and what it does not.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EVRhxi9zpdW2uDUN4FVcao

etc/schinit/udev-trigger.job

@@ -0,0 +1,14 @@
+# Replay the devices that were already there when udevd started, so /run/udev
+# knows about them. Runs once; see /etc/udev-trigger.
+#
+# udevd is started by its own job and schinit has no ordering, so the script
+# waits for the daemon's control socket.
+
+Label     = os.schos.udev-trigger
+Program   = /bin/sh
+Args      = sh /etc/udev-trigger
+RunAtLoad = yes
+KeepAlive = no
+
+StandardOut   = /dev/tty1
+StandardError = /dev/tty1

etc/schinit/udevd.job

@@ -0,0 +1,16 @@
+# eudev's daemon: the thing that turns the kernel's uevents into /run/udev
+# data and /dev symlinks, which is how Xorg and every Wayland compositor learn
+# what input and display devices exist.
+#
+# Alpine's eudev package; the kernel side is the uevent netlink socket and the
+# /sys device tree (kernel/dev/kdev.c, kernel/fs/sysfs.c).
+
+Label     = os.schos.udevd
+Program   = /sbin/udevd
+Args      = udevd
+RunAtLoad = yes
+KeepAlive = yes
+ThrottleInterval = 3
+
+StandardOut   = /dev/tty1
+StandardError = /dev/tty1