Le Mercredi 8 Décembre 2004 11:11, Benoît Audouard a écrit : > one objective for Mandrakelinux 10.2 is to be FHS compliant > Thierry Vignaud can tell more... > Though, I would have put a ln -s /var/run/ppp/resolv.conf /etc/resolv.conf > instead of a relative path... > And I still do not understand how this can work if there's a LAN (with > DNS) + internet connection :-( MandrakeLinux doesn't use such a link: /etc/resolv.conf is updated by /etc/ppp/ip-up. Eagleconfig, when using pppd: * previous system : - mdk : let ip-up update resolv.conf - other : link /etc/resolv.conf to /etc/ppp/resolv.conf * new system (not perfect but should be better) : - if /etc/ppp/ip-up contains "# ppp temp entry", let ip-up update resolv.conf - else : link /etc/resolv.conf to /etc/ppp/resolv.conf
> > strings $PPPD_BIN | grep resolv.conf
> > Is there any drawback with this method?
> filtering the binary content of a file, looking for strings, is a hacker's
> method
> `pppd --version|gawk '{ print $3 }'` # should give 1.4.3 or greater (I do
> not remember how to compare versions...)
I remember that anyone said resolv.conf path was given when compiling pppd. So
I don't know if comparing versions is a good idea. Until we find a more
reliable solution, I choosed the first one (string ... | grep resolv.conf)
_____
Tux
pgpHGi3SL3lCh.pgp
Description: PGP signature
