On Tue, Nov 11, 2025 at 10:49 AM Michael Banck <mbanck@gmx.net> wrote:
> |login: task ./test_signalhandler(767) looked up a bogus port 23 for3205, most probably a bug.
. o O { An absurdly far-fetched thought while browsing glibc/hurd glue
code: if synchronous I/O is implemented as RPC on Mach ports, could
that mean that it's technically possible to submit now and consume
results later, for asynchronous I/O? Possibly too
private/undocumented anyway, and maybe they'll eventually do io_uring
or something... I idly wondered about driving I/O directly with ports
while studying the dismal implementation of POSIX AIO on macOS, which
also derives from CMU Mach, but NeXT/Apple jammed file systems down
into the unikernel part behind traditional syscalls, and it looks like
maybe only raw devices are accessible with ports. (I have dim
memories of learning C and assembler more than 30 years ago on a
Commodore Amiga whose microkernel nee Cambridge TRIPOS worked like
that... that cheap home computer could easily get both floppy drives
doing random I/O at once while computing other stuff, unlike Unix...)
}
