MultiProtocol per interface support (was Re: LFS-6.0 printprocess)
conathan at conet.dyndns.org
Fri Jul 9 12:37:03 PDT 2004
> On Fri, Jul 09, 2004 at 09:27:05AM -0500, DJ Lucas wrote:
>> Now I did mention the possibility of it being considered bloat ("a bit
>> overkill for simple setups"), but don't see it as such.
> Ah, OK. So you were thinking that the entire idea of >1 service per
> interface might be considered bloat, then? Or not?
> I can see that argument, I guess, but if somebody really doesn't like
> it, they can just keep their current ifconfig file. Nothing will change
> (other than ifup/down will perform one extra check) as far as execution
> time, only the amount of code in the ifup/down scripts. And even that's
> not horrible; it shouldn't be much more than 10-15 lines. For the
> people that need it, I can see how it'd be a big help.
> Thinking about this a bit more, we could add something else also -- a
> variable that gets set somewhere to indicate that we should *stop*
> processing scripts when one succeeds (instead of processing all of them
> always). That way, the user can set it up so that DHCP is the "primary"
> service, but they can fall back to a static IP if DHCP fails (for
> example, because there aren't any DHCP servers up). Sound useful, or
Alright, I have started recoding the directory based networking stuff.
(Well, not committed, but *shrug*)
Should I also yank out all the compatibility at this time? [This will all
have to be tested before LFS 6.0, if we add it...]
More information about the lfs-dev