Path: utzoo!attcan!uunet!husc6!rice!sun-spots-request From: apctrc!cra2!zjat02@uunet.uu.net (Jon A. Tankersley) Newsgroups: comp.sys.sun Subject: Re: Help with 4.0 upgrade on Sun 3/260 Keywords: SunOS Message-ID: <853@apctrc.UUCP> Date: 16 May 89 17:59:34 GMT References: <1977@trantor.harris-atd.com> Sender: usenet@rice.edu Organization: Amoco Production Company, Tulsa Research Center Lines: 33 Approved: Sun-Spots@rice.edu Original-Date: 10 May 89 21:40:09 GMT X-Sun-Spots-Digest: Volume 7, Issue 288, message 3 of 11 The problem is not that SunOS 4.x expects a Sun monitor, but rather there are some beta-test errors still in the 4.0 FCS tapes (Boy was I pissed when I found them...... Should never have survived Beta testing that one). Before going into suninstall do the following setenv TERM vt100 set noglob eval `tset -s $TERM` unset noglob This will correctly set the environment. Problem also occurs if you are trying to install software on a heterogenous server at a later date than the suninstall. Other problems with 4.0 FCS - top of the head response.... netmask + doesn't have the hostname field in rc.local. rc scripts don't handle setting netmasks on ie1 for gateway systems: rc.single doesn't have hostname set properly on ifconfig for ie1. rc.single expects hostname to be host-gw but that fact isn't commented ANYWHERE I read. host-gw must exist in /etc/hosts. in.named is not run before mount -at nfs. Can cause problems if the hosts requested are not in /etc/hosts but are in the named database. syslog.conf bug with define(LOGHOST, 1) for loghost systems. yp problems with named. (separate patches available). -tank- #include /* nobody knows the trouble I .... */ tank@apctrc.trc.amoco.com ..!uunet!apctrc!tank