| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
cases and broke the world in some cases.
Fixed some style bugs (the usual ones for DPADD and LDADD, misplacement
of DPADD and LDADD, and misplacement of $FreeBSD$).
|
|
|
|
|
| |
PR: 17250
Submitted by: cjclark@home.com (Crist J. Clark)
|
| |
|
| |
|
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
|
|
|
| |
put the whitespace in the right place.
|
| |
|
|
|
|
| |
Brucified by: bde
|
|
|
|
|
|
|
|
|
|
|
| |
operands. Can _YOU_ tell skip= and seek= apart with 100% accuracy
every time?
This also seems to make us option-for-option compatible with the
Solaris dd(1).
Approved by: jkh
Suggested by: peter
|
| |
|
|
|
|
| |
Approved by: jkh
|
|
|
|
|
| |
PR: 16750
Submitted by: Giorgos Keramidas <keramida@ceid.upatras.gr>
|
|
|
|
|
|
|
|
|
|
| |
The description of -X option in csh(1) manpage uses a wording
that references the descriptions of -x, -v and -V. This might
be a little confusing. Changed this to a complete description
that does not reference other paragraphs.
PR: 16762
Submitted: Giorgos Keramidas <keramida@ceid.upatras.gr>
|
|
|
|
|
|
|
|
|
|
|
| |
The first paragraph of "Argument list processing" says that an
argument of - will make csh be a login shell. However, running
csh with only a - as an argument fails with the error message.
csh(1) corrected to reflect this.
PR: 16754
Submitted by: Giorgos Keramidas <keramida@ceid.upatras.gr>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Three minor changes to the manpage of chmod(1).
1. At the description of -H option, I added that symlinks are
not followed _by default_ to show that links can be followed,
but the default chmod behavior is not to do so.
2. Moved a misplaced .Va file command up to the place it belongs.
3. Simplified the grammar that describes symbolic modes.
PR: 16749
Submitted by: Giorgos Keramidas <keramida@ceid.upatras.gr>
|
|
|
|
|
|
|
| |
Approved-by: jkh
PR: bin/12137
Submitted by: "Danny J. Zerkel" <dzerkel@columbus.rr.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
interface, and statically link them to the programs using them.
These functions, upon reflection and discussion, are too generically
named for a library interface with such specific functionality.
Also the api that they use, whilst ok for private use, isn't good
enough for a libc function.
Additionally there were complications with the build/install-world
process. It depends heavily upon xinstall, which got broken by
the change in api, and caused bootstrap problems and general mayhem.
There is work in progress to address future problems that may be
caused by changes in install-chain tools, and better names for
{g|s}etflags can be derived when some future program requires them.
For now the code has been left in src/lib/libc/gen (it started off
in src/bin/ls).
It's important to provide library functions for manipulating file
flag strings if we ever want this interface to be adopted outside
of the source tree, but now isn't necessarily the right moment
with 4.0-release just around the corner.
Approved: jkh
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
string to u_long and back using two functions, flags_to_string and
string_to_flags, which co-existed with 'ls'. As time has progressed
more and more other tools have used these private functions to
manipulate the file flags.
Recently I moved these functions from /usr/src/bin/ls to libutil,
but after some discussion with bde it's been decided that they
really ought to go in libc.
There are two already existing libc functions for manipulating file
modes: setmode and getmode. In keeping with these flags_to_string
has been renamed getflags and string_to_flags to setflags.
The manual page could probably be improved upon ;)
|
|
|
|
| |
Submitted by: Dan Papasian (bugg_ on irc)
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
. add Xrs to hosts.equiv(5), auth.conf(5), services(5) to some pages
. sort Xrs in SEE ALSO sections
Patches based on PR: docs/15680
Submitted by: Christian Weisgerber <naddy@mips.rhein-neckar.de>
|
|
|
|
|
| |
essentially large unsigned ones, and we already print minor
numbers > 255 in hex.
|
| |
|
|
|
|
| |
Obtained from: bde
|
|
|
|
| |
Noticed by: bde
|
| |
|
|
|
|
| |
many places nowadays.
|
|
|
|
|
|
|
|
|
|
|
|
| |
from the source attributed below. In particular, this removes a goto
inside a switch and replaces those horrendous ATOI macros with
something acceptable.
More clean-ups to come.
PR: bin/14151
Reported by: Christian Weisgerber <naddy@mips.rhein-neckar.de>
Obtained from: NetBSD
|
|
|
|
|
|
|
|
| |
for example "/bin/[".
Reported by: Vlad Skvortsov <vss@ulstu.ru>
Reported by: Peter Jeremy <peter.jeremy@alcatel.com.au>
Message-Id: 99Dec27.111307est.40321@border.alcanet.com.au
|
|
|
|
|
|
|
|
|
|
| |
common way of setting the hostname. The man page already mentioned that
the hostname is set by /etc/rc.network, so this just explains where
/etc/rc.network gets the hostname from.
PR: docs/14319
Submitted by: rwatson
Reviewed by: cmc
|
|
|
|
|
|
| |
a '\0' at the end of a string.
Submitted by: Martin Birgmeier <Martin.Birgmeier@aon.at>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
respectively, in accordance with SUSv2.
This differs from the approach taken in NetBSD, but provides
less obscure error messages in at least the EISDIR case and
does not take up additional disk space for new binaries.
PR: 13071
PR: 13074
Requested by: James Howard <howardjp@wam.umd.edu>
|
|
|
|
|
|
| |
PATH=... command
Noted by and fix works for Marcel Moolenaar <marcel@scc.nl>
|
|
|
|
|
| |
PR: bin/3648
Submitted by: Martin Birgmeier <mbirg@austria.ds.philips.com>
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Obtained from: parts of human readable code from OpenBSD
Reviewed by: obrien
add POSIX, byte and megabyte block size ouput flags
PR: 13579 (POSIX flag)
Submitted by: Mike Meyer <mwm@phone.net>
|
|
|
|
|
|
|
| |
the correct (but less aesthetic) way, now. New lesson: correctness
and aestheticity may be mutually exclusive at times.
Brucified by: bde
|
|
|
|
|
|
|
| |
bfumerola for that pointer!) in GCC complaining about losing a const.
While I'm here, might as well mark in the Makefile that I'm the
${MAINTAINER}. It seems like that's what everyone's doing these days.
|
|
|
|
|
| |
PR: docs/15265
Submitted by: takamune@avrl.mei.co.jp
|
|
|
|
| |
discussed on -arch.
|
|
|
|
| |
Fix a warning.
|
|
|
|
| |
Fix usage() style bug spotted by BDE.
|
|
|
|
| |
Reviewed by: obrien
|
| |
|