summaryrefslogtreecommitdiffstats
path: root/bin
Commit message (Collapse)AuthorAgeFilesLines
* 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()
* Put some safeguards:ache2007-04-301-4/+9
| | | | | | | 1) Under POSIX unsetenv("foo=bar") is explicit error and not equal to unsetenv("foo") 2) Prepare for upcomig POSIXed putenv() rewrite: make putenv() calls portable and conforming to standard.
* Eliminate error with -W* strict flags and make putenv() calls conforming toache2007-04-301-4/+4
| | | | standard in the same way as f.e. gcc internal portable code does.
* Move uuidgen(1) from /usr/bin/ to /bin/. It will be used in rc.d/hostidpjd2007-04-091-0/+2
| | | | | | script, which will be executed before /usr/ mount. Reviewed by: mlaier, rink, brooks, rwatson
* getblocksize expects pointer to long as a second argument, notkan2007-04-061-2/+2
| | | | a pointer to u_long.
* Build updates for tcsh-6.15.00 import.mp2007-03-112-23/+39
| | | | | | Reviewed by: ume Reminded by: Divacky Roman MFC after: 1 week
* Fix a bug where the mutual exclusivity of the -l and -t options is notwill2007-03-081-1/+4
| | | | | | | recognized properly if -l is specified first. PR: bin/105721 MFC after: 1 week
* Fix markup.ru2007-03-041-5/+8
|
* Fix markup.ru2007-03-041-16/+13
|
* Fix markup.ru2007-02-281-2/+3
|
* Fix markup.ru2007-02-271-10/+20
|
* Implement the -h flag (set an ACL on a symbolic link).mckusick2007-02-261-4/+14
| | | | | | | Before this fix the -h flag was ignored (i.e. setfacl always set the ACL on the file pointed to by the symbolic link even when the -h flag requested that the ACL be set on the symbolic link itself).
* Correct typos containing my login name (plus one more in expr.y).ceri2007-02-181-2/+2
| | | | Found courtesy of a recursive grep in the wrong directory.
* Use eaccess() instead of access() for the type builtin, like we do for thestefanf2007-01-181-1/+1
| | | | | | test builtin. Submitted by: Martin Kammerhofer
* Return an error status (127) from the builtins 'type' and 'command' (withstefanf2007-01-111-2/+5
| | | | | | | | | | either -v or -V) if a file with a slash in the name doesn't exist (if there is no slash we already did that). Additionally, suppress the error message for command -v for files with a slash. PR: 107674 Submitted by: Martin Kammerhofer
* Fix markup.ru2006-12-271-5/+7
|
* More markup fixes.ru2006-12-271-3/+3
|
* Fix markup.ru2006-12-271-6/+7
|
* Give a hint to the reader as to what the "whiteout" actually means.ru2006-12-261-2/+3
|
* Fix markup, add the EXIT STATUS section.ru2006-12-261-7/+12
|
* One more nit.ru2006-12-231-1/+1
|
* Fix markup.ru2006-12-231-10/+12
|
* - Mention umask(2) when first referring to it.ru2006-12-221-2/+6
| | | | | | - Add missing markup. Submitted by: Eugene Grosbein <eugen@grosbein.pp.ru>
* Use a standard section name.ru2006-12-181-1/+1
|
* Simplify some markup.ru2006-12-141-32/+34
|
* Style(9) fixes, thanks to Ruslan.kientzle2006-12-082-7/+8
|
* Support the "-f" option by simply ignoring it.kientzle2006-12-082-2/+11
| | | | | | | | | This allows script compatibility with Linux, whose "hostname" is the same as BSD "hostname -s". With this change, "hostname -f" is the same on both systems. MFC after: 7 days
* Once upon a time, the hostname was being set in the /etc/netstart,ru2006-12-051-2/+2
| | | | | | which can be called a "network initialization script", now that it is set in /etc/rc.d/hostname, "network" sounds confusing, so remove it.
* Fix some of the alignment warnings on ARM.ru2006-11-272-17/+17
|
* Fix expanding of quoted positional parameters in case patterns.stefanf2006-11-071-6/+6
| | | | | | Obtained from: NetBSD (expand.c 1.58 and 1.59) Submitted by: Paul Jarc PR: 56147
* When parsing an invalid parameter expansion (eg. ${} or ${foo@bar}) do notstefanf2006-11-053-9/+25
| | | | | | | | | | | issue a syntax error immediately but save the information that it is erroneous for later when the parameter expansion is actually done. This means eg. "false && ${}" will not generate an error which seems to be required by POSIX. Include the invalid parameter expansion in the error message (sometimes abbreviated with ... because recovering it would require a lot of code). PR: 105078 Submitted by: emaste
* Fix typo.ceri2006-11-021-1/+1
|
* Correct a security issue introduced in previous commit:delphij2006-10-312-3/+11
| | | | | | | | | | | | | | | | | | | | instead of removing the file and issue a warning about the removal, do not do any operation at all in case -P is specified when the dinode has hard links. With -f and -P specified together, we assume that the user wants rm to overwrite the contents of the file and remove it (destroy the contents of file but leave its hard links as is). The reason of doing it this way is that, in case where a hard link is created by a malicious user (currently this is permitted even if the user has no access to the file). Losing the link can potentially mean that the actual owner would lose control completely to the user who wants to obtain access in a future day. Discussed with: Peter Jermey
* Be more reasonable when overwrite mode is specified while theredelphij2006-10-302-1/+8
| | | | | | | | | is hard links. Overwritting when links > 1 would cause data loss, which is usually undesired. Inspired by: discussion on -hackers@ Suggested by: elessar at bsdforen de Obtained from: OpenBSD
* Wording nits.trhodes2006-10-271-11/+7
|
* Flesh out the compatibility section a little bit. Bump doc date.trhodes2006-10-241-30/+20
|
* o Backout rev. 1.55. Don't waste cpu cycles for bzero(), do notmaxim2006-10-181-2/+1
| | | | | | call chflags() for whiteouted files. Prodded by: ru
* Avoid a spurious warning for each whiteout found during "ls -lW".ru2006-10-181-2/+3
| | | | | | | | # ls -lW total 2 -rw-r--r-- 1 root wheel 6 Oct 18 14:46 file1 ls: ./file2: No such file or directory w--------- 0 root wheel 0 Jan 1 1970 file2
* o Zero out struct stat before usage. lstat(2) can fail andmaxim2006-10-181-0/+1
| | | | | | | | leave garbage there which will break -W code path. PR: bin/84569 Submitted by: Igor MFC after: 2 weeks
OpenPOWER on IntegriCloud