* Fix typo (defautls).
* Don't use hard sentence breaks in new text.
* Don't introduce the use of the second person (you).
* Use the standard "IMPLEMENTATION NOTES" section name instead of the
non-standard "TUNING".
Although it can go higher, it is not safe to so do on arrays with many
members. Compromise by adding a tunable, "hw.aac.iosize_max" that can be
set at boottime. Also document in the aac(4) manpage.
MFC after: 4 weeks
should not use a `%' in examples.
I don't know if this is the consensus of doc@, or just a unilateral decision
of committer that corrected my following of this example. Maybe a docs
person could review these files and see if they still show current guidelines.
who didn't realize that DDB_UNATTENDED just sets its starting
value.
This change is over 5 years late, and documents the original
semantics of debug.debugger_on_panic, which may have been changed
by the (again undocumented) change in rev 1.44 of kern_shutdown.c.
us anyway because it doesn't work right on the x86 and alpha. On
K&R code, small ints would be promoted to int. ANSI-C doesn't require
this and the small ints can be passed taking 8 or 16 bits of stack
space. However, the x86 abi that we use *does* promote to 32 bit,
and the alpha ABI passes them in 64 bit registers so we dont have
that aspect of the problem here. Losing float precision by having it
cast down to int because the funtion prototype specifies int is the
least of our problems. -Wmissing-prototypes helps here anyway.
net.link.ether.bridge_refresh variables. While I'm here, try to
make some of the markup on this page more consistent with the
new (markup-reviewed) content.
PR: 22060
Reviewed by: ru (for markup, on an earlier version of this delta)
MFC after: 2 days
blown over by the Hurricane and had a house dropped on you by the Tornado.
Now it's time to have your parade rained on by... the Typhoon!
This commit adds driver support for 3Com 3cR990 10/100 ethernet
adapters based on the Typhoon I and Typhoon II chipsets. This is actually
a port of the OpenBSD driver with many hacks by me.
No Virginia, there isn't any support for the hardware crypto yet. However
there is support for TCP/IP checksum offload and VLANs.
Special thanks go to Jason Wright, Aaron Campbell and Theo de Raadt for
squeezing enough info out of 3Com to get this written, and for doing
most of the hard work.
Manual page is included. Compiled as a module and included in GENERIC.
building a .cf file from a .mc file.
Include -D_FFR_TLS_O_T to enable tls policy control since the sendmail binary
build enables that FFR as well.
PR: conf/28361
MFC after: 1 week
functions shouldn't have the first word capitalized, and shouldn't
have a period at the end. This is how most of our programs, and most
(all?) of the 4.4BSD programs, are. In the past, we've even done
sweeps to change things to comply to this.
ppp in 4.x apparently does a close(2) after opening the tun device;
i4brunppp starts up with only file descriptors 0 and 1 open (to the rbch
device) -> tun gets opened as 2 -> tun gets closed -> later use results
in EBADF. A quick fix to i4brunppp.c makes the thing work (I know, this
is ugly, but I needed it up quick...):
Submitted by: Juha-Matti Liukkonen <jml@cubical.fi>
be malloc()ed, but they are now allocated using mmap(), just as the
default-size stacks are. A separate cache of stacks is kept for
non-default-size stacks.
Collaboration with: deischen
the SYNOPSIS hasn't had an example number of devices since rev 1.2 which
was over 5 and a half years ago, so remove a sentence claiming that the
example in the SYNOPSIS limited bpf to 16 devices.
MFC after: 3 days
to have the $FreeBSD$ keyword, as this is now enforced
by the CVSROOT/commit_prep.pl script.
Fold multi-word macro arguments into a single argument
by putting the surrounding double quotes - this speeds
up the -mdoc processing drastically (of course if used
systematically).
Use the new features of -mdoc: exact -width specifiers,
.In macro as an ``.Fd #include'' replacement.
