Le mercredi 29 décembre 2004 à 17:29 +0100, Tux a écrit :
> 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
that's a workaround : it's added at the end of the file, when all
previous updates are kept (I may end up with new DNS not taken into
account as they are 17th in the list with all previous update when only
3 first DNS are taken into accout)
> - other : link /etc/resolv.conf to /etc/ppp/resolv.conf
that's unacceptable : in case I have a LAN my first DNS should be kept
as first, then my local DNS (in case my server is a proxy), afterwards
other DNS (either local or internet or other : 3 DNS being the max ;-) )
> * new system (not perfect but should be better) :
> - if /etc/ppp/ip-up contains "# ppp temp entry", let ip-up update resolv.conf
at the end or beginning or just after first DNS (preferred) ?
> - else : link /etc/resolv.conf to /etc/ppp/resolv.conf
unacceptable at any condition :
- does not take into account static connection,
- wrongly suppose that pppd is used when I may have a LAN or a
DHCP/static connection
/etc/resolv.conf is taken into account immediately when a DNS request is
made : should reflect the available connection, should they be local
(LAN) or to internet (addition to LAN) via pppd, dhcp/static. That's the
reason why adding DNS dynamically (with the limit of 3) is the proper
way to make it... avoiding to add it at the end (after 3 first DNS when
they may have changed...)
> > > 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)
what a pity it has been implemented this way :-(
pppd --path-config-resolv (or equivalent) may have given the same ?
perhaps in 1.4.4 ? where's the bugzilla to provide enhancements ?
"strings pppd" is not a viable solution, in any case (I do not know any
reason why I should have to explain the reason why, anyway just ask).
@++
Ben'. aka baud123
Les femmes sont tellement menteuses, qu'on ne peut meme pas croire le
contraire de ce qu'elles disent. Georges Courteline.
