Strictly speaking this is unnecessary, but it allows nanobsd to work
on systems from before the -x and -y arguments to mdconfig(8) worked
for vnode backing.
Submitted by: "Oivind H. Danielsen" <oivind.danielsen@kopek.net>
from the gdb(1) register number to offsets within struct reg and
struct fpreg. The tool is useful only on selected platforms. On
ia64 the registers are all over the place to simplify handling of
them in various situations, but which makes creating or maintaining
such an offset table error prone to do by hand.
Since remote kernel debugging operates on the same register numbers,
it would be a natural choice to use an identical offset table in the
kernel. However, since the kernel does not operate on struct reg nor
struct fpreg in the remote gdb(1) case, such would not make sense.
Whether we want to use this tool to create offsets for use in the
kernel or duplicate the knowledge of which register number maps to
what register is something that will become clear soon.
Note: in order to build cross debuggers, one cannot use target
headers and/or target definitions. That's why offsets need to be
hardcoded in the first place. Unpleasant, but necessary.
improve readability.
- Use mktemp to create the temporary files and directory.
- Mount temporary md(4) backed file system on a temporary directory,
instead of /mnt.
Approved by: phk
Nanobsd should make it very simple for people to create (CF-)disk images
for embedded us of FreeBSD.
Currently only works for 256MB disks. More agrressive shaving of the
build image can reduce that much further.
regressions would be to see the program or your kernel crashing.
If you want to give it something to really test out, try a much more
reentrant version of the resolver.
<URL:http://green.homeunix.org/~green/reentrant_resolver.patch>
Any Mozilla-based browser would show you a clear difference.
options since revision 1.2, so removed the XXX comment now.
Fixed bogus test(1) expression that would be evaluated as a null
string test if script is run without arguments, compacted option
lists.
UNI protocols. The actual test suites are not in these directories because
of their size. One needs to install the atmsupport port (the script
will remind you, if it cannot find the port).
The SSCOP test suite includes booth the ETSI and the ITU-T test suite,
the SSCF-UNI test suite is home grown and the UNI test suite is the
P2MP ETSI test suite. Others may follow.
