[2602] in SIPB_Linux_Development
Re: /etc/resolv.conf
daemon@ATHENA.MIT.EDU (Salvatore Valente)
Sat Feb 13 01:26:37 1999
Date: Sat, 13 Feb 1999 01:26:18 -0500 (EST)
To: warlord@MIT.EDU
Cc: linux-dev@MIT.EDU
In-Reply-To: "[2571] in SIPB_Linux_Development"
From: Salvatore Valente <svalente@MIT.EDU>
The current RedHat-Athena install process does not put 127.0.0.1 in
/etc/resolv.conf. I'd like to put /etc/resolv.conf back in the
named-conf package to fix this bug.
Here's all the background info:
The RedHat-Athena install program has been modified with regards to
/etc/resolv.conf in the following ways:
1. The install program was modified so it doesn't create a new
/etc/resolv.conf if an /etc/resolv.conf exists after installing the
packages.
2. The RedHat install program only puts the nameserver used during the
install in /etc/resolv.conf. The Athena install program puts all
three MIT nameservers in. (It does not put 127.0.0.1 in, because that
would break during the install process. It would also break if the
user chooses not to install the named-conf package.)
In RedHat-Athena 4.2, modification (1) worked nicely with the
%postinstall script in named-conf:
cat > resolv.conf <<EOF
domain MIT.EDU
nameserver 127.0.0.1
nameserver 18.70.0.160
nameserver 18.71.0.151
EOF
However, modification (2) was irrelevant to the installed system.
For RedHat-Athena 5.2, it makes sense to replace the %postinstall
script with the /etc/resolv.conf that was installed from the source
tree to /srvd.
So, given all this, does anyone object to putting /etc/resolv.conf
back in the named.conf package? If you do object, you should suggest
a better way to get 127.0.0.1 in /etc/resolv.conf when the named.conf
package is installed.
Have a nice day,
Sal.
