.\" $NetBSD: fsu_ln.1,v 1.1 2009/03/23 21:03:57 stacktic Exp $
.\" NetBSD: ln.1,v 1.22 2007/10/29 11:22:59 jnemeth Exp
.\" Copyright (c) 1980, 1990, 1993
.\" The Regents of the University of California. All rights reserved.
.\" This code is derived from software contributed to Berkeley by
.\" the Institute of Electrical and Electronics Engineers, Inc.
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\" @(#)ln.1 8.2 (Berkeley) 12/30/93
.Dd June 17, 2008
.Dt FSU_LN 1
.Nd make links from a file system image through rump
.Op Fl fhinsv
.Ar fstype fsdevice source_file
.Op Ar target_file
.Op Fl fhinsv
.Ar fstype fsdevice source_file ... target_dir
utility creates a new directory entry (linked file) which has the
same modes as the original file on the
file system image contained in
.Ar fsdevice .
It is useful for maintaining multiple copies of a file in many places
at once without using up storage for the
.Dq copies ;
instead, a link
to the original copy.
There are two types of links; hard links and symbolic links.
How a link
to a file is one of the differences between a hard or symbolic link.
The options are as follows:
.Bl -tag -width flag
.It Fl f
Unlink any already existing file, permitting the link to occur.
.It Fl h
is a symbolic link, do not follow it.
This is most useful with the
option, to replace a symlink which may point to a directory.
.It Fl i
to write a prompt to standard error if the target file exists.
If the response from the standard input begins with the character
.Sq Li y
.Sq Li Y ,
then unlink the target file so that the link may occur.
Otherwise, do not attempt the link.
option overrides any previous
.It Fl n
.Fl h ,
for compatibility with other
.It Fl s
Create a symbolic link.
.It Fl v
to be verbose, showing files as they are processed.
A hard link to a file is indistinguishable from the original directory entry;
any changes to a file are effective independent of the name used to reference
Hard links may not normally refer to directories and may not span file systems.
A symbolic link contains the name of the file to
which it is linked.
The referenced file is used when an
.Xr open 2
operation is performed on the link.
.Xr stat 2
on a symbolic link will return the linked-to file; an
.Xr lstat 2
must be done to obtain information about the link.
.Xr readlink 2
call may be used to read the contents of a symbolic link.
Symbolic links may span file systems and may refer to directories.
Given one or two arguments,
creates a link to an existing file
.Ar source_file .
is given, the link has that name;
may also be a directory in which to place the link;
otherwise it is placed in the current directory.
If only the directory is specified, the link will be made
to the last component of
.Ar source_file .
Given more than two arguments,
makes links in
to all the named source files.
The links made will have the same name as the files being linked to.