| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
length modifier for the difference between two pointers.
MFC after: 1 week
|
|
|
|
|
|
|
| |
minutes of activity, to avoid a warning on platforms where time_t is a
32-bit integer.
MFC after: 1 week
|
|
|
|
| |
Noticed by: jilles
|
|
|
|
|
|
| |
No change in rendered output, less mandoc lint warnings.
Tool provided by: Nobuyuki Koganemaru n-kogane at syd.odn.ne.jp
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Just like bin/ and sbin/, I think setting WARNS to the highest value
possible will make it more attractive for people to fix warnings.
- The WARNS variable is set in the Makefile in the directory of the
application itself, making it more likely that it will be removed out
of curiosity to see what happens.
- New applications will most likely build with WARNS=6 out of the box,
because the author would more likely fix the warnings during
development than lower WARNS.
Unfortunately almost all apps in libexec require a lowered value of
WARNS.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. separating L2 tables (ARP, NDP) from the L3 routing tables
2. removing as much locking dependencies among these layers as
possible to allow for some parallelism in the search operations
3. simplify the logic in the routing code,
The most notable end result is the obsolescent of the route
cloning (RTF_CLONING) concept, which translated into code reduction
in both IPv4 ARP and IPv6 NDP related modules, and size reduction in
struct rtentry{}. The change in design obsoletes the semantics of
RTF_CLONING, RTF_WASCLONE and RTF_LLINFO routing flags. The userland
applications such as "arp" and "ndp" have been modified to reflect
those changes. The output from "netstat -r" shows only the routing
entries.
Quite a few developers have contributed to this project in the
past: Glebius Smirnoff, Luigi Rizzo, Alessandro Cerri, and
Andre Oppermann. And most recently:
- Kip Macy revised the locking code completely, thus completing
the last piece of the puzzle, Kip has also been conducting
active functional testing
- Sam Leffler has helped me improving/refactoring the code, and
provided valuable reviews
- Julian Elischer setup the perforce tree for me and has helped
me maintaining that branch before the svn conversion
|
|
|
|
|
|
|
|
|
| |
POSIX. This also makes the struct correct we ever implement an i386-time64
architecture. Not that we need too.
Reviewed by: imp, brooks
Approved by: njl (acpica), des (no objects, touches procfs)
Tested with: make universe
|
|
|
|
| |
socklen_t * argument.
|
| |
|
| |
|
|
|
|
| |
OK'ed by: core
|
|
|
|
| |
any fake value.
|
|
|
|
| |
expects.
|
| |
|
| |
|
|
|
|
| |
Minor markup tweaks.
|
|
|
|
|
|
|
|
| |
While I'm here, sync the usage() synopsis with the manual page synopsis:
make the [-i | -s] explicit and sort the options alphabetically.
Reminded by: ru
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
ever since rev. 1.1 of bootpd.c.
While I'm here, rearrange the synopsis a bit: sort the options and
clarify that -i and -s are mutually exclusive.
Reported by: Atanas Buchvarov <nasko@nove.bg>
MFC after: 3 days
|
|
|
|
| |
From NetBSD's bootpd (in src/usr.sbin/bootp)
|
|
|
|
| |
select is broken.
|
| |
|
|
|
|
| |
Add FreeBSD Id tag where missing.
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 2 weeks
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Remove private __P.
|
|
|
|
| |
Remove private __P.
|
| |
|
|
|
|
| |
Reviewed by: md5
|
|
|
|
| |
(get_errmsg -> get_errmsg())
|
|
|
|
|
|
| |
PR: bin/30864
Obtained from: Dan Lukes <dan@obluda.cz>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
"unkown error" [sic]. Add the missing breaks, and correct the
spelling typo.
PR: bin/30865
Submitted by: Dan Lukes <dan@obluda.cz>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
refers to the size of the whole ethernet packet, just the DHCP
message within the UDP payload, or something else. bootpd interpreted
it as a maximum UDP payload size, so it could end up sending
fragmented packets to clients (such as some versions of Etherboot)
that used different interpretations of the maximum message size.
Switch to the most conservative interpretation: ensure that the
ethernet packet containing the response is no larger than the
specified maximum message size. This matches the behaviour of
the ISC dhcpd.
MFC after: 1 week
|
|
|
|
| |
with a trailing zero-width space: `e.g.\&'.
|
| |
|
|
|
|
| |
- MAN[1-9] -> MAN.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Use _PATH_* where where possible.
|
| |
|
| |
|
| |
|