necessary target system headers (<fs/unicode.h> and <fs/cd9660/iso.h>)
because system headers for the host (like <sys/stat.h>) are also pulled
from there and it causes build errors if target src tree is different
from installed one on the host.
Instead, copy the necessary system headers for host's programs into
${.OBJDIR} first.
Problem reported from Geert Hendrickx, and there is no particular comment
on tech-toolchain.
newfs and mount the target filesystem.
In Hauke's words: "Basically, the mac68k md_make_bsd_partitions() function,
which replaces the MI make_bsd_partitions() because the mac68k port does not
have an on-disk BSD disklabel, neglected to sign up BSD partitions for
newfs'ing and mounting by setting the appropriate flags."
Revert the commit to the install notes (rev. 1.14 of notes/mac68k/prep) which
added a warning and a workaround for this bug, as requested by hubertf in the
PR log.
happen in the TCP stack, this interface calls the specified callback to
handle the situation according to the currently selected congestion
control algorithm.
A new sysctl node was created: net.inet.tcp.congctl.{available,selected}
with obvious meanings.
The old net.inet.tcp.newreno MIB was removed.
The API is discussed in tcp_congctl(9).
In the near future, it will be possible to selected a congestion control
algorithm on a per-socket basis.
Discussed on tech-net and reviewed by <yamt>.
subsystems, based on work by YAMAMOTO Takashi. This is intended to
be used by other subsystems (such as the proc_*() or lwp_*() routines)
rather than directly by consumers.
instead you have config_search_{loc,ia}. Add documentation for
config_finalize_regsiter, too. Mostly fixes PR#32106 by Gavan Fantom, as I
think the cfdriver_* and cfattach_* stuff should be documented too, but I'm
not entirely sure where yet.
I have commited a different version than in the PR, it lacks a license
but if it warrants one we can stick the TNF standard on it. It's just
a main() routine that calls revoke(2).
"yes", and abort if it is "no" - not vice versa.
XXX - when returning to the utilities menu loop, the menu message should
be output again, I think. I couldn't figure out how that is supposed to
be done though.
