ENOSYS here just means that the mkdir system call isn't implemented for that filesystem. I suppose it could possibly return ENOTSUP instead.

POSIX doesn't seem to say anything on the matter

`mkdir /proc/fred` on Linux returns ENOENT

it'd be more like `mkdir /proc/1` on Linux, right? /dev/zvol/rdsk/ does exist

I wonder how to set up illumos do I can have working SerialOver LAN , I use Intel AMT KVM integrated in HP 800 G4 PCs and it works (With Mesh Commander on local web page

But When I try using SerialOverLan I get it working on machine reboot, I get it working only in Loader (SmartOS) but later after booting kernel I don't get SoL working anymore, it stops working.

Maybe I need some parameters to set up in distro after working, so that serial connection survives after booting kernel and continues to work.

Serial connection is much better if one wants to work with terminal or VT's and not GUI that is non-existant.

Does UMEM_SLAB_MEMBER look wrong to anyone else?

shouldn't it be compared to base + cache_slabsize?

It looks ok to me. A bit simpler than `buf >= base and buf <= base + size` and no potential overflow to deal with.

s/<=/</

ohhhh, now I get it, sigh

that might be the first time I've seen this method

It does look odd at first glance, especially with relying on wrapping around zero if buf < base (hence the casts to an unsigned type I imagine)