Date: Mon, 7 Jan 91 09:57:50 EST From: Dwight D. McKay (The Moderator) Reply-To: Suns-at-Home@orchestra.ecn.purdue.edu Subject: Suns-at-Home Digest V4 #1 To: Suns-at-Home-List Suns-at-Home Digest Mon, 7 Jan 91 Volume 4 : Issue 1 Today's Topics: Jaybe Software Connector/cables for SUN-3/60 SCSI help Needed With tape (st) and Boot Errors libcore.a Questions about SLIP. +--------------------------------------------------------------------+ | Submissions: suns-at-home \ @orchestra.ecn.purdue.edu | | Requests: suns-at-home-request > -- or -- | | Archives: suns-at-home-archives / ...rutgers!pur-ee!... | +--------------------------------------------------------------------+ [ I'm finally back from vacation. This digest a few old messages! --ddm ] ---------------------------------------------------------------------- Date: Mon, 10 Dec 90 14:57:09 MST From: bruce%jaybe.UUCP@cs.arizona.edu (Bruce Joseph) Subject: Jaybe Software To: suns-at-home@orchestra.ecn.purdue.edu For those subscribers looking for a low cost, high performance relational database management system, Jaybe Software offers the C Database Management System Toolkit. The Cdb Toolkit provides editors, printout generators, a query language, menu tools, etc. We are a Catalyst vendor. Cdb runs on all Sun platforms including the Sun 2, Sun 3, Sun 4 and Sun 386i running most any Sun OS. Of course we provide complete support for our product. For further information, including a reference list, please contact: Bruce Joseph Jaybe Software (602) 327-2299 ...arizona!jaybe!bruce ...jaybe!bruce@cs.arizona.edu [ You can retreieve price info as well as additional information from the ] [ archive server. Send the line, "send VENDOR Jaybe.Software" in the ] [ *body* of a message to "suns-at-home-archives@orchestra.ecn.purdue.edu".] [ The additional info should be available in a few days. --ddm ] ------------------------------ Date: Mon, 10 Dec 90 9:38:40 EST From: Marcus Leech Subject: Connector/cables for SUN-3/60 SCSI To: suns-at-home@orchestra.ecn.purdue.edu I'm now the proud owner of a SUN-3/60 and a brand-spanking-new Fujitsu 2263SA SCSI drive. I've mounted a SCSI drive in an old PC/XT cabinet and used the supply for the SCSI drive. Is anybody aware of a reasonably-cheap source of cabling arrangments for SUN-3/60-to-third-party drives? I'm thinking that it would be "nice" to have a panel-mounted (RJ71?) connector on the back of the XT-cabinet, and have an cable that maps the 50-pin-D on the back of the SUN-3/60 to RJ71 (50-pin amphenol connector that seems to be a pseudo-standard for SCSI). Anybody else have an opinion? -- ----------------- Marcus Leech, 4Y11 Bell-Northern Research |opinions expressed mleech@bnr.ca P.O. Box 3511, Stn. C |are my own, and not VE3MDL@VE3JF.ON.CAN.NA Ottawa, ON, CANADA |necessarily BNRs ------------------------------ Date: Fri, 4 Jan 1991 19:00:07 -0500 (EST) From: Bill_von_Hagen@transarc.com Subject: help Needed With tape (st) and Boot Errors To: Suns-at-Home@orchestra.ecn.purdue.edu I'm having a lot of problems reading tapes (and therefore booting) my system, and hoped that someone could tell me what's going on, or at least explain the error messages I'm getting. My system is an 8-meg Sun 2/50 attached to a Sun3 (I think) shoebox containing a Toshiba MK 156 disk and a Wangtek 5099EN24 tape drive. The 2/50 passes all of its disgnostics with no problem, yet when I fire up the shoebox and try to boot from tape ("b st()"), the tape drive grinds for a while, but eventually returns the message "st: sense error". The tapes are QIC-11 3.5 boot tapes for a 68010, so I believe that what's on them is correct. I also have another Wangtek drive and SYSGEN board stuffed, frankenstein-fashion, into an old PC drive box. When I shut down the shoebox, hook up the latter, and try to boot, I get the error message "st: error 96A0". Help! HELP!! I can't find anywhere in the standard doc set that explains these messages, and the 2/50 technical docs that I have don't discuss these types of errors. I'd really appreciate any help anyone could give me. Right now I have a lot of useless hardware. How useful it will be when I get it running is debatable, but I'd at least like to get it running!!! Thanks very much! Bill (wvh@transarc.com) ------------------------------ Date: Mon, 17 Dec 90 19:12:21 PST From: teamnet!gpitcher@hp-sdd.sdd.hp.com (Glenn Pitcher) Subject: libcore.a To: suns@sdd.hp.com Does anyone know if the core library that was on at least the Sun 2's and 3's was available on the 386i? I would sure like to get hold of something that would at least give me the same functions or at least close to the same. Thanks, Glenn ------------------------------ Date: Sat, 15 Dec 90 14:20:25 -0600 From: mclay@wilbur.ae.utexas.edu (Robert McLay) Subject: Questions about SLIP. To: suns-at-home@orchestra.ecn.purdue.edu I am now the proud owner of a SLC and 660MB at home. I am trying to implement SLIP (serial line IP) between the SLC and a SUN 4/330 at work (all running sunOS 4.1). I have a pair of telebit T2500's modems to run between the two machines. I am interesting in mainly getting compressed-slip running between the two machines but right now I can't get even slip running. The instructions that come with the slip-4.0.tar (from uunet.uu.net among many other places) is very clear on the modifications to the kernel and the programs to compile in order to get it to work. However it is not clear (at least to me :-) how to actual use the thing. I have read the README's in the distributions and even the rfc's (rfc1055 (SLIP) and rfc1144 (CSLIP)) but it is not very clear. Here is what I've done so far: 1) modified the kernel, re-built it and installed it and rebooted 2) compiled sliplogin, install it with setuid set to root. 3) created a file called /etc/hosts.slip: ________________________________________________________________________ mclay normal 97.83.152.29 97.83.152.135 255.255.0.0 ________________________________________________________________________ 4) then on the machine at home (SLC) I do: slc> tip tb19200 # tip to Telebit T2500 connected atdt1234567 # dial T2500 at work connected to sun4/330 ... sun4/330 login: mclay # login to sun4/330 Password: ... sun4/330> sliplogin # use /etc/hosts.slip ________________________________________________________________________ At this point this window will not respond. In /var/adm/messages (on the 4/330) I get messages telling me that a sliplogin is happening and that slip is coming up. In other windows on the sun4/330 I try doing ping 97.83.152.135 to ping the machine at home (SLC) back from the 4/330. If I do this then I get junk characters in the window on the SLC with the sliplogin command. Note also that the 97.83.152.135 for the slc and the 97.83.152.29 for the 4/330 are fictitious. I was told that they should not be the same as the normal IP addresses but I am not sure why. I assume that I am missing something. Do I need to run sliplogin on both machines? If so, how? Assuming that I do get SLIP and CSLIP running, Has anyone else had to do all the modifications that Pieter H.A. Venemans (sun-at-home vol3 issue 19) had to go through. Also on another front. There are serious complaints against sunOS 4.+ with the streams implementation by Van Jacobson in his note in 12/31/89. Is there a better way to do this? I have seen a slip-4.1-beta from Mark.Andrews@syd.dms.csiro.au but it is not clear at all how to integrate the cslip stuff in it. Also it seems to be a streams based implementation and subject to the same criticism. If someone could tell where to RTFM, I will be very a happy to read the manual if I could only find one. Robert McLay Manager CFDLAB suns ------------------------------ End of Suns-at-Home Digest ******************************