Age | Commit message (Collapse) | Author |
|
It is currently not possible to remove an rtable; claudio made the default
rtable of an rdomain move back into the default rdomain upon deletion of the
non-default rdmoain with sys/net/if_loop.c r1.90 - previously such orphaned
rtables would also continue to exist as well be assigned to any existent
rdomain.
Document the status quo under CAVEATS as it seems unexpected behaviour and
the manual otherwise does not talk about deletion/invaldation of an rtable
at all.
OK remi jmc
|
|
Those do not need root privileges to work.
Prompted by jmc
|
|
It's handy and otherwise easily missed when reading up on routing domains
and tables; wording taken from netstat(1) as is.
Not listing pgrep(1)'s `-T' because examples don't have to be exhaustive and
ps(1) is already demonstrated; same for top(1) users which more likely come
across its `t' and `T' in the help page anyway (I guess).
OK jmc remi
|
|
Pointed out by jsg@
|
|
|
|
|
|
OK jmc@, kn@, "go for it" kettenis@
|
|
ok mglocker
|
|
ok kettenis@
|
|
|
|
|
|
|
|
ok phessler
|
|
|
|
|
|
|
|
|
|
Remove obsolete sysctl_int_arr documentation.
Looks good, deraadt@
reads ok, jmc@
|
|
|
|
|
|
|
|
|
|
Diff from Uwe Werler <uwe at werler dot is>, thanks.
tpmr(4) is really a bridge like bridge(4) or switch(4), and not an
aggregating driver like aggr(4) or trunk(4), hence
"Other forms of Ethernat bridging ..." correctly implies that tpmr does
indeed ethernet bridging, "Other forms of aggregation ..." implies the
same way, but is misleading however, so just say "Link aggregation ...".
OK jmc
|
|
ifconfig(8)'s TRUNK (LINK AGGREGATION) nicely combines the two drivers, so
omit common stuff from the drives specific manuals.
This aids in the overall design of having options documented in ifconfig(8)
alone unless they're inherently driver specific, e.g. "trunkproto" which
stays in trunk(4).
OK jmc
|
|
|
|
ok jmc@
|
|
|
|
ok jcs@
|
|
ok jmatthew@
|
|
|
|
from navan airpost net
|
|
|
|
simplifications, add missing markup, and break an overlong line
|
|
pipex(4) sessions. We did this for prevent use after free issue caused
by pipex_timer(). By default "idle-timeout" is not set in
npppd.conf(5) and I guess this is reason for we forgot to describe this
exception in npppd.conf(5).
Since it's pppx(4) related bug description was added to BUGS section of
pppx(4) man page.
npppd.conf(5) has this exception described in "idle-timeout" section.
ok jmc@ yasuoka@
|
|
RFC 4291 dropped this requirement from RFC 3513:
o An anycast address must not be used as the source address of an
IPv6 packet.
And from that requirement draft-itojun-ipv6-tcp-to-anycast rightly
concluded that TCP connections must be prevented.
The draft also states:
The proposed method MUST be removed when one of the following events
happens in the future:
o Restriction imposed on IPv6 anycast address is loosened, so that
anycast address can be placed into source address field of the IPv6
header[...]
OK jca
|
|
These two interfaces have been entirely unused since introduction.
Remove them and thin the "timeout" namespace a bit.
Discussed with mpi@ and ratchov@ almost a year ago, though I blocked
the change at that time. Also discussed with visa@.
ok visa@, mpi@
|
|
|
|
Add missing TPMR section to ifconfig(8) by moving the commands from the
driver's manual to it (copy/paste) and document the ioctl(2) interface in
tpmr(4).
Indenting tpmr's first EXAMPLE while here; from jmc.
OK jmc
|
|
Spotted by schwarze@, discussed with kn@ and schwarze@
|
|
the SYNOPSIS with the modern .Fo idiom; no output change
|
|
it reads better to me. it might be worth considering this for
queue(3) too.
|
|
|
|
|
|
removal of the vnode interlock in 2007.
Reported by and original diff from Dominik Schreilechner.
OK jmc@
|
|
OK kn@, "fine" deraadt@
|
|
|
|
on any platform. Mention this here, as done for AX201 in the iwx(4) page.
|
|
|
|
|
|
from threads other than the one currently having kcov enabled. A thread
with kcov enabled occasionally delegates work to another thread,
collecting coverage from such threads improves the ability of syzkaller
to correlate side effects in the kernel caused by issuing a syscall.
Remote coverage is divided into subsystems. The only supported subsystem
right now collects coverage from scheduled tasks and timeouts on behalf
of a kcov enabled thread. In order to make this work `struct task' and
`struct timeout' must be extended with a new field keeping track of the
process that scheduled the task/timeout. Both aforementioned structures
have therefore increased with the size of a pointer on all
architectures.
The kernel API is documented in a new kcov_remote_register(9) manual.
Remote coverage is also supported by kcov on NetBSD and Linux.
ok mpi@
|