Re: ln -s file1 file2 funziona anche con gli eseguibili?
Il 27 giugno 2012 09:07, Paolo Sala <piviul@riminilug.it> ha scritto:
> Ma venendo alla tua domanda anche se entrambi i programmi fanno parte
> dello stesso pacchetto coreutils, link non so cosa faccia ma non è lo
> stesso comando di ln:
> $ ls -l $(which link)
> -rwxr-xr-x 1 root root 22208 28 apr 2010 /usr/bin/link
> $ ls -l $(which ln)
> -rwxr-xr-x 1 root root 41104 28 apr 2010 /bin/ln
@Gandalf:~$ info coreutils 'link invocation'
File: coreutils.info, Node: link invocation, Next: ln invocation,
Up: Special file types
12.1 `link': Make a hard link via the link syscall
==================================================
`link' creates a single hard link at a time. It is a minimalist
interface to the system-provided `link' function. *Note Hard Links:
(libc)Hard Links. It avoids the bells and whistles of the more
commonly-used `ln' command (*note ln invocation::). Synopsis:
link FILENAME LINKNAME
FILENAME must specify an existing file, and LINKNAME must specify a
nonexistent entry in an existing directory. `link' simply calls `link
(FILENAME, LINKNAME)' to create the link.
On a GNU system, this command acts like `ln --directory
--no-target-directory FILENAME LINKNAME'. However, the `--directory'
and `--no-target-directory' options are not specified by POSIX, and the
`link' command is more portable in practice.
If FILENAME is a symbolic link, it is unspecified whether LINKNAME
will be a hard link to the symbolic link or to the target of the
symbolic link. Use `ln -P' or `ln -L' to specify which behavior is
desired.
An exit status of zero indicates success, and a nonzero value
indicates failure.
--
Gollum1
Tesssssoro, dov'é il mio tessssoro...
Reply to: