From: Matt Thrailkill <xwred1@xwredwing.net>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] IPv6 support in network initscripts
Date: Sat, 31 May 2003 22:07:15 -0700 [thread overview]
Message-ID: <20030531220715.796a169b.xwred1@xwredwing.net> (raw)
In-Reply-To: <20030601032902.GA3769@gonzo.peterjohanson.com>
Why not make the script back out of everything its done? I.e., rather than downing the interface, unset any networking things it has set. Unconfigure the ip, etc.
A super network interface control script would be cool too, something that is kept up to date and understands all of the Linux networking features that may be applicable. Maybe like a single script that by itself is device agnostic (could configure a normal nic or a bridge interface or some other complex, abstract thing (with ipv4 and ipv6 support)) and figures out what it should do based on a plethora of directives in /etc/conf.d/net.
Like right now, I've got a bridge interface on my Gentoo box, but to run it I made a copy of the init.d script and put a couple bridging commands in there. It'd be cleaner if I could just inform it about bridging information in /etc/conf.d/net and the init script would understand and do it.
On Sat, 31 May 2003 23:29:27 -0400
Peter Johanson <latexer@gentoo.org> wrote:
> I really prefer the first method, as it provides much finer grained
> control. I've got a net6.ethX script mostly done, but i wanted to get
> some feedback and opinions before fully implementing. The one major
> sticking point is how to deal with the current "do something or die and
> bring the interface down" situation. This behavior would obviously have
> to change.
>
> -pete
>
>
> --
> Peter Johanson
> <latexer@gentoo.org>
>
--
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-06-01 5:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 3:29 [gentoo-dev] IPv6 support in network initscripts Peter Johanson
2003-06-01 5:07 ` Matt Thrailkill [this message]
2003-06-01 5:56 ` Robin H.Johnson
2003-06-01 6:13 ` Seemant Kulleen
2003-06-01 7:50 ` Matt Thrailkill
2003-06-01 12:49 ` Peter Johanson
2003-06-01 19:52 ` Matt Thrailkill
2003-06-07 4:27 ` Gontran Zepeda
2003-06-13 19:42 ` Martin Schlemmer
2003-06-01 7:37 ` Dan Armak
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=20030531220715.796a169b.xwred1@xwredwing.net \
--to=xwred1@xwredwing.net \
--cc=gentoo-dev@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox