Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!spool.mu.edu!sol.ctr.columbia.edu!howland.reston.ans.net!Germany.EU.net!EU.net!ieunet!news.ieunet.ie!jkh
From: jkh@whisker.hubbard.ie (Jordan K. Hubbard)
Newsgroups: comp.os.386bsd.questions
Subject: Re: changing 2.0 behavior
Date: 02 Dec 1994 20:18:48 GMT
Organization: Jordan Hubbard
Lines: 23
Message-ID: <JKH.94Dec2201848@whisker.hubbard.ie>
References: <D05wFw.v2@murdoch.acc.Virginia.EDU> <3bmetj$6be@sol.ctr.columbia.edu>
NNTP-Posting-Host: whisker.hubbard.ie
In-reply-to: wpaul@ctr.columbia.edu's message of 2 Dec 1994 06:30:11 GMT
In article <3bmetj$6be@sol.ctr.columbia.edu> wpaul@ctr.columbia.edu (Bill Paul) writes:
Whoa... er, wait. You mean to say the installation created /etc/resolve.conf
instead of resolv.conf? Hurm... this bug must have been introduced recently:
when I did my installation, which was a day or so after 2.0-RELEASE first
hit the net, the install script created resolv.conf correctly (it botched
almost everything else, but resolv.conf it did right ;). Somebody must
have violated the "it's not broken, don't fix it" rule. Okay Jordan:
what's your excuse this time? :)
Not me, boss!
jkh@whisker-> cd /usr/src/release/
jkh@whisker-> grep resolv *
netinst.sh: echo "domain ${DOMAIN}" > ${ETC}/resolv.conf
netinst.sh: echo "nameserver ${NAMESERVER}" >> ${ETC}/resolv.conf
I think this was pilot error on the user's part, somehow. Of all the
things I've broken so far, this isn't one of them! :-)
Jordan
--
Jordan K. Hubbard FreeBSD core team Clams are your friends