| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Obtained from: NetBSD (expand.c 1.58 and 1.59)
Submitted by: Paul Jarc
PR: 56147
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
|
| |
call chflags() for whiteouted files.
Prodded by: ru
|
|
|
|
|
|
|
|
| |
# 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
|
|
|
|
|
|
|
|
| |
leave garbage there which will break -W code path.
PR: bin/84569
Submitted by: Igor
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
- Document how whiteouts look in the long output. [1]
- Sort entry types.
- Fix description of the socket type.
PR: docs/51921 [1]
|
|
|
|
| |
Lesson from: bde
|
|
|
|
|
|
|
| |
directories; it should not change the permission bits of already
existing directories.
Submitted by: Alex Unleashed (modified by me)
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
| |
Submitted by: bde
|
|
|
|
|
|
| |
o Place error checking code near to the syscall.
Submitted by: bde
|
|
|
|
|
|
|
|
| |
displayed by SIGINFO handler from overflow.
PR: bin/104039
Submitted by: Geoffrey Giesemann
MFC after: 2 weeks
|
|
|
|
| |
Overall still not kosher but better matches style(9).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
- Touch manpage's document date.
|
|
|
|
| |
attempt to enter append mode twice in vi(1). :-)
|
|
|
|
|
|
| |
Bikeshedded to death on: hackers
Submitted by:andersonatcenttech.com
MFC in: 1 month
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
data that's alreday 0. In another, it saves us from zeroing data that
will be overwritten again.
|
|
|
|
| |
be safe, memset the entire msg to '0'.
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
when reading a word spanning multiple lines.
PR: bin/101094
MFC after: 5 days
|
|
|
|
| |
extend it with an example to clarify the point.
|
|
|
|
|
|
| |
Acknowledge Kenneth Almquist's contribution in AUTHORS.
MFC after: 5 days
|
|
|
|
|
|
|
|
|
| |
"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
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
| |
Obtained from: NetBSD, Coverity ID 1754
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
.//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
|
| |
|
|
|
|
|
| |
MFC after: 1 week
Approved by: kan (mentor)
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
sorted. Sort the variables before printing.
PR: 96415
|
|
|
|
|
|
|
|
|
| |
own buffer. Interactively typing in long lines (>1023 characters)
previously overflowed the buffer. Unlike the NetBSD people I don't see the
need to subtract 8 from BUFSIZ, so I just used BUFSIZ-1.
Obtained from: NetBSD
PR: 91110
|
| |
|
| |
|
|
|
|
|
|
| |
PR: bin/95292
Submitted by: Charles Hardin
Obtained from: NetBSD via OpenBSD, PR
|