🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.sys.sun
Article #12291

setup(8) problems during remote installation of Sun OS 3.5

#12291
From: John Sun
Date: Wed, 26 Apr 1989 07:43
27 lines
1647 bytes
Back in Oct. 88, I read some postings about problems with running setup(8)
with class B networks when doing a remote installation of Sun OS 3.5.
Since I am having problems with setup(8) and have a class B network, I was
wondering if anyone could tell me what they did to solve this problem?

As suggested in Oct., I configured the tape server to make tapeless client
a boot client, booted the tapeless client in single user mode, and then
used dd(1) to copy over the miniroot.  I was able to run setup(8) but I
got complaints such as "Unable to make contact with 1/4" Tape Drive".  I
tried to fake out setup(8) by using 128.109.40961 instead of 128.109.160.1
(40961 = 256*160 + 1) for the tapeless client's host address but that
didn't seem to work.  Am I doing this right?  Is there some other trick
that you have to play on setup(8)?

I also get the following error on the tapeless client whenever I try to
execute setup(8), rsh, or rlogin:

	ioctl: Operation not supported on socket
	Where are you?

What does this message mean?

Any help or advice is greatly appreciated!


					John Sun
					sunj@dopey.cs.unc.edu
Technical Details
Message-ID: <7719@thorin.cs.unc.edu>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!uw-beaver!rice!sun-spots-request
From: sunj@unc.cs.unc.edu (John Sun)
Newsgroups: comp.sys.sun
Subject: setup(8) problems during remote installation of Sun OS 3.5
Keywords: SunOS
Message-ID: <7719@thorin.cs.unc.edu>
Date: 26 Apr 89 07:43:50 GMT
Sender: usenet@rice.edu
Organization: Sun-Spots
Lines: 27
Approved: Sun-Spots@rice.edu
Original-Date: 12 Apr 89 14:15:41 GMT
X-Sun-Spots-Digest: Volume 7, Issue 254, message 11 of 12