summaryrefslogtreecommitdiffstats
path: root/bin
Commit message (Collapse)AuthorAgeFilesLines
* o Add a missed "." .maxim2004-12-021-1/+1
| | | | | Reviewed by: ru MFC after: 3 weeks
* o Terminate an endless loop sh -T goes into in dowait() around waitproc().maxim2004-12-021-1/+2
| | | | | | | | | | | | XXX from Tor: "The shell can also go into a similar loop if the child was killed by signal 127, since the shell would believe the child to have only stopped (WIFSTOPPED() macro returns nonzero value). Disallowing signals 127 and 128 will fix that problem." See kern/19402 for details. PR: bin/66242 Submitted by: tegge Analysis and testcase by: demon MFC after: 3 weeks
* Point at the mac(4) man page when describing the -Z option.rwatson2004-11-291-5/+4
| | | | | | Remove reference to /dev/lomac, which is no longer used by mac_lomac(4). MFC after: 3 days
* Do not emit a spurious warning when "directory" argumentru2004-11-201-1/+3
| | | | to "rmdir -p" is absolute, with one or more leading slash.
* Fixed "rmdir -p" that got broken by rev. 1.15.ru2004-11-201-6/+5
| | | | (This also fixes "rmdir -v /nonexistent".)
* Use statfs instead of getmntinfo(). This will make the procfs checkscsjp2004-11-191-9/+6
| | | | | | | play nicer in prisons. It also simplifies things. Reviewed by: rwatson Bumped into by: Jilles Tjoelker
* Currently if the user specifies -e and procfs is not mounted on /proc,csjp2004-11-141-0/+25
| | | | | | | | | | | printing of the process environment will fail silently. -define a function which will check to see if procfs is mounted on /proc -Implement this test if the user specified -e -If procfs is not mounted on /proc and -e was specified, print a warning. informing the user that procfs(5) is required. Reviewed by: wes, rwatson
* Removed bitrot.ru2004-11-132-14/+2
|
* Fix off-by-one errors and potential buffer overrunsyar2004-11-131-18/+30
| | | | | | | | | | WRT handling file and link names that reach the allowed maximum for old tar and ustar archive formats. PR: bin/40466 Submitted by: Cyrille Lefevre <email in the PR> (portions) Reviewed by: freebsd-arch (silence) MFC after: 1 month
* UNIX conformance: If -r -f on non-existent directory, don't emit error.jkh2004-11-131-1/+4
|
* Back out recent TTYDEF_LFLAG_ECHO invention.ache2004-11-061-1/+1
| | | | | This change is NOP, because TTYDEF_LFLAG = TTYDEF_LFLAG_ECHO now, but to minimize diffs with other BSDs.
* Introduce the PRECIOUSPROG knob in bsd.prog.mk, similarru2004-11-031-1/+1
| | | | | | | | to PRECIOUSLIB from bsd.lib.mk. The side effect of this is making installing the world under jail(8) possible by using another knob, NOFSCHG. Reviewed by: oliver
* stty sane should set the echo bits.phk2004-11-021-1/+1
| | | | | | PR: 73423 Submitted by: Michiel Boland <michiel@boland.org> Overlooked by: phk
* When listing the special $ variables, ($!, $#, etc) list them as $!alfred2004-11-011-12/+16
| | | | | | | | instead of just !, this allows one to more easily locate/understand the section of the manpage in question. Additional wording correction by: keramida Reviewed by: keramida
* Correct a typo and make the documentation more mdoc(7) complaint.delphij2004-11-011-3/+3
| | | | | Pointed out by: dd Approved by: murray (mentor)
* Add -I, an option that asks for confirmation once if recursivelydelphij2004-10-282-5/+70
| | | | | | | | | | | | | | | | | | | | | removing directories or if more than 3 files are listed in the command line. This feature is intended to provide a safe net but not being too annoying like having "rm -i" for every deleting operations, and is generally good for both newbies and power users, preventing them from being so easily run into ``rm -rf /'', ``rm -rf *'' and so forth. Originally implemented by Matthew Dillon for DragonFly, plus some improvements done by various DragonFly contributors. Approved by: murray (mentor; the original dillon's version) Discussed with: des Obtained from: DragonFly's bin/rm/ rm.c rev. 1.4 - 1.8 rm.1 rev. 1.3 - 1.4 MFC After: 1 month
* The previous commit added code to rm(1) to warn about and remove anydes2004-10-041-1/+2
| | | | | | | | | | | | | | | occurrences of "/" in the argument list. This corresponds to Enhancement Request Number 5 in the Austin Group TC2 Aardvark's XCU Defects Report (<URL:http://www.opengroup.org/austin/aardvark/finaltext/xcubug.txt>). Further discussion is available in the Austin Group mailing list archives (<URL:http://www.opengroup.org/austin/mailarchives/>, "Defect in XCU rm") and for Austin Group members, in the Austin Group Interpretations archive (<URL:http://www.opengroup.org/austin/interps/>, AI-019) This commit makes that check conditional on !POSIXLY_CORRECT, since it is not strictly correct according to the current version of the standard (but is expected to be correct according to the next version, and has already been adopted by Solaris).
* Markup fixes.des2004-10-041-4/+4
| | | | Pointed out by: ru
* Find out how flame-proof my underwear really is.des2004-10-042-1/+25
|
* Whitespace cleanup.des2004-10-041-4/+4
|
* chflags compiles with WARNS?=6.stefanf2004-10-031-0/+1
|
* Garbage collect a variable whose value was never read.stefanf2004-10-031-5/+4
|
* Attempting to unset an undefined variable or function should not bedes2004-09-272-2/+2
| | | | | | | | considered an error according to the Open Group Base Specification. PR: standards/45738 Submitted by: Matthias Andree <matthias.andree@web.de> MFC after: 3 days
* Don't read the byte at *argv[strlen(*argv) + 1].das2004-09-241-1/+1
| | | | PR: 71743
* Group equivalent flags together and delete the `aliases' section.keramida2004-09-211-13/+8
| | | | | PR: docs/70856 Submitted by: Rostislav Krasny <rosti_bsd@yahoo.com>
* Add a "fillchar" command line argument to dd(1) that permits the userrwatson2004-08-155-2/+32
| | | | | | | to specify an alternative padding character when using a conversion mode, or when using noerror with sync and an input error occurs. This facilities reading old and error-prone media by allowing the user to more effectively mark error blocks in the output stream.
* Change the behaviour of `-v' so that, e.g., stepping a month backyar2004-08-092-1/+30
| | | | | | | | | | | | | | | | | on March 31 won't take you to March 2 or 3 (now the result will be the last day of February.) In general, now stepping by months from the last days of the current month A will take you to the very last day of the target month B if B is shorter than A. The previous version would just step to March 31 and rely on mktime(3) to correct the date. Despite its simplicity, such way was counter-intuitive to users and caused pain to shell script writers. Noticed by: Igor Timkin <ivt at gamma dot ru> Approved by: brian MFC after: 2 weeks
* Join the 21st century: Cryptography is no longer an optional componentcperciva2004-08-061-1/+0
| | | | | | | | | | of releases. The -DNOCRYPT build option still exists for anyone who really wants to build non-cryptographic binaries, but the "crypto" release distribution is now part of "base", and anyone installing from a release will get cryptographic binaries. Approved by: re (scottl), markm Discussed on: freebsd-current, in late April 2004
* Now that we have gcc 3.4, we can flip ia64 to using a dynamically linkedgordon2004-08-061-1/+1
| | | | | | /bin and /sbin. Reviewed by: marcel (via pluto1)
* Allow for capital letters as size suffixes.pjd2004-07-311-8/+20
| | | | | Inspired by: le Approved by: green (maintainer)
* Currently if a mount point is not accessible by the calling user,csjp2004-07-202-6/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | invalid information will be printed if the -t flag is specified. $ df -t ufs Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s1a 495726 139944 316124 31% / /dev/ad0s1e 253678 6438 226946 3% /tmp /dev/ad0s1f 56206340 13594248 38115586 26% /usr /dev/ad0s1d 694126 19812 618784 3% /var /dev/ad0s1d 694126 19812 618784 3% /var $ Note that the mount point which is not accessible shows up as the previous file system that was printed. The reason for this is that df -t will call statfs(2) on the pathname supplied by getfsstat(2). This is done to refresh the file system statistics in the event that a previous file system had a long delay in providing its stats. This change affects the df utility in the following ways: o Teach df has to deal with statfs(2) failing. If statfs(2) fails, fall back on the possibly stale stats provided by the initial call to getfsstat(2). o Print a warning that the fs stats could possibly be stale o Modify the man page and document this new behavior as a bug. Approved by: bmilekic (mentor) PR: 68165
* Use warn() instead of perror().tjr2004-07-202-4/+4
|
* Give the most awesome example of how to parse the output of datealfred2004-07-171-0/+8
| | | | | | back into epoch time. Everytime I'm asked to do this by someone I have to spend about ten minutes recreating the same command line. So record it under examples.
* Remove BUGS section that talked about missing multibyte character support.tjr2004-07-121-5/+1
| | | | We have support now that the regular expression routines do.
* KANJI and DSPMBYTE are now "on" by default in the tcsh 6.13.00 distribution.mp2004-07-112-24/+34
|
* Document missing multibyte character handling in utilities specifiedtjr2004-07-034-4/+20
| | | | by POSIX.
* Clarify: test compares strings by binary value, not "ASCII value".tjr2004-07-031-3/+3
|
* Deal with double whitespace.ru2004-07-039-21/+23
|
* Mechanically kill hard sentence breaks.ru2004-07-0218-156/+302
|
* Removed trailing whitespace.ru2004-07-021-1/+1
|
* Change the "rtprio" format so it prints an informative string forgad2004-06-271-0/+3
| | | | | | the PRI_ITHD case (instead of just printing the digit '1'). Submitted by: Cyrille Lefevre
* Improve checking for `ps -t <dev>', and give better error messages whengad2004-06-271-8/+16
| | | | | an invalid <dev> is specified. Aside: It turns out that the S_ISCHR() check is true for almost every device that we have (not just tty's).
* Don't continue if the '-C' option (a-la GNUtar; commited in options.cobrien2004-06-251-1/+3
| | | | | | | | rev 1.18, but not documented in the man page) caused a failed chdir. Otherwise, one can easily overwrite files. Submitted by: Robert Nagy <robert@openbsd.org> Obtained from: OpenBSD
* Fix a bug I introduced by some last-minute changes in -r 1.102. I endedgad2004-06-241-1/+1
| | | | | | up checking the wrong variable for NULL. Submitted by: bde
* Rework the logic for `-t <tty>', such that it accepts "ttyp0" and "console",gad2004-06-241-15/+43
| | | | in addition to "/dev/ttyp0" or "p0" and "/dev/console" or "co".
* Change "struct varent" to use the standard queue(8) macros, instead ofgad2004-06-235-32/+25
| | | | | | using it's own version of the same basic algorithm. Submitted by: part by Cyrille Lefevre, part of it done by me
* Add a check for defunct processes in saveuser(), so the output for "args"gad2004-06-231-10/+18
| | | | | | | (aka "command") will display "<defunct>", as does the output from "comm" for those processes. Also do better checking for malloc() failures. Submitted by: Cyrille Lefevre
* Avoid padding the value of "ucomm" when it is the last column in the line.gad2004-06-231-1/+4
| | | | Submitted by: Cyrille Lefevre
* Make sure the value of "upr" (scheduling priority on return from system call)gad2004-06-233-3/+15
| | | | | | is scaled in the same way that "pri" (scheduling priority) is scaled. Submitted by: Cyrille Lefevre
* Include the `-c' option in the usage() message.gad2004-06-231-1/+1
| | | | Submitted by: Cyrille Lefevre
OpenPOWER on IntegriCloud