1 |
On Fri, 21 Mar 2003, Martin Schlemmer wrote: |
2 |
|
3 |
> On Wed, 19 Mar 2003 15:46:37 +0100 (CET) |
4 |
> Wout Mertens <wmertens@×××××.com> wrote: |
5 |
> |
6 |
> > activate_eth0="dhcp static" |
7 |
> > activate_eth1="iwconfig static dhcp leap" |
8 |
> > activate_ppp0="ppp" # Extra parameters in net.ppp0 |
9 |
> > events_eth0="apache" |
10 |
> > events_ppp0="dyndns" |
11 |
> > events_global="wwwoffled chronyd" |
12 |
> > |
13 |
> > What do you think? I think this would be able to take all the things I |
14 |
> > tried to do over the last few years :) |
15 |
> |
16 |
> Err, mind explaining a bit over here ? |
17 |
|
18 |
Well, instead of hard-coding a few ways (ifconfig parameters or dhcp) of |
19 |
bringing up the network interfaces, I propose a modular approach, where a |
20 |
few functions/scripts are defined that can bring up the interface, and you |
21 |
can define which ones you like in what order. To bring up the interface, |
22 |
they will be called in order until one succeeds. |
23 |
|
24 |
On top of that, I propose the same thing, but for events about network |
25 |
interfaces. That way, you can add in dyndns clients, reconfigure |
26 |
applications etc. |
27 |
|
28 |
Configuration is still done through /etc/conf.d/net. |
29 |
|
30 |
I have done a lot of weird stuff with my network scripts over the last few |
31 |
years, and this approach would be able to do all the things I can |
32 |
remember, in a way that can be automated and clean. |
33 |
|
34 |
> > We could start prototyping something in a separate ebuild, |
35 |
> > sys-apps/gentoo-net or something, and when it is stable, merge it back |
36 |
> > in baselayout. |
37 |
> |
38 |
> Could work |
39 |
|
40 |
Well, if there are no takers, I think I'll give that approach a whirl and |
41 |
see what happens. |
42 |
|
43 |
Wout. |
44 |
|
45 |
-- |
46 |
gentoo-dev@g.o mailing list |