summaryrefslogtreecommitdiffstats
path: root/bin
Commit message (Collapse)AuthorAgeFilesLines
* use 'const' for the parameters of the two static functions unalias() and ↵rse2008-06-071-4/+4
| | | | hashalias()
* remove an unnecessary includerse2008-06-071-1/+0
|
* Unbreak last commit to ln for amd64.keramida2008-06-071-1/+1
| | | | | | | | Cast string precision to `int'. amd64 systems warn about the field precision being `long int' if we don't, and pathnames are normally short enough to fit in an `int'. Noticed by: pav
* Add a -w warning flag to ln(1). When the -w option is enabled,keramida2008-06-062-7/+47
| | | | | | | | | | | ln(1) checks to see if the source of a symlink, i.e. the file it should point to actually exists. The default is the old ln behavior, that does not check, to avoid surprising people who may be using ln(1) in scripts or other non-interactive places. PR: bin/7265 Submitted by: Joel Ray Holveck, detlev!joelh at mail.camalott.com MFC after: 2 weeks
* Fix checking if a variable name is LINENO. As STPUTC changes the pointer if itstefanf2008-05-281-2/+5
| | | | | | needs to enlarge the buffer, we must not keep a pointer to the beginning. PR: ports/123879
* Expand $LINENO to the current line number. This is required by SUSv3's "Userstefanf2008-05-153-7/+35
| | | | | | | | | Portability Utilities" option. Often configure scripts generated by the autotools test if $LINENO works and refuse to use /bin/sh if not. Package test run by: pav
* Sigh, when reapplying the patch to HEAD, I somehow forgot to commit this file.stefanf2008-04-281-6/+3
| | | | Reported by: Jaakko Heinonen
* - Fix bugs where the value of arithmetic expansion$((...)) was trucatedstefanf2008-04-273-14/+29
| | | | | | | | | | | to type int. - Change the type used for arithmetic expansion to intmax_t (ie. 64 bit on all currently supported FreeBSD architectures). SUSv3 requires at least type long but allows for larger types. Other shells (eg. bash, zsh, NetBSD's sh) do that too. PR: 122659 Submitted by: Jaakko Heinonen (minor modifications by me)
* Turn a tab into a space. This fixes a misalignment for ls -l.imp2008-04-051-2/+2
| | | | Tabs Noticed by: Antoine Brodin
* - Add -D to usage().ru2008-04-042-4/+5
| | | | | - Bump document date for the addition of the -D option. - Reformat a sentence to look like a real sentence.
* Add -D option to specify exact format of date and time output with ls -l.grog2008-04-044-16/+46
|
* Reset the internal state used for the 'getopts' built-in when 'shift' or 'set'stefanf2008-03-221-2/+2
| | | | | | | | are used to modify the arguments. Not doing so caused random memory reads or null pointer dereferences when 'getopts' was called again later (SUSv3 says getopts produces unspecified results in this case). PR: 48318
* uuidgen has been repo-copied from usr.bin/ to bin/ to match its "new"obrien2008-03-132-3/+2
| | | | (2007/04/09) installation location.
* - P_SA has been removed.jeff2008-03-121-1/+0
|
* Add an '-a' option which is identical to specifying '-RpP' forjhb2008-03-103-5/+15
| | | | | | compatibility with other implementations. MFC after: 1 month
* Enhance realpath(1) in a number of ways:rwatson2008-03-092-7/+34
| | | | | | | | | | | | | - Allow realpath to accept multiple paths on the command line. - Add -q to suppress warnings if some paths can't be processed, and use getopt(3) to process flags. - Print the path being requested rather than a possibly partially processed path when a failure occurs so that you can tell which of several passed paths did fail. MFC after: 1 week PR: 112920 Submitted by: Ighighi <ighighi@gmail.com>
* Make chflags(1) more chmod(1)-like (and more feature complete):rwatson2008-03-092-17/+43
| | | | | | | | | | | | | | - Add -v to print file names as they are processed; -vv prints the flags change as well. - Add -f to ignore failures with the same semantics as chflags(1), neither printing an error nor affecting the return code. - Don't try to set the flags if they won't change. I made minor cosmetic tweaks to the code in the patch. MFC after: 1 week PR: 112827 Submitted by: Ighighi <ighighi at gmail.com>
* Split updatepwd() into two smaller functions. The first one, findpwd(),stefanf2008-02-241-38/+45
| | | | | | | | | | computes the new path and the second one, updatepwd(), updates the variables PWD, OLDPWD and the path used for the pwd builtin according to the new directory. For a logical directory change, chdir() is now called between those two functions, no longer causing wrong values to be stored in PWD etc. if it fails. PR: 64990, 101316, 120571
* Fix "warning: comparison is always false due to limited range of data type"marcel2008-02-181-4/+1
| | | | | | | on platforms with unsigned chars. The comparison in question is there to determine whether chars are unsigned or not and is based on comparing a char, initialized to -1, for less than 0. Change the comparison to check for geater than 0 instead...
* Don't reset DST computed by strptime() (when e.g. setting theru2008-02-071-6/+3
| | | | | | | date via -f %s). Reported by: Eugene Grosbein Diagnosed by: Miguel Lopes Santos Ramos
* - Roll-back attempts to mimic rename(2) atomicity introduced in 1.47,dds2007-12-271-95/+69
| | | | | | | | | | | | | | and follow the letter of the POSIX specification. - Moving a directory to an existing non-empty directory will now fail, as required. - Improve consistency and remove some style bugs of earlier versions. This version passes all tests of tools/regression/bin/mv/regress.sh 1.6 Reviewed by: bde MFC after: 1 month
* As suggested, replace earlier changed warnx() / exit() with an errx()edwin2007-12-261-4/+3
| | | | Submitted by: Peter Jeremy <peterjeremy@optushome.com.au>
* When copying multiple files to a directory, make sure that a properedwin2007-12-251-1/+1
| | | | | | | | | warning is given when the directory doesn't exist. PR: bin/50656 Submitted by: Edwin Groothuis <edwin@mavetju.org> Approved by: grog@ Not reviewed by: grog@
* Calling any function from vfork other than exec* and _exit yieldsdds2007-12-171-3/+9
| | | | | | undefined behavior. Noted by: alfred
* Eliminate gcc "variable clobbered" warnings by declaring the variablesdds2007-12-161-1/+2
| | | | | | living across the vfork as volatile. Noted by: kan
* When moving a directory across devices to a place where a directorydds2007-12-161-22/+82
| | | | | | | | | | | | | | | | | with the same name exists, delete that directory first, before performing the copy. This ensures that mv(1) across devices follows the semantics of rename(2), as required by POSIX. This change could introduce the potential of data loss, even if the copy fails, violating the atomicity properties of rename(2). This is (mostly) mitigated by first renaming the destination and obliterating it only after a succesfull copy. The above logic also led to the introduction of code that will cleanup the results of a partial copy, if a cross-device copy fails. PR: bin/118367 MFC after: 1 month
* Move WARNS as ed(1) also is only WARNS = 2 clean in the !DES case.marius2007-12-091-1/+1
| | | | | | | | | This fixes its compilation if MK_OPENSSL == no and also obsoletes release/Makefile rev. 1.192. The latter isn't reverted though as support for the fixit floppy and the rest of the boot floppies is scheduled to be deorbited anyway. Discussed with: kensmith
* Revise the markup.ru2007-12-051-275/+382
|
* Reduce the WARNS level to avoid a compiler warning about a variablejb2007-11-181-1/+1
| | | | possibly being clobbered by a longjmp or a fork with gcc4.
* Express in the usage() and SYNOPSIS that -F depends on -s, andru2007-11-172-4/+8
| | | | that -f and -i are exclusive.
* Swap "source"/"target" where appropriate, to match documentation.ru2007-11-171-38/+38
|
* Teach ps(1) to parse pts TT values (i.e. '0', '1') for the -t flag.jhb2007-11-081-9/+23
| | | | | MFC after: 1 week Reported by: kris
* Bump document date on behalf of previous revision.ru2007-11-011-1/+1
|
* fix sorting of 'tdnam' keyword in keyword list.julian2007-10-281-2/+1
|
* Introduce a way to make pure kernal threads.julian2007-10-264-6/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | kthread_add() takes the same parameters as the old kthread_create() plus a pointer to a process structure, and adds a kernel thread to that process. kproc_kthread_add() takes the parameters for kthread_add, plus a process name and a pointer to a pointer to a process instead of just a pointer, and if the proc * is NULL, it creates the process to the specifications required, before adding the thread to it. All other old kthread_xxx() calls return, but act on (struct thread *) instead of (struct proc *). One reason to change the name is so that any old kernel modules that are lying around and expect kthread_create() to make a process will not just accidentally link. fix top to show kernel threads by their thread name in -SH mode add a tdnam formatting option to ps to show thread names. make all idle threads actual kthreads and put them into their own idled process. make all interrupt threads kthreads and put them in an interd process (mainly for aesthetic and accounting reasons) rename proc 0 to be 'kernel' and it's swapper thread is now 'swapper' man page fixes to follow.
* The exit status of a case statement where none of the patterns is matchedstefanf2007-10-042-0/+5
| | | | | | | | is supposed to be 0, not the status of the previous command. Reported by: Eygene Ryabinkin PR: 116559 Approved by: re (gnn)
* Use owner name and owning group name instead of uid and gidkevlo2007-09-191-2/+30
| | | | | | | for displaying the three-line comment header by default. Reviewed by: kientzle Approved by: re (bmah)
* - Move all of the PS_ flags into either p_flag or td_flags.jeff2007-09-172-7/+6
| | | | | | | | | | | | | | - p_sflag was mostly protected by PROC_LOCK rather than the PROC_SLOCK or previously the sched_lock. These bugs have existed for some time. - Allow swapout to try each thread in a process individually and then swapin the whole process if any of these fail. This allows us to move most scheduler related swap flags into td_flags. - Keep ki_sflag for backwards compat but change all in source tools to use the new and more correct location of P_INMEM. Reported by: pho Reviewed by: attilio, kib Approved by: re (kensmith)
* Take care that the input to setenv() may actually be a pointer straightscf2007-07-061-14/+28
| | | | | | | | from environ; make a copy before manipulating it and passing it to setenv(). Approved by: wes Approved by: re (kensmith)
* Significantly reduce the memory leak as noted in BUGS section forscf2007-07-042-7/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | setenv(3) by tracking the size of the memory allocated instead of using strlen() on the current value. Convert all calls to POSIX from historic BSD API: - unsetenv returns an int. - putenv takes a char * instead of const char *. - putenv no longer makes a copy of the input string. - errno is set appropriately for POSIX. Exceptions involve bad environ variable and internal initialization code. These both set errno to EFAULT. Several patches to base utilities to handle the POSIX changes from Andrey Chernov's previous commit. A few I re-wrote to use setenv() instead of putenv(). New regression module for tools/regression/environ to test these functions. It also can be used to test the performance. Bump __FreeBSD_version to 700050 due to API change. PR: kern/99826 Approved by: wes Approved by: re (kensmith)
* Don't include encryption features of ed(1) when building for thekensmith2007-07-021-0/+2
| | | | | | | "rescue media" bundled with releases. Suggested by: ru Approved by: re (hrs)
* Correct the referenced securelevel document, it's now securelevel 7.remko2007-06-021-2/+2
| | | | Pointed out by: ru
* Fix probably copy&paste from chmod(1) - we change file flags here, not mode.pjd2007-05-281-1/+1
|
* Remove unnecessary free argument casts.brian2007-05-254-32/+29
| | | | Don't abuse arcname's constness.
* Cleanup pax(1) sources a little bit while I poked around in them:rse2007-05-245-25/+25
| | | | | - remove a superfluous doubled trailing semicolon. - remove the extra void casts on calls to void-function free(3).
* In the error handling path, don't call close(fd) if the error we'recperciva2007-05-221-1/+2
| | | | | | | | handling is that fd = open(foo) is -1. This bug is harmless since close(-1) just returns an error (which the code ignores). Found by: Coverity Prevent(tm) CID: 1503 (in userland test run)
* Work around a vendor issue that was causing the builtin malloc to bemp2007-05-162-2/+3
| | | | | | used instead of the system malloc. Submitted by: ume
* Replace a fairly opaque sentence with a much clearer wording from NetBSD.pav2007-05-121-2/+2
| | | | | | PR: docs/101330 (inspired by) Submitted by: Peter Gildea <peter@gildea.com> Obtained from: NetBSD
* Back out all POSIXified *env() changes.ache2007-05-012-13/+8
| | | | | | | | | Not because I admit they are technically wrong and not because of bug reports (I receive nothing). But because I surprisingly meets so strong opposition and resistance so lost any desire to continue that. Anyone who interested in POSIX can dig out what changes and how through cvs diffs.
* Simplify previous fix and disallow VTEXTFIXED direct pass for putenv() too,ache2007-04-301-3/+3
| | | | just use savestr()
OpenPOWER on IntegriCloud