[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080125192026.e667f396.akpm@linux-foundation.org>
Date: Fri, 25 Jan 2008 19:20:26 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Jarek Poplawski <jarkao2@...il.com>
Cc: netdev@...r.kernel.org, joonwpark81@...il.com,
bugme-daemon@...zilla.kernel.org, schwab@...e.de
Subject: Re: [Bugme-new] [Bug 9816] New: cannot replace route
> On Sat, 26 Jan 2008 00:11:57 +0100 Jarek Poplawski <jarkao2@...il.com> wrote:
> Andrew Morton wrote, On 01/25/2008 11:26 PM:
>
> >> On Fri, 25 Jan 2008 13:23:49 -0800 (PST) bugme-daemon@...zilla.kernel.org wrote:
> >> http://bugzilla.kernel.org/show_bug.cgi?id=9816
>
> ...
>
> > I'd agree with Andrea: replacing a route with itself a) used to work and b)
> > should still work (surely)?
>
> ...on the other hand:
>
> $ touch file1
> $ cp file1 file1
> cp: `file1' and `file1' are the same file
> $ mv file1 file1
> mv: `file1' and `file1' are the same file
>
> and: 'everything' in 'linux' is file...
>
> ergo: route cannot replace with itself!
>
That's not a very good analogy - the source is a kernel object. A better
example would be:
linux-2.6.24-rc8:
echo foo > /tmp/1
echo bar > /tmp/2
echo foo > /tmp/1
linux-2.6.24:
echo foo > /tmp/1
echo bar > /tmp/2
echo foo > /tmp/1
sh: cannot write /tmp/1: Inalid argument
But whatever. It used to work. People's scripts will break. Regression.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists