> Because most of these solutions will cause more dialling. We
> don't want a situation where people complain that 2.2 is costing
> them a lot of money because it dials when 2.0 didn't.
When I was running with modular ipv4, I saw relatively few problems
that would make me think existing applications would break.
Sure - its not the same as `things that would cause it to dial' but
perhaps an indication that this might be an option.
> Also, the original dyn_addr hack is already in 2.1, it works
> the problems are theoretical, and you can switch it off.
It's a hack - and an ugly hack IMO. I don't want the code in my
kernel (although, it's not all that much really).
Anyhow - for 2.2.x is must remain, but I think that for 2.3.x maybe
we should `solve' the problem by redefining it as a userspace and
application level problem - not a kernel problem.
-cw
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/