- Copy stable/10 (r259064) to releng/10.0 as part of the
10.0-RELEASE cycle.
- Update __FreeBSD_version [1]
- Set branch name to -RC1

[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so
start releng/10.0 at '100' so the branch is started with
a value ending in zero.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.

Approved by: re (implicit)
Sponsored by: The FreeBSD Foundation

Add 'static' where able.

Fix wording nit.

PR: 174787
Submitted by: Cody Rank
MFC after: 3 days

Add a couple of examples.

Obtained from: OpenBSD

Put some static keywords in the source code.

For these simple utilities, it doesn't harm to make all global variables
static. In fact, this allows the compiler to perform better forms of
optimisation and analysis.

bin: Prefer strrchr() to rindex().

This removes the last index/rindex usage from /bin.

Spelling fixes.

symlink(7): Add lpathconf(2) and *at system calls.

MFC after: 1 week

symlink(7): The ownership of symlinks is used by the system,
in at least three ways, so do not say it is ignored:
* who may delete/rename a symlink in a sticky directory
* who may do lchflags(2)/lchown(2)/lchmod(2)
* whose inode quota is charged

MFC after: 1 week

ln: Allow a trailing slash when creating a link to a directory.

In the 'ln source... directory' synopsis, the basename of each source
determines the name of the created link. Determine this using basename(3)
instead of strrchr(..., '/') which is incorrect if the pathname ends in a
slash.

The patch is somewhat changed to allow for basename(3) implementations that
change the passed pathname, and to fix the -w option's checking also.
The code to compare directory entries only applies to hard links, which
cannot be created to directories using ln.

Example:
ln -s /etc/defaults/ /tmp
This should create a symlink named defaults.

PR: 121568
Submitted by: Ighighi
MFC after: 1 week

ln: Refuse deleting a directory entry by hardlinking it to itself.

Two pathnames refer to the same directory entry iff the directories match
and the final components' names match.

Example: (assuming file1 is an existing file)
ln -f file1 file1
This now fails while leaving file1 intact. It used to delete file1 and then
complain it cannot be linked because it is gone.

With -i, this error is detected before the question is asked.

MFC after: 2 weeks

Allow creating hard links to symlinks using ln(1).

This implements the POSIX.1-2008 -L and -P flags.

The default remains to create hard links to the target of symlinks.

Approved by: re (kib), ed (mentor)

Clean up a bit of confusing language and improve .Nd.

PR: 47818
Reviewed by: keramida

Unbreak last commit to ln for amd64.

Cast string precision to `int'. amd64 systems warn about the
field precision being `long int' if we don't, and pathnames are
normally short enough to fit in an `int'.

Noticed by: pav

Add a -w warning flag to ln(1). When the -w option is enabled,
ln(1) checks to see if the source of a symlink, i.e. the file it
should point to actually exists. The default is the old ln
behavior, that does not check, to avoid surprising people who may
be using ln(1) in scripts or other non-interactive places.

PR: bin/7265
Submitted by: Joel Ray Holveck, detlev!joelh at mail.camalott.com
MFC after: 2 weeks

Express in the usage() and SYNOPSIS that -F depends on -s, and
that -f and -i are exclusive.

Swap "source"/"target" where appropriate, to match documentation.

Add '-F' option which allows to delete existing empty directories, when
creating symbolic links.

PR: bin/92149
Submitted by: Eugene Grosbein <eugen grosbein.pp.ru>

Expand *n't contractions.

Sync program's usage() with manpage's SYNOPSIS.

Add the new standard EXIT STATUS section where appropriate.
Sort standard sections in the (documented) preferred order.

/*- or .\"- or #- to begin license clauses.

Deal with double whitespace.

Mechanically kill hard sentence breaks.

Removed trailing whitespace.

Remove clause 3 from the UCB licenses.

OK'ed by: imp, core

Quiet warnings about copyright[].

s/filesystem/file system/ as discussed on -developers

Claim conformance to 1003.2-1992 instead of 1003.1-2001 due to doubts
raised by Lukas Ertl over symbolic link handling.

PR: 41576
MFC after: 1 week

Fix an easy WARNS.

Consistently use __FBSDID

Check that snprintf() does not truncate the destination pathname when
linking into a directory.

ln(1)'s symbolic link handling conforms to IEEE Std. 1003.1-2001, note
this in the Standards section.

Correctly mark up the final command line arguments with the Ar macro for
the last two synopsis forms.

Reject options, handle "--" end-of-options marker in link(1).

mdoc(7) police: punctuation.

Note that the lutimes(2) and lchflags(2) syscalls also do not follow symlinks.
Remove incorrect examples.

PR: 25016
Submitted by: Martin Kammerhofer, Joshua Goodall

Add lchmod(2) to the list of syscalls that do not follow symbolic links.

Consistancy check s/file system/filesystem/

Reviewed by: brian

Add semicolon to empty default case to silence warning.

Fix warnings inspired by lint, a commercial lint and WARNS=4.

o __P has been reoved
o Old-style K&R declarations have been converted to new C89 style
o register has been removed
o prototype for main() has been removed (gcc3 makes it an error)
o int main(int argc, char *argv[]) is the preferred main definition.
o Attempt to not break style(9) conformance for declarations more than
they already are.

Default to WARNS=2. Binary builds that cannot handle this must explicitly
set WARNS=0.

Reviewed by: mike

mdoc(7) police: s/BSD/.Bx/ where appropriate.

Remove whitespace at EOL.

mdoc(7) police: removed HISTORY info from the .Os call.

WARNS= -> WARNS?=

Submitted by: Mike Barcroft <mike@q9media.com>

Use PATH_MAX in preference to MAXPATHLEN.

Also sort declarations per style(9) (big arrays come last) while I'm
in the area.

Silence WARNS=2 and BDECFLAGS on i386 and alpha

MFC After: 1 week

Fixed a typo.

Put a note that `-h' and `-n' is non-standard and provided only for
compatibility purposes.

Prompted by: ru

Bring in `-h' compatability option and its alias `-n' to match NetBSD and GNU
semantics.

style(9) Reviewed by:
Obtained from: NetBSD

MAN[1-9] -> MAN.

Note that rmdir(2) does not follow symbolic links.

Prepare for mdoc(7)NG.

mdoc(7) police: use the new features of the Nm macro.

Avoid use of direct troff requests in mdoc(7) manual pages.

Fix markup typo

PR: 21084
Submitted by: Gerhard Sittig <Gerhard.Sittig@gmx.net>

Fix style bugs and poor wording introduced in rev 1.12.

Submitted by: bde

Fix style bugs and inconsistencies introduced in rev 1.16.

Submitted by: bde

Don't explicitly declare optarg and optind. These are declared in
unistd.h, which is already included.

Add the -i option, as found in rm(1), which provides an interactive
mode in which the user is prompted for confirmation before an
existing file is replaced.

Submitted by: alex

Remove single-space hard sentence breaks. These degrade the quality
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.

Fix cut'n'paste niggles in previous commit.

Add link(1) and unlink(1) as special cases of ln(1) and rm(1)
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>

Add verbose processing flag.

$Id$ -> $FreeBSD$

Grammatical fixes.

Obtained from: OpenBSD

Reverted some more of rev.1.9 (emphasize that -H != -h).

Revert part of the previous commit. Keep the example that shows how the
"-h" flag is used, but use "chown" in the example instead of "file".

Prompted by: bde

Change description of file(1) following symlinks to the truth (namely,
by default, file(1) does not follow symlinks, the -L flag must be
specified.

PR: docs/8602
Submitted by: Kazuo Horikawa <k-horik@yk.rim.or.jp>
Reviewed by: nik

Correct use of .Nm. Add rcsid.

Updated references to the behaviour of ls(1).

PR: bin/6140
Submitted by: Max Euston

Try again to explain the existence of lchown() and the absence of
lchmod() and lutimes().

Update some text to reflect the fact that symbolic links now have
owner and group attributes.

Cosmetic change in usage string.

Add xref to lchown(2) and symlink(2).
Obtained from: {Net|Open}BSD

compare return value from getopt against -1 rather than EOF, per the final
posix standard on the topic.

Revert $FreeBSD$ to $Id$

Make the long-awaited change from $Id$ to $FreeBSD$

This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.

Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.

-Wall cleaning.

[HISTORY] command appeared in Version 1 AT&T UNIX
Obtained from: A Quarter Century of UNIX, Peter H. Salus, page 41

Nuke the undocumented -F flag, since it doesn't do anything anymore.

It used to allow root to hard-link directories (and screw up programs that
expexted the ".." entry to point to the parent dir)

Use lstat() instead of stat() for checking if the final source file exists,
so that `ln -fs' works when the source is a symlink pointing to a non-
existent file.

Added $Id$

fix ln to accept -f again. Thanks Bruce. Seems that Joe Grosch isn't
quite as safe as I thought. I will have to look much closer on his
patches. Damn.

/home/phk/jg

Fix makefiles for our macros.

This commit was generated by cvs2svn to compensate for changes in r1556,
which included commits to RCS files with non-trunk default branches.