Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!trwrb!scgvaxd!wlbr!jplgodo!mahendo!elroy!jplopto!earle From: earle@jplopto.uucp (Greg Earle) Newsgroups: comp.dcom.lans Subject: Re: SUN 3.4 problems Message-ID: <4354@elroy.Jpl.Nasa.Gov> Date: Thu, 27-Aug-87 14:33:59 EDT Article-I.D.: elroy.4354 Posted: Thu Aug 27 14:33:59 1987 Date-Received: Sun, 30-Aug-87 06:14:39 EDT References: <1615@briar.Philips.Com> Sender: news@elroy.Jpl.Nasa.Gov Reply-To: earle@jplopto.JPL.NASA.GOV (Greg Earle) Followup-To: poster Organization: Jet Propulsion Laboratory, Pasadena, CA Lines: 59 Keywords: RPC Broadcast ypbind Summary: Wrong Files on the 3.4 Upgrade tapes Some of the files that were supposed to be on the 3.4 upgrade tapes didn't make it. There is a tar file of fixes, available via anonymous FTP from host sesun.JPL.NASA.GOV [128.149.4.18], in pub/3.4-fix.tar. Here is the README file that accompanies it (3.4-fix.README) : -------------------------------------------------------------------------- 3.4-fix.tar: This distribution contains a number of files that were inadvertantly omitted from the SunOS 3.4 distribution tape. All the binaries (except in.rwhod) are ones received directly from Sun and will be incorporated in the next release. This should be considered as a MANDATORY patch to SunOS 3.4 systems. The problems that appear are related to RPC broadcasts. In particular, ypbind will fail if the machine is on a subnet. David Robinson MS 168-522 JPL 4800 Oak Grove Drive, Pasadena CA 91109 (818) 354-3595 (Office) Contents: ./etc/ypbind ./etc/umount ./etc/in.routed ./usr/ucb/rup ./usr/ucb/rusers ./usr/etc/in.rwhod Install by: # /etc/halt > b vmunix -s # mount /usr # cd / # tar xvpf 3.4-fix.tar # /etc/reboot ---------------------------------------------------------------------- David Robinson of Caltech discovered the problem, and talking with Sun discovered the fact that the corrected versions accidentally didn't get on the 3.4 upgrade tapes. Since the network was OK before, it's doubtful that it is bad; however the `ie0: no carrier' messages *are* puzzling since they normally indicate a tap fallen off, or a bad solder connection in a cable connector (if not using vampire taps), etc. Are you running subnets? - Greg Earle Currently moonlighting for Sun Consulting Greg Earle earle@jplopto.JPL.NASA.GOV Sun Consulting earle%jplopto@jpl-elroy.ARPA [aka:] (Freelance - earle%jplopto@elroy.JPL.NASA.GOV write me) ...!cit-vax!elroy!smeagol!jplopto!earle