4 ms·
Hmm, interesting thanks. Given the name IO..ctl, is this unintended or unavoidable behaviour?
by _hilro 5y ago
Hmm, interesting thanks.
Given the name IO..ctl, is this unintended or unavoidable behaviour?
- phendrenad2 5y agoThe name probably originally came from controlling i/o ports and devices at a meta level. But they're just a mechanism for sending a chunk of data to the kernel, and if something in the kernel is watching that path (e.g. /sys/foobar) then it'll be in invoked. This is apparently how audio works on Linux. The kernel abstracts over sound devices, and provides a sort of "virtual device" at /proc/asound (https://www.kernel.org/doc/html/latest/sound/designs/procfile.html https://www.kernel.org/doc/html/latest/sound/designs/procfil...)