summaryrefslogtreecommitdiffstats
path: root/usr.bin
Commit message (Collapse)AuthorAgeFilesLines
* - Document gencat(1)dds2003-08-221-2/+2
| | | | | | | - Fix grammar error and rationale for not using the command Approved by: schweikh (mentor) MFC after: 2 weeks
* Big cleanup. Remove unused stuff, make closer to style(9).markm2003-08-221-183/+79
| | | | OK'ed by: peter (long time ago)
* Warns fixes. Mainly unused headers/params/vars removal, but alsomarkm2003-08-227-28/+19
| | | | some malloc cleanup.
* In case of zero span data supress the histogram plot.phk2003-08-181-0/+6
|
* Tidy up usage message.tjr2003-08-172-6/+6
|
* Tidy up synopsis.tjr2003-08-171-3/+1
|
* Tidy up usage message.tjr2003-08-171-2/+2
|
* Add my birthday to calendarmat2003-08-151-0/+1
| | | | Approved by: demon (mentor)
* Add my birthday to the calendar.bland2003-08-151-0/+1
| | | | Approved by: marcus (mentor)
* Removed check of st_rdev changing in the -F support. st_rdev for regulardg2003-08-141-1/+0
| | | | | | | | | | | files is usually the first direct block pointer. Since FreeBSD does automatic block reallocation to reduce filesystem fragmentation, the file being tailed can be relocated to different blocks 'on-the-fly', making the check for st_rdev unreliable. The result of this bug is tail -F pseudo-randomnly thinking the file was rotated when it wasn't, and as a result, spews out the entire file trying to catch up. MFC after: 3 days
* Add Alfred Hitchcock's birthday.murray2003-08-131-0/+1
| | | | Inspired by: google.com
* A small statistics tool for gauging the statistical significancephk2003-08-135-0/+621
| | | | | | | | of data from benchmarks etc. Implements "Student's t" for various confidence levels, defaults to 95%. If your benchmarks are not significant at the 95% confidence level, we don't want to hear about it.
* Add GB18030 and GBK to the list of encodings. Cross-reference thetjr2003-08-101-1/+10
| | | | new manual pages for the Big5, GB18030, GBK, and MSKanji encodings.
* Fix sign-extension bug for 32 and 64-bit values. For 64-bit valuesmarcel2003-08-091-39/+27
| | | | | | | | | | | this involves the sign-extension of the high and low "word". Both of which are 32-bit. The bug is especially harmful on ia64, where 0x9fffffffe0000000 is a common address (base of register stack). This was invariably displayed as 0xffffffffe0000000. The sign-extension is fixed by using {b|l}e{16|32|64}dec() where applicable. Since elfdump(1) is not a bootstrap tool, dependency on these functions is not a problem.
* 1. Add support for printing PIM-related statistics withhsu2003-08-075-1/+136
| | | | | | | | | netstat -s -p pim 2. Print information about the bandwidth meters installed in the kernel with netstat -g Submitted by: Pavlin Radoslavov <pavlin@icir.org>
* Add Jonathan Postel's year of birth.grog2003-08-061-1/+1
|
* send() and recv() are just wrappers, not actual syscalls.des2003-08-051-4/+0
|
* * Use sysctlbyname(3) to print statistics about the MFC andhsu2003-08-051-6/+24
| | | | | | | | | | | | | | multicast VIF tables. This change is needed for consistency with the rest of the netstat/mroute.c implementation, and because in some cases "netstat -g" may fail to report the multicast forwarding information (e.g., if we run a multicast router on PicoBSD). * Remove "DVMRP" from the head comment of file netstat/mroute.c, because the printed multicast-related statistics are not DVMRP-specific anymore. Submitted by: Pavlin Radoslavov <pavlin@icir.org>
* Add recv(2), recvfrom(2), send(2) and sendfrom(2).des2003-08-051-2/+10
|
* Back out [:upper:] and [:lower:] classes sorting, it is not requiredache2003-08-051-6/+3
| | | | by POSIX and gains nothing with current code.
* Clarify upper/lower conversion description more.ache2003-08-051-7/+4
|
* Remove redundant declarations.das2003-08-051-2/+0
|
* Don't overflow the block quota calculations for NFS mounts.das2003-08-051-3/+3
| | | | | PR: 47607 Submitted by: Eric van Gyzen <vangyzen@stat.duke.edu>
* Explain better what happens when [:lower:] <-> [:upper:]ache2003-08-051-0/+19
|
* No functional changes, just code reorganization from prev. commit, itache2003-08-042-12/+18
| | | | | | makes one malloc unneeded, removes two bzero's and makes code more readable. "Bright ideas comes only _after_ commits."
* POSIX require complex processing of 'c-c' ranges: if one of the endpointsache2003-08-042-22/+41
| | | | | | | is octal sequence, range is taken in the byte values order, for non-octal endpoints range is taken in the sorted collation order. Implement it.
* Special fix just forache2003-08-041-0/+7
| | | | | | | | tr -[cC]s '[:upper:]' '[:lower:]' case (or vice versa): chars taken from s2 can be different this time due to lack of complex upper/lower processing, so fill string2 again to not miss some.
* Microoptimization of prev. patch: do strdup() only if (cflag || Cflag)ache2003-08-031-3/+5
|
* 1) Fix -C - it was broken since introduced, wrong array sortedache2003-08-032-23/+19
| | | | 2) Fix last (repeated) char after [:class:], it was \0 in original code
* Remove charcoll() stabilization added in 1.16, it gains nothing but conflictsache2003-08-031-5/+1
| | | | with ranges.
* POSIX requires 'c-c' must conform collate and be in collation orderache2003-08-033-15/+23
|
* This patch address two problems.ache2003-08-033-20/+70
| | | | | | | | | | | | | | | | 1st one is relatively minor: according our own manpage, upper and lower classes must be sorted, but currently not. 2nd one is serious: tr '[:lower:]' '[:upper:]' (and vice versa) currently works only if upper and lower classes have exact the same number of elements. When it is not true, like for many ISO8859-x locales which have bigger amount of lowercase letters, tr may do nasty things. See this page http://www.opengroup.org/onlinepubs/007908799/xcu/tr.html for detailed description of desired tr behaviour in such cases.
* Fix truss on ia64. The syscall arguments are written to the trapmarcel2003-08-021-17/+5
| | | | | | | | frame, occupying scratch registers r16 and up. We don't have to save any scratch registers for syscalls, so we have plenty of room there. Consequently, when we fetch the registers from the process, we automaticly have all the arguments and don't need to read them seperately.
* Add ip6 and icmp6 displays to systat.dwmalone2003-08-017-1/+632
| | | | MFC after: 2 weeks
* Fix jot so that 'jot -r -w %d 1 1 4' never prints 4. Previously, itdas2003-08-011-1/+1
| | | | | | | | | | would print it with probability 1/2**32. It seems that the correct behavior is to print 4 with probability 1/4, but I'd like to avoid breaking POLA until all the range inconsistencies in jot can be fixed in one pass. See PR for details. PR: 54878 Submitted by: David Brinegar <jot.3.brinegar@spamgourmet.com>
* Allow GB18030 localeache2003-07-291-0/+1
|
* Add the -n maxrec option as an alias for -maxrec for compatibility withtjr2003-07-272-10/+18
| | | | | | | System V and consistency with other utilities. Document the new form instead of the old form in the manual page. PR: 54661
* State that in -exec ... ; the semicolon should be quoted if invoked fromschweikh2003-07-251-0/+4
| | | | | | | | a shell. PR: docs/54667 Submitted by: Patrick Alken <pa59@cornell.edu> MFC after: 3 days
* Don't check for the existance of src/crypto/ for building items thatmarkm2003-07-241-1/+1
| | | | | may contain crypto. The days of ITAR paranoia are over, and the simple macro tests that remain are sufficient.
* Make sure that a "make release" (more accurately the bit that makesmarkm2003-07-241-0/+2
| | | | | the crunched binary) get a non-cryptographic telnet. This is overkill in that it covers stuff that is not normally used in a crunched binary.
* Ensure that for the cryptographic instances of *telnet*, the "crypto"markm2003-07-241-0/+1
| | | | distribution is used. This only affects release-building.
* Connect ncplist, ncplogin, and smbutil to the amd64 build.peter2003-07-241-0/+6
|
* Fixed .Nm element, updated HISTORY section, added AUTHORS section.dds2003-07-221-2/+6
| | | | | Reviewed by: schweikh (mentor) MFC after: 2 weeks
* Test 8.16 in sed.test tests the ability of a sed to handle an emptydds2003-07-221-11/+19
| | | | | | | | | | | | | | | | | regular expression as the first argument to a substitute command. If used to test a sed which (erroneously) evaluates this at translation time rather than at execution time, the bugged sed is put into an infinite loop. This mode of failure seems excessive. Such a failing sed is the Free Software Foundation's sed 3.02. The specific test was also not being executed for the BSD sed. Both problems are now fixed. PR: misc/25585 Submitted by: Walter Briscoe <w.briscoe@ponl.com> Approved by: schweikh (mentor) MFC after: 2 weeks
* Make sure the crypto versions of libfetch and fetch(1) appear inru2003-07-221-0/+1
| | | | | | the "crypto" distribution. Approved by: des
* Replace an alloca() call with a slightly more standard malloc()/free()markm2003-07-211-3/+8
| | | | pair.
* Add my birthday to calendarkrion2003-07-211-0/+1
| | | | Approved by: fjoe
* Test correct macro for "without crypto" option(s).markm2003-07-201-1/+1
|
* Add my birthday to the calendar.simon2003-07-201-0/+1
| | | | Approved by: ceri (mentor)
* make sockstat not print wierd addresses on not connected unix domain socketsjmg2003-07-191-1/+5
| | | | | Pointed out by: rwatson Reviewed by: peter
OpenPOWER on IntegriCloud