summaryrefslogtreecommitdiffstats
path: root/tools
Commit message (Collapse)AuthorAgeFilesLines
* Make it works with POSIX sort (POS arg)ache2002-09-241-1/+1
| | | | All old sorts understand -k too.
* Add ability to make threads that run on > 1 cpujulian2002-09-232-41/+191
| | | | | | this DOES NOT WORK YET. (well it kind-of-does but it's unsafe) Submitted by: davidxu
* Update the KSE test utility to the new KSE API.mini2002-09-193-319/+482
|
* Initiate deorbit burn for the i386-only a.out related support. Moves arepeter2002-09-171-6/+1
| | | | | | | | | | | | | | | under way to move the remnants of the a.out toolchain to ports. As the comment in src/Makefile said, this stuff is deprecated and one should not expect this to remain beyond 4.0-REL. It has already lasted WAY beyond that. Notable exceptions: gcc - I have not touched the a.out generation stuff there. ldd/ldconfig - still have some code to interface with a.out rtld. old as/ld/etc - I have not removed these yet, pending their move to ports. some includes - necessary for ldd/ldconfig for now. Tested on: i386 (extensively), alpha
* Pick up modules from the compile directory instead of /boot/kernel.phk2002-09-161-2/+13
| | | | | | Allow the script to operate on any convenient kernel. Submitted by: "Matthew Emmerton" <matt@gsicomp.on.ca>
* Some change in src/share/mk seems to have made it possible to removephk2002-09-1514-14/+0
| | | | 50% of the active ingredients in these Makefiles.
* Overhaul the kernel-simulation bits here to use pthreads instead.phk2002-09-1319-160/+144
| | | | | | | If somebody wanted to, this could for the beginning of a "libkernel" which could be used to run kernel code in userland. Sponsored by: DARPA & NAI Labs.
* Remove magicspace from reference data.phk2002-09-068-282/+0
| | | | Sponsored by: DARPA & NAI Labs.
* expat2 changed the name of their include file to expat.hphk2002-09-062-2/+2
| | | | Sponsored by: DARPA & NAI Labs.
* Fix an indentation typo.phk2002-09-061-1/+1
| | | | Sponsored by: DARPA & NAI Labs.
* Add a zeroed out sector one for the GPT hack and test T003.phk2002-09-061-0/+21
| | | | Sponsored by: DARPA & NAI Labs.
* Add regression tests for sysvipc.alfred2002-08-1510-0/+1079
| | | | | Submitted by: Hiten Pandya <hiten@uk.FreeBSD.org> Obtained from: NetBSD
* Fix typos; each file has at least one s/seperat/separat/schweikh2002-08-111-1/+1
| | | | | | | | | | (I skipped those in contrib/, gnu/ and crypto/) While I was at it, fixed a lot more found by ispell that I could identify with certainty to be errors. All of these were in comments or text, not in actual code. Suggested by: bde MFC after: 3 days
* As of revision 1.38 of make/parse.c, our make(1) will warn too. Note thatjmallett2002-07-282-4/+6
| | | | | this isn't just for the sake of testing behaviour, and that things really do break if this regression occurs.
* Update to current reality: change COMPILEDIR and work on "R"ead-only-dataphk2002-07-191-2/+2
| | | | symbols as well.
* Update another mention of <CR><CR> I missed the first time around (rev 1.2)tjr2002-07-041-1/+1
|
* Note that two carriage returns aren't required after entering thetjr2002-07-031-2/+3
| | | | | | initial setup anymore (since process.c rev. 1.25). Add $FreeBSD$. MFC after: 2 weeks
* KSE test programjulian2002-06-293-0/+383
|
* The wrong y/// output got spammed into this file; from green@ indirectly.jmallett2002-06-271-1/+1
|
* Correct the psl regression test for sed(1)'s now-fixed newlinegreen2002-06-273-0/+8
| | | | | | | | | | 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>
* Erk, I forgot that regress.in has an ending newline, so change the test forjmallett2002-06-262-5/+2
| | | | transliterate to use echo -n to supress newline and a simple string.
* Reduce internal code duplication, add REGRESSION_PASSFAIL([testname]) tojmallett2002-06-251-19/+14
| | | | | | | 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.
* Add a regression test for transliterate which happens to match charactersjmallett2002-06-252-0/+5
| | | | | | | at an EOL/EOF, and therefore should catch the broken behaviour fixed by Tim J. Robbins in sed(1) recently. Suggested by: obrien
* I explicitly meant to not move any of this over to the new m4(1) framework,jmallett2002-06-242-2/+11
| | | | even slightly. Grrr CVS.
* Move all remaining tests except for:jmallett2002-06-2410-73/+23
| | | | | | | | | | | | | | 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.
* Add two new mostly freeform types of regression tests, and a macro for dyingjmallett2002-06-241-0/+30
| | | | ungracefully.
* Comments to describe what these macros do, so that someone other than mejmallett2002-06-241-0/+13
| | | | might be able to figure out how to write some of these tests (hint hint).
* Convert straightforward regression tests to use regress.m4.jmallett2002-06-246-93/+19
| | | | Goodbye, duplicated code, you will certainly not be missed.
* Add a simple (to be expanded) library of functions for the regression tests,jmallett2002-06-241-0/+23
| | | | | | | 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.
* Grrr, make the test for embedded variables in the left-hand-side actually dojmallett2002-06-202-4/+4
| | | | the right thing in every case. Yuck.
* Add a test for what was fixed in revision 1.27 and 1.28 of make(1)'s var.c,jmallett2002-06-192-0/+34
| | | | | | expansion of embedded variables in the left-hand-side of an assignment expression, using the simplest case - hiding recursion using nil-expanded variables.
* Catch up with kernel.phk2002-06-096-12/+12
|
* Describe ia64_unaligned and geom directories. I hope I got these right.jmallett2002-06-071-0/+2
|
* Add the m4(1) regression test.jmallett2002-06-071-1/+1
|
* Add a regression test for m4(1).jmallett2002-06-075-0/+50
| | | | This checks the behaviour of changecom() in both GNU and BSD modes of our m4.
* Fixed typos.ru2002-06-061-3/+5
|
* Tidy up.ru2002-06-061-5/+3
|
* Fix typo in the BSD copyright: s/withough/without/schweikh2002-06-021-1/+1
| | | | | Spotted and suggested by: des MFC after: 3 weeks
* Update for current /usr/src.ru2002-05-281-1/+1
|
* Mutex statistics script.des2002-05-261-0/+130
|
* Update to match kernel side.phk2002-05-2116-906/+1152
| | | | Sponsored by: DARPA & NAI Labs.
* Catch up with recent events.phk2002-05-194-5/+7
| | | | Sponsored by: DARPA & NAI Labs.
* Regenerate with new output grouping in uuencode -m.jmallett2002-05-171-86/+72
|
* file system > filesystemtrhodes2002-05-161-2/+2
|
* Add a regression test for bin/5297, regarding sysv substitution with a niljmallett2002-05-054-0/+20
| | | | left-hand-side.
* Add a test for the -R option.jmallett2002-05-032-1/+8
|
* Regenerate -I output since an argument bogon in the -I code was fixed, amongjmallett2002-05-031-1/+1
| | | | other things.
* Modernizephk2002-05-021-52/+71
|
* Un-rot the VOP_ table generator.phk2002-05-021-6/+27
|
* Redirect stdin from the input file, rather than passing the input file tojmallett2002-04-271-6/+4
| | | | | | | | 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.
OpenPOWER on IntegriCloud