From: Whit Blauvelt <whit@transpect.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] RTNETLINK answers: File exists
Date: Tue, 27 Nov 2001 01:12:44 +0000 [thread overview]
Message-ID: <marc-lartc-100682374223722@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100679899116747@msgid-missing>
On Mon, Nov 26, 2001 at 01:22:08PM -0500, Whit Blauvelt wrote:
> # ip route del default via 65.84.205.97 dev eth2
....
> # ip route add default via 65.84.205.97 dev eth2
> RTNETLINK answers: File exists
Let me be clear about this: anything that can be deleted, should be able to
be added. The "File exists" message is quite wrong, since no file creation
has been requested - this is about a route. The error message is worthless,
stupid, and just plain wrong.
Has Linus really allowed such nonsense to be integrated with the kernel?
It's a totally cool idea, being able to do Cisco-type stuff with Linux. But
if the implementation is this lame, it shouldn't have been integrated at
all.
Sorry for being pissed off, but please don't contribute anything to Linux
that isn't done consistently and right!
Whit
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-11-27 1:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 18:22 [LARTC] RTNETLINK answers: File exists Whit Blauvelt
2001-11-26 18:50 ` Julian Anastasov
2001-11-26 18:56 ` Greg Scott
2001-11-26 19:18 ` Julian Anastasov
2001-11-27 0:51 ` Whit Blauvelt
2001-11-27 1:01 ` Whit Blauvelt
2001-11-27 1:12 ` Whit Blauvelt [this message]
2001-11-27 10:46 ` Julian Anastasov
2005-06-10 15:07 ` Dariusz Dwornikowski
2005-06-11 2:37 ` gypsy
2005-06-11 9:41 ` Dariusz Dwornikowski
2005-06-11 10:11 ` Thomas Graf
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=marc-lartc-100682374223722@msgid-missing \
--to=whit@transpect.com \
--cc=lartc@vger.kernel.org \
/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.