From: Nick Matthews <nick@efni.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] net.eth0
Date: Fri, 21 Mar 2003 21:07:11 -0500 [thread overview]
Message-ID: <20030321210711.10f445ed.nick@efni.com> (raw)
In-Reply-To: <20030322010346.075b4dd9.azarah@gentoo.org>
On Sat, 22 Mar 2003 01:03:46 +0200
Martin Schlemmer <azarah@gentoo.org> wrote:
> On Fri, 21 Mar 2003 16:42:00 +0100 (CET)
> Wout Mertens <wmertens@cisco.com> wrote:
>
> > Well, instead of hard-coding a few ways (ifconfig parameters or dhcp)
> > of bringing up the network interfaces, I propose a modular approach,
> > where a few functions/scripts are defined that can bring up the
> > interface, and you can define which ones you like in what order. To
> > bring up the interface, they will be called in order until one
> > succeeds.
> >
> > On top of that, I propose the same thing, but for events about network
> > interfaces. That way, you can add in dyndns clients, reconfigure
> > applications etc.
> >
> > Configuration is still done through /etc/conf.d/net.
> >
> > I have done a lot of weird stuff with my network scripts over the last
> > few years, and this approach would be able to do all the things I can
> > remember, in a way that can be automated and clean.
> >
>
> Yes, but I wanted a bit more specifics.
>
> > Well, if there are no takers, I think I'll give that approach a whirl
> > and see what happens.
> >
>
> To be honest, my resources networks wise is very limited, and I would
> appreciate it if somebody with enough pcmcia/wireless/dhcp/whatever
> knowledge will take the network bit off my hands.
Well, lets see here, I have a pcmcia setup, with both wireless and wired connections, I use dhcp most of the time, but need to use static ips as well. (My laptop at times needs to be used for static testing purposes on the same lan as an entirely different dhcp network)
I can certainly help test any network script changes.
I need to have a look again as to whats currently going on, and then I might have some ideas and suggestions.
>
> I do have one requirement though: Please keep it sane, and me in
> the loop for at least the initial stuff until we agree that it is
> a workable solution.
>
>
> Regards,
>
> --
>
> Martin Schlemmer
> Gentoo Linux Developer, Desktop/System Team Developer
> Cape Town, South Africa
>
>
> --
> gentoo-dev@gentoo.org mailing list
>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-03-22 2:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 20:46 [gentoo-dev] net.eth0 Frederick Reeve
2003-03-09 5:16 ` Martin Schlemmer
[not found] ` <20030309070831.GB23088@purematrix.com>
2003-03-09 10:02 ` Frederick Reeve
2003-03-09 22:58 ` Joseph Carter
2003-03-17 15:35 ` Wout Mertens
2003-03-18 3:09 ` Joseph Carter
2003-03-18 18:44 ` Martin Schlemmer
[not found] ` <Pine.GSO.4.53.0303191423140.15485@oaktree.cisco.com>
2003-03-21 6:43 ` Martin Schlemmer
2003-03-21 15:42 ` Wout Mertens
2003-03-21 15:44 ` Paul de Vrieze
2003-03-21 23:03 ` Martin Schlemmer
2003-03-22 2:07 ` Nick Matthews [this message]
2003-03-09 10:41 ` Sven Vermeulen
2003-03-09 9:58 ` Frederick Reeve
2003-03-10 6:44 ` Sven Vermeulen
-- strict thread matches above, loose matches on Subject: below --
2003-03-19 17:16 Wout Mertens
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=20030321210711.10f445ed.nick@efni.com \
--to=nick@efni.com \
--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