> On 4 Mar 2026, at 16:22, John G. Heim <[email protected]> wrote: > > It's no different than a monitor. > > I am a little disappointed by the amount of pushback I'm getting on this. > What if you had to log in and load a kernel module to get your monitor to > work? You're a server admin, you go into the server room to look at a down > server. You plug in a monitor and it's just blank. You have to log in and > type in a commend -- with the monitor blank -- to get started. Of course, if > the machine isn't even at the login prompt, and it's probably not, just > trying to blindly type in your login credentials isn't going to do anything. > > This is real life for a blind systems admin or systems engineer. People's > jobs depend on this. This is how I put food on the table for my entire career. > > Instead of thinking up reasons to *not* do it, how about if we try to figure > out ways to get it done? > I agree this is a real life issue.
I'm not sure if systemd or the distros are best placed to solve this issue. You might find that asking the distros to add the udev rule would work to get this going. Barry > > > > > On 3/4/26 1:59 AM, Windl, Ulrich wrote: >> …unless some other admin considers that to be a security risk… >> >> Kind regards, >> Ulrich Windl >> From: systemd-devel <[email protected]> >> <mailto:[email protected]> On Behalf Of John G. >> Heim >> Sent: Wednesday, February 25, 2026 11:26 PM >> To: Adrian Vovk <[email protected]> <mailto:[email protected]> >> Cc: [email protected] >> <mailto:[email protected]> >> Subject: [EXT] Re: [systemd-devel] Udev rules for hardware speech synths >> >> [Windl, Ulrich] (…) >> If we can get the kernel to recognize hardware speech synths, a blind >> systems engineer will be able to walk up to any Linux server, plug in his >> hardware synth, and listen to it boot. >> >> [Windl, Ulrich] (…) >>
