summaryrefslogtreecommitdiffstats
path: root/bin
Commit message (Collapse)AuthorAgeFilesLines
* Reject options, handle "--" correctly in unlink(1).tjr2002-05-301-4/+7
|
* Reject options, handle "--" end-of-options marker in link(1).tjr2002-05-301-4/+7
|
* mdoc(7) police: punctuation.ru2002-05-291-1/+1
|
* mdoc(7) police: tidy up the markup a bit.ru2002-05-291-142/+41
|
* mdoc(7) police: markup nits.ru2002-05-291-11/+11
|
* mdoc(7) police: markup nits.ru2002-05-291-2/+3
|
* mdoc(7) police: punctuation.ru2002-05-291-3/+3
|
* mdoc(7) police: replace the XXX with the correct width.ru2002-05-291-2/+1
|
* Add uuidgen(2) and uuidgen(1).marcel2002-05-283-0/+190
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The uuidgen command, by means of the uuidgen syscall, generates one or more Universally Unique Identifiers compatible with OSF/DCE 1.1 version 1 UUIDs. From the Perforce logs (change 11995): Round of cleanups: o Give uuidgen() the correct prototype in syscalls.master o Define struct uuid according to DCE 1.1 in sys/uuid.h o Use struct uuid instead of uuid_t. The latter is defined in sys/uuid.h but should not be used in kernel land. o Add snprintf_uuid(), printf_uuid() and sbuf_printf_uuid() to kern_uuid.c for use in the kernel (currently geom_gpt.c). o Rename the non-standard struct uuid in kern/kern_uuid.c to struct uuid_private and give it a slightly better definition for better byte-order handling. See below. o In sys/gpt.h, fix the broken uuid definitions to match the now compliant struct uuid definition. See below. o In usr.bin/uuidgen/uuidgen.c catch up with struct uuid change. A note about byte-order: The standard failed to provide a non-conflicting and unambiguous definition for the binary representation. My initial implementation always wrote the timestamp as a 64-bit little-endian (2s-complement) integral. The clock sequence was always written as a 16-bit big-endian (2s-complement) integral. After a good nights sleep and couple of Pan Galactic Gargle Blasters (not necessarily in that order :-) I reread the spec and came to the conclusion that the time fields are always written in the native by order, provided the the low, mid and hi chopping still occurs. The spec mentions that you "might need to swap bytes if you talk to a machine that has a different byte-order". The clock sequence is always written in big-endian order (as is the IEEE 802 address) because its division is resulting in bytes, making the ordering unambiguous.
* Note that the lutimes(2) and lchflags(2) syscalls also do not follow symlinks.tjr2002-05-261-13/+16
| | | | | | | Remove incorrect examples. PR: 25016 Submitted by: Martin Kammerhofer, Joshua Goodall
* Add lchmod(2) to the list of syscalls that do not follow symbolic links.tjr2002-05-261-1/+3
|
* sh appeared in Version 1, not System V.1.tjr2002-05-251-1/+1
|
* Implement `set +o', which displays the currently set options in a formattjr2002-05-252-5/+28
| | | | suitable for re-input into the shell.
* Bring back the cd -L and -P options from revision 1.24, but try harder nottjr2002-05-221-33/+105
| | | | | | to fail when the logical current directory no longer exists. Allow changes to absolute paths when logical cwd is invalid, fall back to physical cd if logical cd fails.
* Temporarily back out revision 1.24; it seems to handle the case where thetjr2002-05-221-78/+22
| | | | current directory no longer exists incorrectly and breaks `make cleandir'.
* Add the SUSv3 -L and -P options to the cd and pwd builtin utilities. `Logical'tjr2002-05-202-24/+110
| | | | handling of .. is now the default.
* Remove a small, annoying, nit I ran in to editing this file, a lone tabjmallett2002-05-191-1/+1
| | | | on a line by itself.
* Implement the -u (-o nounset) option, which gives an error message iftjr2002-05-192-1/+11
| | | | | | an unset variable is expanded. Obtained from: NetBSD (bjh21, christos)
* Make the fg and bg commands give the output required by SUSv3.tjr2002-05-191-0/+10
| | | | | fg outputs the name of the command, bg outputs the name of the command and the job id.
* Implement the -C (-o noclobber) option, which prevents existing regulartjr2002-05-198-1/+19
| | | | files from being overwritten by shell redirection.
* Add missing options required by SUSv3:tjr2002-05-195-16/+100
| | | | | | | | -m List files across the page, separated by commas. -p Print a slash after directory names -x Same as -C but sort across the columns rather than down Submitted by: Kyle Martin <mkm@ieee.org>
* Unconditionally update the maximum field width statistics when weiedowse2002-05-181-5/+3
| | | | | | | refetch the filesystem information in MNT_WAIT mode. This avoids incorrect column alignment that sometimes occurs with NFS filesystems. Submitted by: Ian <freebsd@damnhippie.dyndns.org>
* Back out part of previous commit: make -P the default again until I'mtjr2002-05-182-2/+2
| | | | convinced it's a good idea.
* Make -L the default, allow both -L and -P to be specified (last one usedtjr2002-05-182-11/+16
| | | | matters), fall back to -P mode if we can't get the logical directory.
* Optimize prev. commit code a bitache2002-05-171-4/+4
|
* Trailing slash fixes.ache2002-05-171-2/+12
| | | | | | | | | | Fix the case: cp file nonexistent/ which create nonextstent as file while trailing slash clearly indicates that nonexistent must be a directory. Also fix the case: cp file1 file2/ which should produce error.
* Remove local definition of _PATH_CP, and use <paths.h>, _PATH_CP is in thejmallett2002-05-172-1/+1
| | | | CURRENT <paths.h>.
* The sysctl has changed from 'kern.ps_showallprocs' tojoe2002-05-161-1/+1
| | | | 'security.bsd.see_other_uids'.
* more file system > filesystemtrhodes2002-05-161-1/+1
|
* Consistancy check s/file system/filesystem/trhodes2002-05-1620-46/+46
| | | | Reviewed by: brian
* restore missing default case removed in ls.c:r1.57billf2002-05-152-0/+4
| | | | | | add break statements to default cases where missing. Submitted by: bde
* Make 'user' and 'group' const as to not discard the qualifier from thejmallett2002-05-151-1/+2
| | | | | functions we use to assign them. Doesn't seem to be anything else that relies on these being non-const.
* Remove an empty default case to make this syntactically correct. Not therejmallett2002-05-151-1/+0
| | | | is as good as blaknk.
* Remove the private code for reading UFS superblocks, this does not belongphk2002-05-122-110/+36
| | | | | | | | | | | | | | | | in df(1) when we have multiple filesystem types, and the complications of handling UFS2 pushes this over the edge. Use the .../mount/extern.h to get prototypes of the functions we borrow from there. Constify things to match. (why aren't these functions in a lib anyway ?) Make everything static and set WARNS?=5. The way the "df diskdevice" thing works for unmounted diskdevices is not very general. Sponsored by: DARPA & NAI Labs.
* Add semicolon to empty default case to silence warning.jedgar2002-05-111-0/+1
|
* EXPR_COMPAT should imply -e, since there is no way to specify it otherwise,wollman2002-05-112-1/+18
| | | | and -e reflects the historic behavior of FreeBSD's expr.
* while i'm breaking stuff, use __dead2 instead of GCC specific __attribute__.alfred2002-05-111-2/+1
|
* backout additional include of cdefs.h, it's not helping any.alfred2002-05-111-1/+0
|
* include cdefs.h for __printf0like to silence warning.alfred2002-05-111-0/+1
|
* Add semicolon to empty default case to silence warning.jedgar2002-05-111-0/+1
|
* Add semicolon to empty default case to silence warning.alfred2002-05-111-0/+1
|
* The response to my POSIX interpretation request says that `expr'wollman2002-05-102-46/+88
| | | | | | is required to be oblivious to overflow and to use the data type `long'. (Division by zero is undefined in ISO C so it's still OK to check for it here.) Add a new `-e' flag to get the old, more useful behavior.
* Remove gCC'isms.obrien2002-05-101-1/+0
|
* Replace /kernel with /boot/kernel/kernel.joe2002-05-091-2/+2
| | | | | PR: docs/37757 Submitted by: Hiten Pandya <hiten@uk.FreeBSD.org>
* Use <paths.h> rather than "pathnames.h", and fix a couple of whitespace nits.des2002-05-082-45/+10
| | | | Sponsored by: DARPA, NAI Labs
* Check for possible overflow from sysconf _SC_ARG_MAX and error out in ajmallett2002-05-051-5/+10
| | | | | | | | | | | | | | | correct manner. Revert my incorrect change to use err(3) for malloc(3) failing. Use a size_t variable to store the size of the argument buffer we allocate, and remove silly casts as the result of having this around. Modify the math in some of the paranoid checks for buffer overflow to account for the fact we now are dealing with the actual size of the buffer. Remove the static qualifier for arg_max, and the bogus setting of it to -1. Include <limits.h> for the definitions we use to check for possible overflows. Submitted by: bde
* Don't cast incorrectly to malloc(3), and don't use errx(3) if malloc(3)jmallett2002-05-021-2/+2
| | | | returns NULL, as malloc(3) sets errno. Use err(3).
* Reorder for style.markm2002-04-281-3/+3
|
* Provide an environment variabloe, EXPR_COMPAT, which disables optionwollman2002-04-222-10/+27
| | | | parsing for compatibility with old implementations.
* Usage style sweep: spell "usage" with a small 'u'.des2002-04-221-1/+1
| | | | | Also change one case of blatant __progname abuse (several more remain) This commit does not touch anything in src/{contrib,crypto,gnu}/.
OpenPOWER on IntegriCloud