From: David Ford <david@blue-labs.org>
To: Petr Titera <owl@century.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: issue: deleting one IP alias deletes all
Date: Wed, 24 Oct 2001 02:52:46 -0400 [thread overview]
Message-ID: <3BD6653E.70906@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0110240042570.1210-100000@u.domain.uli> <3BD65188.1060203@blue-labs.org> <02b601c15c53$c02f4990$0800a8c0@century.cz>
I agree that the documentation for 'ip' is sparse or hard to grok.
Learn by example. I have some scripts on http://blue-labs.org/, the
rc.* scripts. These two scripts are my live scripts and cover a lot of
things from simple to advanced.
(comments appreciated for corrections or improvements)
David
Petr Titera wrote:
>>Actually it is quite sane. The tool is not.
>>
>>Switch to 'ip' instead of 'ifconfig', several large distros now include
>>it. Addresses can be added and removed completely indiscriminately on
>>interfaces.
>>
>I'd like to, but there's nothing like documentation with it.
>
>Petr
>
>P.S.: Yes I know about examples in Linux 2.4 routing, but manpage would be
>nicer.
>
next prev parent reply other threads:[~2001-10-24 6:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 1:01 issue: deleting one IP alias deletes all Julian Anastasov
2001-10-24 5:28 ` David Ford
2001-10-24 6:18 ` Petr Titera
2001-10-24 6:52 ` David Ford [this message]
2001-10-24 12:48 ` Wilson
2001-10-25 16:34 ` Matthew G. Marsh
2001-10-24 8:19 ` Julian Anastasov
2001-10-24 14:02 ` Christopher Friesen
2001-10-24 15:34 ` Tim Hockin
2001-10-24 17:14 ` Christopher Friesen
2001-10-24 20:36 ` David Ford
2001-10-24 20:54 ` Tim Hockin
2001-10-27 17:26 ` kuznet
2001-10-25 17:40 ` Matthew G. Marsh
2001-10-25 20:01 ` Tim Hockin
2001-10-25 19:56 ` David S. Miller
2001-10-25 20:29 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2001-10-23 17:54 Tim Hockin
2001-10-24 11:36 ` Kurt Roeckx
2001-10-24 12:00 ` Kurt Roeckx
2001-10-25 16:30 ` Matthew G. Marsh
2001-10-26 19:51 ` Michal Jaegermann
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=3BD6653E.70906@blue-labs.org \
--to=david@blue-labs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=owl@century.cz \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox