Age | Commit message (Collapse) | Author |
|
3rd (variadic) mode_t parameter is irrelevant. Many developers in the past
have passed mode_t (0, 044, 0644, or such), which might lead future people
to copy this broken idiom, and perhaps even believe this parameter has some
meaning or implication or application. Delete them all.
This comes out of a conversation where tb@ noticed that a strange (but
intentional) pledge behaviour is to always knock-out high-bits from
mode_t on a number of system calls as a safety factor, and his bewilderment
that this appeared to be happening against valid modes (at least visually),
but no sorry, they are all irrelevant junk. They could all be 0xdeafbeef.
ok millert
|
|
Replace the hand-written routing with a proper library allowing even more
formats.
Since ldomctl's local util.h conflicts with the now used global util.h from
libutil, rename it to ldom_util.h.
Manual wording from amd64's vm.conf(5).
OK kettenis
|
|
|
|
shorter. This subtly reduces the impact of truncation effects, as the
truncation is less likely, and if it exists it may be detected
directly by the system call with a proper error check. (this strange
justification is sadly valid in a world where people moan oh so loudly
about truncation but then don't audit and fix all instances)
ok kettenis
|
|
|
|
This is done by opening the corresponding /dev/vdspN device file. The virtual
disk will remain available until that device is closed, which happens
automatically when ldomd(8) exits.
|
|
|
|
reconfigure. Makes it possible to use ldomctl(8) when ldomd(8) is running.
|
|
|
|
to handle multiple channels. Use it to provide the var-config domain service
to all the currently configured guest domains.
|
|
that provides some essential services to guest domains.
|