All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcus Meissner <Marcus.Meissner@caldera.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Marcus Meissner <Marcus.Meissner@caldera.de>,
	Marcus Meissner <mm@ns.caldera.de>,
	linux-kernel@vger.kernel.org
Subject: Re: ln -s broken on 2.4.5
Date: Thu, 31 May 2001 00:05:05 +0200	[thread overview]
Message-ID: <20010531000505.A30497@caldera.de> (raw)
In-Reply-To: <20010530233005.A27497@caldera.de> <E155DqA-0006g7-00@the-village.bc.nu>
In-Reply-To: <E155DqA-0006g7-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, May 30, 2001 at 10:49:18PM +0100

On Wed, May 30, 2001 at 10:49:18PM +0100, Alan Cox wrote:
> > The problem is only there if you specify a directory for the linked to
> > component.
> > 
> > [marcus@wine /tmp]$ strace -f ln -s fupp/berk xxx
> > execve("/bin/ln", ["ln", "-s", "fupp/berk", "xxx"], [/* 39 vars */]) = 0
> > ... ld stuff ... locale stuff ... 
> 
> bash-2.04$ ln -s foo/frob eep
> bash-2.04$ ls -l eep
> lrwxrwxrwx    1 alan     users           8 May 30 22:19 eep -> foo/frob

*sigh*

I just rebooted and it is no longer reproducable.

Sorry for the confusion caused.

Ciao, Marcus

  reply	other threads:[~2001-05-30 22:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-30 16:40 ln -s broken on 2.4.5 Edsel Adap
2001-05-30 17:13 ` Rasmus B. Hansen
2001-05-30 18:24 ` Alan Cox
2001-05-30 19:23   ` Marcus Meissner
2001-05-30 19:47     ` LA Walsh
2001-05-30 20:08     ` Alan Cox
2001-05-30 21:30       ` Marcus Meissner
2001-05-30 21:42         ` Sergey Kubushin
2001-05-30 21:44         ` Mike Castle
2001-05-30 21:47         ` Rasmus B. Hansen
2001-05-30 21:49         ` Alan Cox
2001-05-30 22:05           ` Marcus Meissner [this message]
2001-05-30 19:42   ` Edsel Adap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010531000505.A30497@caldera.de \
    --to=marcus.meissner@caldera.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm@ns.caldera.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.