[arch-projects] [initscripts][netcfg] deprecating advanced network functionality from initscripts

[Dave Reisner]

On Tue, Apr 26, 2011 at 12:52:30PM -0500, Dan McGee wrote:
> On Tue, Apr 26, 2011 at 12:40 PM, Tom Gundersen <teg at jklm.no> wrote:
> > Here are some suggestions of what we can do (by order of preference),
> > feedback appreciated:
> >
> > 1) Make sure netcfg support all the usecases that initscripts does,
> > add netcfg to base and remove all network support from initscripts;
> > 2) Similarly, but keep support for one wired interface configured
> > statically (each supported option listed explicitly) or via dhcp (just
> > enough to support a rescue/install scenario); or
> > 3) Something less extreme based on uscases that I have not thought of...
> 
> I'd vote for #2, keeping old timers (and me) happy. It seems like the
> right line to draw so that someone using a "normal" desktop computer
> setup, a VM, a VPS, etc. over Ethernet doesn't need to suddenly dive
> into netcfg. This would eliminate a lot of code still: wi_up,
> bond_up/down, bridge_up/down.
> 
> -Dan

I'll vote for #2 as well. Since this involves some amount of dramatic
change, can I be annoying and harp on my iproute2 patchwork as well?
Seems like it would be an appropriate time to merge, since we're
breaking other things as well.

d