summaryrefslogtreecommitdiffstats
path: root/tools
Commit message (Collapse)AuthorAgeFilesLines
* exit if "make distribition" failsjulian2009-11-251-1/+1
| | | | | Submitted by: patrick tracanelli MFC after: 1 week
* Make this test case little bit more interesting.jkim2009-11-231-500/+500
|
* sh: Ensure the same command input file is on top after executing a builtin.jilles2009-11-221-0/+27
| | | | | | | | | | | | | This avoids weirdness when 'fc -e vi' or the like is done and there is a syntax error in the file. Formerly an interactive shell tried to execute stuff after the syntax error and exited. This should also avoid similar issues with 'command eval' and 'command .' when 'command' is implemented properly as in NetBSD sh. Special builtins did not have this problem since errors in them cause the shell to exit or to reset various state such as the current command input file.
* trap: do not consider a bad signal name a fatal error.jilles2009-11-211-0/+12
| | | | | POSIX explicitly prescribes this. Continue processing any other signals and return status 1.
* Add a test for r199631.stefanf2009-11-211-0/+15
|
* Add a few very basic tests for cd -{L,P} and pwd -{L,P}.stefanf2009-11-211-12/+22
|
* Correct copyright date in the BPF regression test.jkim2009-11-201-1/+1
|
* Adjust BPF JIT compiler regression tests to catch up with r199603.jkim2009-11-207-20/+35
|
* Add nanobsd example for the PC Engines ALIX board (serial console).mr2009-11-1918-0/+1312
|
* Add a test case for very long BPF program.jkim2009-11-192-1/+1031
|
* Collapse devinfo_state_t with device_state_t in order to avoid aattilio2009-11-151-6/+6
| | | | | | | structure replication and improve manteneability. Reviewed by: jhb, imp Tested by: Riccardo Torrini <riccardo at torrini dot org>
* sh: Allow a newline before "in" in a for command, as required by POSIX.jilles2009-11-141-0/+29
|
* Convert {small prefix}BSD to TERM=xterm as well.ed2009-11-132-23/+23
| | | | | | Clean up the ttys files shipped with PicoBSD, NanoBSD and TinyBSD. While there, it seems one of them still had references to sio(4). Make it in sync with what we do in the base system.
* Switch the default terminal emulation style to xterm for most platforms.ed2009-11-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Right now syscons(4) uses a cons25-style terminal emulator. The disadvantages of that are: - Little compatibility with embedded devices with serial interfaces. - Bad bandwidth efficiency, mainly because of the lack of scrolling regions. - A very hard transition path to support for modern character sets like UTF-8. Our terminal emulation library, libteken, has been supporting xterm-style terminal emulation for months, so flip the switch and make everyone use an xterm-style console driver. I still have to enable this on i386. Right now pc98 and i386 share the same /etc/ttys file. I'm not going to switch pc98, because it uses its own Kanji-capable cons25 emulator. IMPORTANT: What to do if things go wrong (i.e. graphical artifacts): - Run the application inside script(1), try to reduce the problem and send me the log file. - In the mean time, you can run `vidcontrol -T cons25' and `export TERM=cons25' so you can run applications the same way you did before. You can also build your kernel with `options TEKEN_CONS25' to make all virtual terminals use the cons25 emulator by default. Discussed on: current@
* Add test-pidfile.c and increase warning level.des2009-11-121-2/+2
|
* Test cases for pidfile(3) - including two designed to catch issues arisingdes2009-11-121-0/+280
| | | | from the incorrect use of fcntl(2) instead of flock(2).
* Fix warnings and remove one unnecessary use of vfork(). The other coulddes2009-11-121-9/+3
| | | | also be removed with a little more work.
* Fix warningsdes2009-11-123-7/+9
|
* Check fork() return valuedes2009-11-101-2/+5
|
* sh: Exempt $@ and $* from set -ujilles2009-10-241-0/+12
| | | | | | | | This seems more useful and will likely be in the next POSIX standard. Also document more precisely in the man page what set -u does (note that $@, $* and $! are the only special parameters that can ever be unset, all the others are always set, although they may be empty).
* Add some tests for ${var?} and set -u.jilles2009-10-242-0/+51
|
* wordexp(3): fix some bugs with signals and long outputsjilles2009-10-231-0/+42
| | | | | | | | | | | | * retry various system calls on EINTR * retry the rest after a short read (common if there is more than about 1K of output) * block SIGCHLD like system(3) does (note that this does not and cannot work fully in threaded programs, they will need to be careful with wait functions) PR: 90580 MFC after: 1 month
* Fix a case where rename actually succeeds, which is also expected behaviourpjd2009-10-201-2/+3
| | | | | | according to POSIX. This fixes ZFS on Solaris testing. Submitted by: Milan Cermak <Milan.Cermak@Sun.COM>
* Update copyright.des2009-10-191-1/+1
|
* Remove redundant $FreeBSD$.des2009-10-191-2/+0
|
* Support the specification of a range of destination ports e.g.luigi2009-10-151-51/+88
| | | | | | | | | | | | | | | | | | | | | | | | netsend 127.0.0.1 6666-7777 [payloadsize] [packet_rate] [duration] This is useful to test the behaviour of systems that do some kind of flow classifications and so exhibit different behaviour depending on the number of flows that hit them. I plan to add a similar extension to sweep on a range of IP addresses, so we can issue a single command to flood (obviously, for testing purposes!) a number of different destinations. When there is only one destination, we do a preliminary connect() of the socket so we can use send() instead of sendto(). When we have multiple ports, the socket is not connect()'ed and we do a sendto() instead. There is a performance hit in this case, as the throughput on the loopback interface (with a firewall rule that blocks the transmission) goes down from 900kpps to 490kpps on my test machine. If the number of different destinations is limited, one option to explore is to have multiple connect()ed sockets. MFC after: 1 month
* A small change to avoid calling gettimeofday() too oftenluigi2009-10-151-4/+19
| | | | | | | | | | | | | | | | | (hardwired to once every 20us at most). I found out that on many machines round here, i could only get 300-400kpps with netsend even on loopback and a 'deny' rule in the firewall, while reducing the number of calls to gettimeofday() brings the value to 900kpps and more. This code is just a quick fix for the problem. Of course it could be done better, with proper getopt() parsing and the like, but since this applies to the entire program i'll postpone that to when i have more time. Reviewed by: rwatson MFC after: 1 month
* Tweaks for sigqueue tests:kib2009-10-112-12/+27
| | | | | | | | | | | - slightly adjust code for style, sort headers. - in sigqtest2, print received signals, to make it easy to see why test failed. - in sigqtest2, job_control_test(), cover a race by adding sleep after child stopped itself to allow for SIGCHLD due to stop and exit to not be coalesced. MFC after: 2 weeks
* Fix build on amd64.delphij2009-10-071-4/+5
| | | | | PR: misc/139409 Submitted by: gk
* sh: Send the "xyz: not found" message to redirected fd 2.jilles2009-10-061-0/+29
| | | | | | | | | | This also fixes that trying to execute a non-regular file with a command name without '/' returns 127 instead of 126. The fix is rather simplistic: treat CMDUNKNOWN as if the command were found as an external program. The resulting fork is a bit wasteful but executing unknown commands should not be very frequent. PR: bin/137659
* A few regression tests for SOCK_SEQPACKET UNIX domain sockets.rwatson2009-10-054-0/+593
| | | | Sponsored by: Google
* Regression tests for r197752 (handling of empty/NULL buffers).das2009-10-041-1/+20
|
* Replace the name of the sysctl to security.bsd.map_at_zero and to bebz2009-10-021-13/+13
| | | | | consistent updated the name of the variable as well, after the change in r197711.
* sh: Disallow mismatched quotes in backticks (`...`).jilles2009-10-011-0/+7
| | | | | | | | | Due to the amount of code removed by this, it seems that allowing unmatched quotes was a deliberate imitation of System V sh and real ksh. Most other shells do not allow unmatched quotes (e.g. bash, zsh, pdksh, NetBSD /bin/sh, dash). PR: bin/137657
* Add a simple C program to check mmap calls to various different addresses.bz2009-09-272-0/+102
| | | | | | | | | | The most important test is the mapping fixed at address 0 depending on the new sysctl. Things will be updated and possibly converted to m4/.t style once the details about the kernel patch will be shaken out. Submitted by: simon (initial version)
* - When we run our trap cleanup handler, echo that we are running thissimon2009-09-271-1/+4
| | | | | | | | | | handler to make it more clear why we are 'suddenly' running df, umount, and mdconfig. - Remove trap handler again after we have unconfigured the memory device etc. Before we could end up running the trap handler if a later stage failed, which was a bit confusing and not really useful. MFC after: 2 weeks
* Update the includes to two more levels of subdirs.rpaulo2009-09-241-2/+2
| | | | MFC after: 1 week
* Add cross-filesystem regression tests for ACLs.trasz2009-09-233-1/+289
|
* Add ACL fuzzer. It's not used by the regression tests right now,trasz2009-09-231-0/+225
| | | | but I'd prefert to have it here, so it won't get lost.
* - Remove a bogus test: setsockopt() doesn't return a length, getsockopt()jhb2009-09-231-4/+1
| | | | | does. - Use %z to printf a size_t to fix compile on 64-bit platforms.
* IEEE Std 1003.1, 2004 Edition states:dds2009-09-203-0/+6
| | | | | | | | | | | | | "The escape sequence '\n' shall match a <newline> embedded in the pattern space." It is unclear whether this also applies to a \n embedded in a character class. Disable the existing handling of \n in a character class following Mac OS X, GNU sed version 4.1.5 with --posix, and SunOS 5.10 /usr/bin/sed. Pointed by: Marius Strobl Obtained from: Mac OS X
* Follow POSIX (IEEE Std 1003.1, 2004 Edition) in the implementationdds2009-09-202-0/+5
| | | | | | | | | | | of the y (translate) command. "If a backslash character is immediately followed by a backslash character in string1 or string2, the two backslash characters shall be counted as a single literal backslash character" Pointed by: Marius Strobl Obtained from: Mac OS X
* Add correct test results.dds2009-09-203-0/+42
|
* Describe how other systems treat this case.dds2009-09-201-1/+5
|
* Allow [ to be used as a delimiter.dds2009-09-201-0/+9
| | | | | Pointed by: Marius Strobl Obtained from: Apple
* The transition to Subversion allows us to rename files withoutdds2009-09-20124-9/+7
| | | | | | repo-copy hacks. Remove the test-number prefix from the name of the output files, so that new test cases can be easily added.
* Add regression tests for NFSv4 ACL granular permission enforcement.trasz2009-09-079-2/+738
|
* Add regression tests for NFSv4 ACLs and update POSIX.1e tests to the changedtrasz2009-09-074-26/+1013
| | | | error messages.
* Adapt to the fact that ls(1) correctly prints '+' for symlinks with ACLs now.trasz2009-09-011-2/+1
|
* Add regression test for ACLs on device files - mostly to maketrasz2009-08-311-0/+16
| | | | sure we don't crash on attempt to set ACL on them.
OpenPOWER on IntegriCloud