Re: ifplugd, guessnet, ifscheme, netscript, whereami, ... -- what should I use?
OoO Lors de la soirée naissante du jeudi 09 juin 2005, vers 18:58,
Matej Cepl <cepl@surfbest.net> disait:
>> The main problem of those solutions is that they are "interface
>> bound". I mean it does not make sense in most cases to have both eth0
>> and wlan0 up at the same time.
> That's true, but there is not much cost involved with it, is it? Will Linux
> (I am not sure who exactly -- kernel, libc?) remember that some interface
> lead nowhere and so it doesn't try it for some time, or what?
Not sure, but you have also the problems with domain name servers in
/etc/resolv.conf for example. Most users here have problem when
switching from wire to wireless because of duplicate default routes.
--
Don't stop at one bug.
- The Elements of Programming Style (Kernighan & Plaugher)
Reply to:
- References:
- ifplugd, guessnet, ifscheme, netscript, whereami, ... -- what should I use?
- From: Matej Cepl <cepl@surfbest.net>
- Re: ifplugd, guessnet, ifscheme, netscript, whereami, ... -- what should I use?
- From: Enrico Zini <enrico@enricozini.org>
- Re: ifplugd, guessnet, ifscheme, netscript, whereami, ... -- what should I use?
- From: Vincent Bernat <bernat@luffy.cx>
- Re: ifplugd, guessnet, ifscheme, netscript, whereami, ... -- what should I use?
- From: Matej Cepl <cepl@surfbest.net>
- Prev by Date:
unsubscribe
- Next by Date:
Re: ifplugd, guessnet, ifscheme, netscript, whereami, ... -- what should I use?
- Previous by thread:
Re: ifplugd, guessnet, ifscheme, netscript, whereami, ... -- what should I use?
- Next by thread:
Re: ifplugd, guessnet, ifscheme, netscript, whereami, ... -- what should I use?
- Index(es):