-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 3/16/2005 1:53 AM:
>>$ touch a
>>$ ln -s a b
>>$ ln b c # Bug: c should be a hard link to a, not b
>>$ ls -l a b c
>>-rw-r--r-- 1 eblake None 0 Mar 15 19:04 a
>>lrwxrwxrwx 2 eblake None 1 Mar 15 19:04 b -> a
>>lrwxrwx
Eric Blake <[EMAIL PROTECTED]> writes:
> $ touch a
> $ ln -s a b
> $ ln b c # Bug: c should be a hard link to a, not b
> $ ls -l a b c
> -rw-r--r-- 1 eblake None 0 Mar 15 19:04 a
> lrwxrwxrwx 2 eblake None 1 Mar 15 19:04 b -> a
> lrwxrwxrwx 2 eblake None 1 Mar 15 19:04 c -> a
I agree that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Jim Meyering on 3/15/2005 10:35 AM:
>
> But the actual referent (as opposed to the symlink value) may be
> another symlink, which may point to another, etc. The final
> non-symlink value -- assuming there is one -- is the referent.
> It'
Hi Bob,
[EMAIL PROTECTED] (Bob Proulx) wrote:
> Jim Meyering wrote:
>> Is it worth it to make cp manually follow a sequence of symlinks
>> when given both -L and --link?
>
> That would certainly be a nice capability.
>
> If it is not worth it could that case be made an invalid case? That
> way th
Jim Meyering wrote:
> Is it worth it to make cp manually follow a sequence of symlinks
> when given both -L and --link?
That would certainly be a nice capability.
If it is not worth it could that case be made an invalid case? That
way there is no doubt. Because I agree that I would not have exp
Tim Waugh <[EMAIL PROTECTED]> wrote:
> On Tue, Mar 15, 2005 at 04:38:03PM +0100, Jim Meyering wrote:
...
>> Thanks for the report.
>> I suppose this is a documentation bug, since
>> making hard links to symlinks is not portable.
>> I suppose -L and -l should mention that when they are used
>> toget
On Tue, Mar 15, 2005 at 04:38:03PM +0100, Jim Meyering wrote:
> Tim Waugh <[EMAIL PROTECTED]> wrote:
> > coreutils-5.2.1:
> >
> > $ mkdir /tmp/foo
> > $ cp -lL /lib/libc.so.6 /tmp/foo
> > $ ls -l /tmp/foo
> > total 4
> > lrwxrwxrwx 2 root root 13 Mar 8 10:59 libc.so.6 -> libc-2.3.4.so
> >
> > Th
Tim Waugh <[EMAIL PROTECTED]> wrote:
> coreutils-5.2.1:
>
> $ mkdir /tmp/foo
> $ cp -lL /lib/libc.so.6 /tmp/foo
> $ ls -l /tmp/foo
> total 4
> lrwxrwxrwx 2 root root 13 Mar 8 10:59 libc.so.6 -> libc-2.3.4.so
>
> The man page says that -L always dereferences symbolic links, but when
> used in conj
coreutils-5.2.1:
$ mkdir /tmp/foo
$ cp -lL /lib/libc.so.6 /tmp/foo
$ ls -l /tmp/foo
total 4
lrwxrwxrwx 2 root root 13 Mar 8 10:59 libc.so.6 -> libc-2.3.4.so
The man page says that -L always dereferences symbolic links, but when
used in conjuction with -l (link files instead of copying) this is
