behavior. Add the bcb regression test which checks for failures due
to a backslash ('\') coinciding with the very last character of the
command buffer. The regression test is cf. this PR (which I did not
know about) and has a different fix for the bug.
PR: bin/22351
Submitted by: Stefan Duerholt <stefan.duerholt@t-online.de>
handle printing of the PASS/FAIL messages. Suffix PASS/FAIL/FATAL with the
string (in $directory) where $directory is ${.CURDIR} from make(1), to
make it easier to use grep(1) and a bit of sed/awk to do statistics of
failure for some utilities over time, etc.
make(1): Does not work like the other tests. Its Makefile is
self-testing.
m4(1): It uses complex voodo to test GNU m4(1) features.
To the new framework. I had worried about passing the binary data that
uudecode(1)'s test passes to diff(1) might give a user something nasty,
but this is unlikely to happen as even with an unmodified old nasty
diff(1) which doesn't recognise many binary files, these binary files
are recognised. Using $DIFF instead of `diff' in the library and making
it possible to override this with `cmp -s' might be nice some day, but
as of this second, there's no immediate need.
to handle the ones which output to stdout and have output in regress.$test.out,
etc. More freeform macros should and will be written, but these are the most
prominent and most straightforward sort of tests we have around, so it makes
sense to try to accomodate them.
expansion of embedded variables in the left-hand-side of an assignment
expression, using the simplest case - hiding recursion using nil-expanded
variables.
uuencode(1), and set a umask, so that the mode in the header is predictable.
If it varies, then the test is right to fail.
Remove the note about this test falsely failing, with that in mind.
and for proper behaviour of some sed functions given a nil pattern space,
as fixed in PR 34813.
The test for G was based on the test in the PR. The nil pattern space test
is slightly different as we need to get *some* output, as the core dump will
also produce no output (old behaviour) and turn up falsely that the utility
is working fine.
This is a set of userland shims in which GEOM can be run through simple
tests.
The simulation of kernel synchronization primitives is very primitive
and consequently some times tests will fail because of races.
Data/ contains a number of files in XML format which describe the
key sectors for a number of disk images
This is a very handy tool for people developing GEOM methods. The
"simdisk" method can be told to read from a "real disk" and afterwards
dump the accessed sectors in XML format for further use.
I hope future method writes will see the benefit of this test
collection and add to it when they write methods for GEOM.
You will need ports/textproc/expat for the XML parser.
Sponsored by: DARPA, NAI Labs.
allows this tool to compile again. Albeit, now to test a new malloc
implementation one has to install the new libc which may have bad
consequences (i.e. if the new malloc implementation were buggy).
Add logic to workaround malloc's current behaviour of returning an
invalid non-NULL pointer for 0 byte allocation requests; this prevents the
tool from coring during the NOPS loop.
Add $FreeBSD$ tags.
The script written and used originally by msmith has been lost.
This version takes the Boemler and Heckenbach lists and produces merged
output. It defaults to ignoring any entries from Heckenbach already
found in Boemler but the -l option causes it to take the entry with the
longest description where an entry appears in both lists.
If this script is replaced, care should be taken to
1) Always use upper-case hexidecimal tokens in device ids.
2) Always keep device lists sorted within vendor lists, which must also
be sorted.
3) Do not try to include input from the previous pci_vendors file, since
bogus ids seem to be removed from both the Boemler and Heckenbach
lists from time to time.
test by default, as setugid() is now part of the base kernel (assuming
(options REGRESSION) has been enabled for the running kernel).
Obtained from: TrustedBSD Project
This test utility attempts to evaluate the current kernel policy
for authorization inter-process activities, currently ptrace(),
kill(, SIGHUP), getpriority(), and setpriority(). The utility creates
pairs of processes, initializes their credential sets to useful
cases, and reports on whether the results are in keeping with hard-coded
safety expectations.
o Currently, this utility relies on the availability of __setugid(),
an uncomitted system call used for managing the P_SUGID bit. Due to
continuing discussion of optional regression testing kernel components
("options REGRESSION") I'll hold off on committing that until the
discussion has reached its natural termination.
o A number of additional testing factors should be taken into account
in the testing, including tests for different classes of signals,
interactions with process session characteristics, I/O signalling,
broadcast activities such as broadcast signalling, mass priority
setting, and to take into group-related aspects of credentials.
Additional operations should also be taken into account, such as ktrace,
debugging attach using procfs, and so on.
o This testing suite is intended to prevent the introduction of bugs
in the upcoming sets of authorization changes associated with the
introduction of process capabilities and mandatory access control.
Obtained from: TrustedBSD Project
are ignored and the remaining is passed on to cp(1). This allows
a build to be run as non-root without forcing any user/group
setting and also prevents setting any file flags.
This may not be the right place for buildtools.
Reads the output of 'diff -r' and splits it into separate
patch files, one per file. The files are named 'patch-XX'
where XX is aa, ab, ac, ... Useful when creating ports.
Web files which does not exists on your host.
E.g.
httpd-error -userhits < /var/log/httpd-error.log
print the number of errors by users, sorted by error hits.
makefile doesn't install them, and they couldn't be used without
lots of undocumented -I's in CFLAGS. tcl.h is still installed in
/usr/include/tcl/. Note that rev.1.24 of tcl_bmake/mkMakefile.sh
broke all the section 3 tcl man pages by putting it there instead
of in /usr/include.
before we make the same mistake with tcl8.0. This _should_ no longer
conflict with a not-yet-imported tcl8.0 port and should allow the
system and ports versions to be updated independently of each other
(and tk) without the sky falling.
third-party device-driver source to the FreeBSD kernel (at versions
2.2 and later). It can list and remove drivers it's added too.
It can (should) be included by device-driver authors in their driver
distributions, but is perhaps a little too specific to warrant a place
in the mainstream distribution.
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
- Be more intelligent about library-like objects that are actually
symlinks. (Suggested by Steve Price)
- Complain about nonexistent libraries referenced by executables (instead
of creating a library called 'not' and putting them there. (oops)
- Fix a few typos.
shared libraries in the system.
It locates libraries using the output of 'ldconfig -r' to find
directories containing libraries, and then performs a recursive
descent of the entire filesystem heirachy looking for dynamically
linked executables and recording the libraries that they use.
After scanning, a report is produced listing used libraries and the
executable(s) that use them, and seperately listing unused libraries.
missing define during the libtcl build. This is needed to get Tclmidi 3.1
to work.
This should close PR#2006
This should also go into 2.2, like the previous commit.
Submitted by: A JOSEPH KOSHY <koshy@india.hp.com>
Subject to be moved elsewhere in case we decided on a more cmplete
upgrade toolset. Right now, put it here so that people can upgrade
their wtmp files if they want.
Note that the tool is not yet fully bullet-prrof. It tries to do its
best however.
it's wrong. It "knows" that ranlib is not used on shared libraries, this
is not a valid assumption since it exports this definition to the world
via tclConfig.sh. :-( Hence, things like expect (to be updated) fall over
because they were using ":" instead of "ranlib" on their static libraries.
TCL_SHLIB_SUFFIX, since some tools use it for generating the name of
shared objects for dlopen(), which do not have version numbers. This
setting is back to "as distributed".
It seems that some tools (eg: expect-5.21) use TCL_LIB_SPEC to generate
their shared library suffix. This should be .so.1.0, not .so as ld can't
use it.
Revert part of the previous change here, it did too much. libtcl75.so.1.1
was bumped, but the rules to generate library names for _other_ packages
were not supposed to be. Sigh.
of tcl with new functions in the library), but the ports-compatable
link name wasn't bumped as it should have been.
Minor cleanups while here (including preserving the $Id: line)
diagnostic program for debugging the interface MIB and an example of
how to use same. Someday, netstat should be updated to print this
information in a prettier form.
- don't install nroff tcl.macros in /usr/include.... :-]
- set $MAN3 and $MANn in one go rather than a string of MAN3+= ...
- cosmetic tweaks to make it more readable
- no longer copy tcl.macros to the obj dir, install it from source dir
Use the MANFILTER rather than generate rules for each page
Use .PATH to source the man pages rather than copy them for build
Install a tclConfig.sh with build params, may need more tweeks yet.
Install libtcl.so.75.0 *and* libtcl75.so.1.0 for ports compat.
This directory is for tools.
A tool is something which is sometimes useful, and doesn't fit any of the
other categories.
Please make a subdir per program, and add a brief description to this file.
This directory is for test programs.
A test program is one that will excercise a particular bit of the system
and try to break it and/or measuring performance on it.
Please make a subdir per program, and add a brief description to this file.
This directory is for regression test programs.
A regression test program is one that will excercise a particular bit of the
system to check that we have not reintroduced an old bug.
Please make a subdir per program, and add a brief description to this file.
This directory is for diagnostic programs.
A diagnostic program is one that will inform you that something is wrong
somewhere, for instance by traversing a kernel-structure and verifying
the integrity.
Please make a subdir per program, and add a brief description to this file.
This directory tree contains tools used for the maintenance of FreeBSD.
There are no Makefile structure, but possibly Makefiles in some of the
subdirs.
Nothing show be installed from here and into the running system.
This directory should contain only subdirs and this file.
