At 06:42 PM 1/26/00 -0500, François Pinard wrote:
"Derek J. Balling"
writes: I put a bunch of stuff in boot.local (flushing the route table and rebuilding it), EXPECTING that boot.local would be the last thing to run. Instead I found that my local changes got overridden by /etc/rc.d/route, because that ran LATER.
I currently wholly replace `/sbin/init.d/route' with a script taking care of initialising routes, arp tables and setting maybe one thousand of ipchains rules, and it seems to work well for me, so far.
SuSE surely tries very hard to make so the network is easy to setup in a great variety of situations. Yet, after a certain level of complexity, it becomes a bit unreasonable to expect SuSE to do it all. You might have to take some parts over.
Oh, I agree, but I think that a very few modifications to yast's networking stuff (and by extension the way rc.config is stored/read), could greatly improve its ability to deal with "slightly" odder stuff, like host-routes and ifconfig flags, as well as even (potentially) arp-tables. I wish I knew C, so I could just code a patch to yast to do it. :) D -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/