| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
"rescue media" bundled with releases.
Suggested by: ru
Approved by: re (hrs)
|
|
|
|
| |
Pointed out by: ru
|
| |
|
|
|
|
| |
Don't abuse arcname's constness.
|
|
|
|
|
| |
- remove a superfluous doubled trailing semicolon.
- remove the extra void casts on calls to void-function free(3).
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
| |
used instead of the system malloc.
Submitted by: ume
|
|
|
|
|
|
| |
PR: docs/101330 (inspired by)
Submitted by: Peter Gildea <peter@gildea.com>
Obtained from: NetBSD
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
just use savestr()
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
standard in the same way as f.e. gcc internal portable code does.
|
|
|
|
|
|
| |
script, which will be executed before /usr/ mount.
Reviewed by: mlaier, rink, brooks, rwatson
|
|
|
|
| |
a pointer to u_long.
|
|
|
|
|
|
| |
Reviewed by: ume
Reminded by: Divacky Roman
MFC after: 1 week
|
|
|
|
|
|
|
| |
recognized properly if -l is specified first.
PR: bin/105721
MFC after: 1 week
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
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).
|
|
|
|
| |
Found courtesy of a recursive grep in the wrong directory.
|
|
|
|
|
|
| |
test builtin.
Submitted by: Martin Kammerhofer
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
- Add missing markup.
Submitted by: Eugene Grosbein <eugen@grosbein.pp.ru>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
which can be called a "network initialization script", now that it
is set in /etc/rc.d/hostname, "network" sounds confusing, so remove
it.
|
| |
|
|
|
|
|
|
| |
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
|