summaryrefslogtreecommitdiffstats
path: root/bin
Commit message (Collapse)AuthorAgeFilesLines
* 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
* - Improve description of the -A option.ru2006-10-121-7/+12
| | | | | | | | - Document how whiteouts look in the long output. [1] - Sort entry types. - Fix description of the socket type. PR: docs/51921 [1]
* Fix style(9) bugs in previous commit.trhodes2006-10-111-7/+4
| | | | Lesson from: bde
* Adhere to POSIX: the -m option only applies to the newly createdru2006-10-101-13/+21
| | | | | | | directories; it should not change the permission bits of already existing directories. Submitted by: Alex Unleashed (modified by me)
* Make -r a synonym for -R, similar to behavior on Linux while being backwardstrhodes2006-10-072-14/+41
| | | | | | | | compatible with old -r behavior with regards to -L. You can now copy fifos and other special files with -r. Reviewed by: -standards (long ago), das, bde Approved by: bde (recently)
* Add the POSIX option -p to the jobs builtin command. It prints the PID of thestefanf2006-10-074-22/+40
| | | | | | | | process leader for each job. Now the last specified option for the output format (-l, -p or -s) wins, previously -s trumped -l. PR: 99926 Submitted by: Ed Schouten and novel (patches modified by me)
* o Style(9).maxim2006-10-071-9/+7
| | | | Submitted by: bde
* o Avoid division by zero.maxim2006-10-071-3/+8
| | | | | | o Place error checking code near to the syscall. Submitted by: bde
* o Hold copied bytes counter in off_t. This prevents statisticsmaxim2006-10-061-1/+1
| | | | | | | | displayed by SIGINFO handler from overflow. PR: bin/104039 Submitted by: Geoffrey Giesemann MFC after: 2 weeks
* Move the -l option processing to where it belongs.ru2006-09-291-4/+4
| | | | Overall still not kosher but better matches style(9).
* Based on The Open Group Base Specifications Issue 6 IEEE Std 1003.1, ourcsjp2006-09-201-2/+11
| | | | | | | | | | | | | | | | | | | | | | current implementation of df(1) is does not properly format the output under certain conditions. Right now -kP and -Pk are not the same thing. Further, when we set the BLOCKSIZE environment variable, we use "1k" instead of "1024", making the header display incorrectly. To quote the specification: "When both the -k and -P options are specified, the following header line shall be written (in the POSIX locale): "Filesystem 1024-blocks Used Available Capacity Mounted on\n" - If -P has been specified, check to make sure that -k has not already been specified, if so, simply break instead of clobbering the previous blocksize - Use 1024 instead of 1k to make the header POSIX compliant Reported by: Andriy Gapon Discussed with: bde, ru MFC after: 1 week
* Markup fixes.ru2006-09-176-10/+14
|
* - Fix options order.ru2006-08-252-7/+7
| | | | - Touch manpage's document date.
* Remove a stray -a option that probably sneaked in from julian'sru2006-08-251-2/+2
| | | | attempt to enter append mode twice in vi(1). :-)
* Add an option to allow copying of a hierarchy while linking he regular files.julian2006-08-244-82/+105
| | | | | | Bikeshedded to death on: hackers Submitted by:andersonatcenttech.com MFC in: 1 month
* For the sake of clarity, explicitly tell that comma and spaceyar2006-08-211-2/+3
| | | | | | characters can be included in a custom column title string -- that's why it may appear at the end of a keyword list argument only.
* Prefer strlcpy to strncpy. In one case, this saves us from re-zeroingimp2006-08-201-2/+2
| | | | | data that's alreday 0. In another, it saves us from zeroing data that will be overwritten again.
* Use strlcpy in place of strncpy + setting the last character NUL. Toimp2006-08-201-2/+2
| | | | be safe, memset the entire msg to '0'.
* Document a detail in the present syntax of "ps -o foo=bar". Nowyar2006-08-181-6/+7
| | | | | | | | the header title string "bar" extends to the end of the argument even if it contains commas or spaces, unlike in RELENG_4 or earlier. The modern syntax agrees with SUSv3. MFC after: 3 days
* while(0); -> while (0) in multiline macroimp2006-08-171-1/+1
|
* Commit the results of the typo hunt by Darren Pilgrim.yar2006-08-041-1/+1
| | | | | | | | | | This change affects documentation and comments only, no real code involved. PR: misc/101245 Submitted by: Darren Pilgrim <darren pilgrim bitfreak org> Tested by: md5(1) MFC after: 1 week
* Do not forget to increment the input line counteryar2006-07-311-0/+1
| | | | | | | when reading a word spanning multiple lines. PR: bin/101094 MFC after: 5 days
* Granting the amount of misunderstanding the last change received,yar2006-07-311-1/+7
| | | | extend it with an example to clarify the point.
* Tell more of the sh(1) history.yar2006-07-291-2/+17
| | | | | | Acknowledge Kenneth Almquist's contribution in AUTHORS. MFC after: 5 days
* Document that both sides of -a or -o are always evaluated. Thisyar2006-07-271-1/+8
| | | | | | | | | "feature" doesn't seem to be in the standards or elsewhere, and it is against what we are used to in C and sh(1), so put the paragraph under BUGS. Pointed out by: dougb MFC after: 3 days
* Make it easier to find that we have test(1) built-in in sh(1).yar2006-07-261-4/+9
| | | | MFC after: 3 days
* More inactive maintainers.markm2006-07-091-2/+0
|
* o Call fts_close() before exit.maxim2006-07-041-0/+1
| | | | Obtained from: NetBSD, Coverity ID 1754
* Document the fact that 'true' and 'false' are among sh(1) built-in commands.yar2006-06-211-1/+5
| | | | MFC after: 3 days
* Merge NetBSD's revision 1.86: Don't crash on "<cmd> | { }".stefanf2006-06-151-1/+1
|
* Implement the PS4 variable which is defined by the POSIX User Portabilitystefanf2006-06-154-6/+23
| | | | | | | | | | | | Utilities option. Its value is printed at the beginning of the line if tracing (-x) is active. PS4 defaults to the string "+ " which is compatible with the old behaviour to always print "+ ". We still need to expand variables in PS1, PS2 and PS4. PR: 46441 (part of) Submitted by: schweikh Obtained from: NetBSD
* Don't strip a leading ./ from the path for the cd builtin to avoid interpretingstefanf2006-06-121-2/+3
| | | | | | | | | | .//dir as /dir. Rather strip it only for the purpose of checking if the directory path should be printed. PR: 88813 Submitted by: Josh Elsasser Patch from: NetBSD (cd.c rev 1.38) MFC after: 2 weeks
* o Fix grammar, format.maxim2006-06-091-3/+3
|
* Document the way to get list of files to process from the stdin.kib2006-06-091-1/+3
| | | | | MFC after: 1 week Approved by: kan (mentor)
* Copy filename read from the stdin into the private buffer. Otherwise,kib2006-06-091-1/+5
| | | | | | | | | next read filename overwrite previous one, resulting in acl being applied only to the last name in the list. Submitted by: Oleg Lomaka <oleg.lomaka at gmail com> MFC after: 1 week Approved by: kan (mentor)
* Fix the wording about the blocksize (-b) parameter. The existingcokane2006-05-101-2/+3
| | | | | | | | | wording makes it look like pax archives > 32256 bytes are not POSIX-compliant! Correct this to state that pax archives with block sizes > 32256 are not POSIX compliant...and settle our fears. PR: docs/97059 Reviewed by: Giorgos Keramidas <keramida>
OpenPOWER on IntegriCloud