| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
bsd.*.mk infrasture.
Obtained from: ru
|
|
|
|
| |
so use default WARNS level from bin/Makefile.inc
|
| |
|
| |
|
|
|
|
|
| |
Approved by: grehan (mentor)
Obtained from: DragonFlyBSD
|
|
|
|
|
| |
Requested by: ru
Approved by: grehan (mentor)
|
|
|
|
|
|
|
| |
- Add WARNS?= 6
Approved by: stefanf, grehan (mentor)
Obtained from: DragonFlyBSD
|
| |
|
| |
|
|
|
|
| |
Sort standard sections in the (documented) preferred order.
|
| |
|
| |
|
|
|
|
| |
header update.
|
|
|
|
|
|
|
|
| |
match.
PR: 28095
Submitted by: bill at twwells dot com
MFC after: 7 days
|
|
|
|
|
|
|
|
|
|
|
| |
regardless whether the output is to a terminal or not. As this is
consistent with the SUSPv2 specification (even though we do not
otherwise fully implement SUSPv2's ls(1) options), document this as it
is now, rather than trying to change the behaviour itself.
PR: docs/76072
Submitted by: Sebastian Rey <Sebastian.rey@gmx.net>
MFC after: 1 week
|
| |
|
|
|
|
| |
that nai was OK with all third clause removals.
|
| |
|
| |
|
|
|
|
| |
Pointed out by: ru (some time ago)
|
| |
|
| |
|
|
|
|
|
| |
Reviewed by: ru
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
XXX from Tor: "The shell can also go into a similar loop if the child was
killed by signal 127, since the shell would believe the child to have
only stopped (WIFSTOPPED() macro returns nonzero value). Disallowing
signals 127 and 128 will fix that problem." See kern/19402 for details.
PR: bin/66242
Submitted by: tegge
Analysis and testcase by: demon
MFC after: 3 weeks
|
|
|
|
|
|
| |
Remove reference to /dev/lomac, which is no longer used by mac_lomac(4).
MFC after: 3 days
|
|
|
|
| |
to "rmdir -p" is absolute, with one or more leading slash.
|
|
|
|
| |
(This also fixes "rmdir -v /nonexistent".)
|
|
|
|
|
|
|
| |
play nicer in prisons. It also simplifies things.
Reviewed by: rwatson
Bumped into by: Jilles Tjoelker
|
|
|
|
|
|
|
|
|
|
|
| |
printing of the process environment will fail silently.
-define a function which will check to see if procfs is mounted on /proc
-Implement this test if the user specified -e
-If procfs is not mounted on /proc and -e was specified, print a warning.
informing the user that procfs(5) is required.
Reviewed by: wes, rwatson
|
| |
|
|
|
|
|
|
|
|
|
|
| |
WRT handling file and link names that reach the allowed
maximum for old tar and ustar archive formats.
PR: bin/40466
Submitted by: Cyrille Lefevre <email in the PR> (portions)
Reviewed by: freebsd-arch (silence)
MFC after: 1 month
|
| |
|
|
|
|
|
| |
This change is NOP, because TTYDEF_LFLAG = TTYDEF_LFLAG_ECHO now,
but to minimize diffs with other BSDs.
|
|
|
|
|
|
|
|
| |
to PRECIOUSLIB from bsd.lib.mk. The side effect of this
is making installing the world under jail(8) possible by
using another knob, NOFSCHG.
Reviewed by: oliver
|
|
|
|
|
|
| |
PR: 73423
Submitted by: Michiel Boland <michiel@boland.org>
Overlooked by: phk
|
|
|
|
|
|
|
|
| |
instead of just !, this allows one to more easily locate/understand
the section of the manpage in question.
Additional wording correction by: keramida
Reviewed by: keramida
|
|
|
|
|
| |
Pointed out by: dd
Approved by: murray (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
removing directories or if more than 3 files are listed in the
command line.
This feature is intended to provide a safe net but not being too
annoying like having "rm -i" for every deleting operations, and
is generally good for both newbies and power users, preventing
them from being so easily run into ``rm -rf /'', ``rm -rf *''
and so forth.
Originally implemented by Matthew Dillon for DragonFly, plus
some improvements done by various DragonFly contributors.
Approved by: murray (mentor; the original dillon's version)
Discussed with: des
Obtained from: DragonFly's bin/rm/
rm.c rev. 1.4 - 1.8
rm.1 rev. 1.3 - 1.4
MFC After: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
occurrences of "/" in the argument list. This corresponds to Enhancement
Request Number 5 in the Austin Group TC2 Aardvark's XCU Defects Report
(<URL:http://www.opengroup.org/austin/aardvark/finaltext/xcubug.txt>).
Further discussion is available in the Austin Group mailing list archives
(<URL:http://www.opengroup.org/austin/mailarchives/>, "Defect in XCU rm")
and for Austin Group members, in the Austin Group Interpretations archive
(<URL:http://www.opengroup.org/austin/interps/>, AI-019)
This commit makes that check conditional on !POSIXLY_CORRECT, since it
is not strictly correct according to the current version of the standard
(but is expected to be correct according to the next version, and has
already been adopted by Solaris).
|
|
|
|
| |
Pointed out by: ru
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
considered an error according to the Open Group Base Specification.
PR: standards/45738
Submitted by: Matthias Andree <matthias.andree@web.de>
MFC after: 3 days
|
|
|
|
| |
PR: 71743
|
|
|
|
|
| |
PR: docs/70856
Submitted by: Rostislav Krasny <rosti_bsd@yahoo.com>
|
|
|
|
|
|
|
| |
to specify an alternative padding character when using a conversion
mode, or when using noerror with sync and an input error occurs. This
facilities reading old and error-prone media by allowing the user to
more effectively mark error blocks in the output stream.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on March 31 won't take you to March 2 or 3 (now the result will
be the last day of February.)
In general, now stepping by months from the last days of the current
month A will take you to the very last day of the target month B if
B is shorter than A.
The previous version would just step to March 31 and rely on mktime(3)
to correct the date. Despite its simplicity, such way was counter-intuitive
to users and caused pain to shell script writers.
Noticed by: Igor Timkin <ivt at gamma dot ru>
Approved by: brian
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
| |
of releases. The -DNOCRYPT build option still exists for anyone who
really wants to build non-cryptographic binaries, but the "crypto"
release distribution is now part of "base", and anyone installing from a
release will get cryptographic binaries.
Approved by: re (scottl), markm
Discussed on: freebsd-current, in late April 2004
|