Re: Devices.

to: - To provide an API for device drivers to manage their own device nodes, - To allow for auto-discovery/creation of device nodes, - To allow complex devices to own their own complexity, - To provide a sensible default policy for common cases, - With the ability to override for specific use cases, - To (optionally) provide a MAC security policy in /dev, - And reduce the clutter. jf -- John Franklin frank...@elfie.org signature.asc Description: PGP signature

Re: partial failures in write(2) (and read(2))

so much for the kernel’s system call. I suppose libc could set a default handler for the new signal, and do some extra work to set errno. Apps that need more control can override the signal hander. jf -- John Franklin frank...@elfie.org

Re: Issues with intelfb(4) and USB keyboards

be log entries in there about reported EDID information, what display outputs the driver can see, and maybe something about which one it's choosing. jf -- John Franklin frank...@elfie.org

Re: kernel frameworks for jumbo frame

lti-NIC servers, and allowed for arbitrarily complex situations. It’s only in the infrequent case of a replacement NIC that would force an admin to find and update the udev rules (he’s in there already updating the hardware!), which IMHO, falls under Works As Intended. Splitting eth0 vs wifi0 makes sense to me, as the inherent nature of the devices are fundamentally different. jf -- John Franklin frank...@elfie.org smime.p7s Description: S/MIME cryptographic signature