Sun-Spots-Request@RICE.EDU (William LeFebvre) (08/04/88)
SUN-SPOTS DIGEST Monday, 1 August 1988 Volume 6 : Issue 161 Today's Topics: Re: Sun OS Re: SunOS source licenses (academic) Re: Level 2 interrupt problems (for SunIPC) SUN-monitor tips (Mfd by 'Moniterm') Problems with Fujitsu M244X tape drive Problem with lockd and statd on 4.0. minor problem logging in to Suns via DNI gcc question Sun OS 4.0 Source Distributions? sunlink/DNA & printers? Microsoft Windows and the 386i? troff to postscript? Public Domain Franz Lisp on SunOS 4.0? Wanted: Third-party disk info for Sun 3/60 Send contributions to: sun-spots@rice.edu Send subscription add/delete requests to: sun-spots-request@rice.edu Bitnet readers can subscribe directly with the CMS command: TELL LISTSERV AT RICE SUBSCRIBE SUNSPOTS My Full Name Recent backissues are available via anonymous FTP from "titan.rice.edu". For volume X, issue Y, "get sun-spots/vXnY". They are also accessible through the archive server: mail the request "send sun-spots vXnY" to "archive-server@rice.edu" or mail the word "help" to the same address for more information. ---------------------------------------------------------------------- Date: Wed, 20 Jul 88 15:36:16 PDT From: cire@clash.cisco.com Subject: Re: Sun OS > From: doug@icase.arpa (Doug Peterson) > > It strikes me that the time is near for such individuals to converge > and produce the Berkeley equivalent of an OS for a distributed > computing system.... This is exactly one of the reasons that Stallman is doing GNU. -c cire|eric Eric B. Decker cire@clash.cisco.com [[ And don't forget CMU's "mach" project: a distributed Unix, as I recall. Is GNU going to be built on a message passing kernel (a *true* kernel as opposed to that thing in Unix graciously termed "the kernel") a la "V"? I understand that that is the current trend in distributed OS research. --wnl ]] ------------------------------ Date: Wed, 20 Jul 88 18:01:05 +0100 From: William Armitage <wja%computer-science.nottingham.ac.uk@nss.cs.ucl.ac.uk> Subject: Re: SunOS source licenses (academic) > From: "P. Ashton" <paul@cantuar.uucp> > > We have been in the process of attempting to get a source license > (academic-type) for Sun OS for some time now, but things have been > progressing very slowly... We found things rather slow in Europe too. We currently have Sun 3.4 sources. It proved sufficient to have a AT&T System 5 Release 2 license with at least one of the suns sited on the license. It took sun 6 months from order date for Sun to decided we needed the sun cpu on the license. It took another 6 months for AT&T to upgrade one of the cpu's on our license to a Sun and another 6 months for sun to ship the goodies. One year later we still don't have the compleated licenses returned. I have just investigated 4.0. It seems we need an AT&T System 5 Release 3 license to get this. Gloom!. AT+T have just sent us details of 3.2 but it will probably take ages to get this through. We could still be running 3.4 with selected parts of 4.3tahoe this time next year!. William. PS. Sun have also not returned our compleated NFS source license either. ------------------------------ Date: 21 Jul 88 04:17:56 GMT From: tekbspa!tss!joe@uunet.uu.net (Joe Angelo) Subject: Re: Level 2 interrupt problems (for SunIPC) If you are seeing "Level X interrupt" when ever you access your IPC board, or any board, that's a good inidication that something has gone amuck on the bus. Chances are you forgot to remove BUS-GRANT and INTERRUPT-ACK daisy chain jumpers on the VME BUS back panel, PXX03 and PXX04, respectively. Generally, any card cage slot which is either empty or contains a memory board during the card cage configuration process must have PXX03 and PXX04 installed. Ofcourse, that's the general rule stated in the VME bus techy guide. I've found that almost any direct-VME board (ie: no multi-bus to vme adapter) from Sun does require these jumpers installed; surely, there are execptions. One exception is this: The IPC board doesn't bridge BUS-GRANT, so PXX03 should always be installed. Another exception: The IPC board may or may not pass INTERRUPT-ACK (that's not true, but that's what the results look like...) so PXX04 may or may not need to be installed. Normally, PX004 for a single IPC board installation should be installed. HOWEVER, if you are placing the IPC board in a slot that's not recommended by Sun, then you'll need to remove PXX04. For multi-IPC board installations, you'll have to remove PXX04 for each board. When I think about it, you shouldn't be getting a Level2 int, instead, I think a Level4 would occure. What I'd do is: - Try removing PXX04 and rebooting, then see what happens. (Electrically: it's safe to remove the jumpers with everything up and runner. Logically: strange things can happen.) - You could also try inserting the IPC board in a recommended slot (3/280 = 7,8,9,10,11). If the above doesn't work, I'd assume your board is bad or that perhaps the INT level isn't set properly -- I don't recall if the IPC board has VME INT level dips (it does have vme-address dips). -- About your subnetting problem -- me too! Subnetting works in one direction (ie: running PCTOOL from a subnetted machine) but not the other way around (ie: mount a dir on the PC from a subnetted machine... or using telnet) Sigh -- We've never needed subnetting abilities (from the IPC) until you mentioned it! Soooo, if you find anything out, please Cc: me ;-) Hope this helps, Joe Angelo -- Senior Systems Engineer/Systems Manager at Teknekron Software Systems, Palo Alto 415-325-1025 uunet!tekbspa!joe -OR- tekbspa!joe@uunet.uu.net ------------------------------ Date: Thu, 21 Jul 88 11:23:11 CDT From: gene@uicsl.csl.uiuc.edu (Gene Gardner) Subject: SUN-monitor tips (Mfd by 'Moniterm') This info is probably too "hardware-ish" for readers of this net, but if you happen to be reading this on a SUN-monitor manufactured by "Moniterm" (as identified by a long black Brightness shaft on the rear..also a plastic slide- cover over the fuse) which has a dim display and poor clarity, you may be in- clined to pass the info along to your technical department. We don't have a large number of units by this mfr., but have had several develop this symptom, so that it would appear to be a failure-trend. The problem is caused by the CRT (Picture-tube) heater voltage dropping to only about 4.5 volts. On the P-C board on the left-side (as you face the screen) there is a 6-volt regulator (MC-7806) which supplies the CRT heater voltage. The problem is the 220uf electrolytic (C-26 if you have a schematic) which connects from the "input" pin of the MC-7806, to ground. (The center pin of MC-7806 also connects to ground.) This capacitor opens up but you don't need to remove it....simply tack-solder a 150uf-15v "tantulum" on the opposite side of the P-C board. BE SURE and observe polarity. As arbitrary precaution, I also shunted the neighboring identical 220uf which performs a similar function....it is the other polarity, such that its negative connects to test-hole "k" (C-30 if you have schematic)... i.e. shunted a 150uf-15volt tantulum. BUT in addition to the above, I also took the liberty of making a small design change: Most CRT's are rated at 6.3 volts on the heater, and the present 6volts seems a little stingy, so I snipped the center lead of the MC-7806 and inserted a 1N4003 silicon diode instead. BE SURE to put the Anode to the center-pin of the MC-7806, and the Cathode to ground. ALSO, since the case of the MC-7806 is also bolted to ground, you will need to insulate it from ground with an appropriate heat-conducting insulator. This "bootstraps" the regulated 6vdc up to 6.6vdc at the output, and gives a very noticeable improvement in screen-brightness...i.e. they very well may be returned to as bright as when new. WARNING, the technician should not be careless when installing the diode...if a poor connection comes loose, it might result in enough excess heater-voltage to burn out the CRT! ------------------------------ Date: Thu, 21 Jul 88 11:36 EDT From: Neil Bodick <Bodick@cis.upenn.edu> Subject: Problems with Fujitsu M244X tape drive My co-worker is having the following difficulty. We have a 3/160C, a Fujitsu M2361A disk, and a Fujitsu M244X tape drive with cache, running SunOS 4.0 Release. Whenever I try to write a file from the local disk to the local tape I get the following errors: xt0:lost interrupt xt0:hard error bn =0 er=4 xt0:stray interupt xt0:bad command synchronization xt0:hard interupt and dump reports that there was a write error. I have been able to read files from the local tape drive to the local disk, and have been able to use the tape drive to write files over a network connection from a remote disk. Sometimes I can get away with writting a short file, but the drive is totally useless for doing backups or tars from the local disk. The controllers for these devices, a Xylogics 451 and Xylogics 472, are in slots 6 and 7. All jumpers on these boards are set as per Xylogics' specifications, and the config files have been properly modified to reflect the state of the hardware. Ideas anyone? Andre Marquis bodikc@cis.upenn.edu ------------------------------ Date: Thu, 21 Jul 88 14:22:48 EST From: munnari!lupus.cc.deakin.oz.au!craig@uunet.uu.net (Craig Bishop) Subject: Problem with lockd and statd on 4.0. Here is a problem description I sent to our sun support here in Australia, so far not much has happened can anyone help with this problem. Hardware: Sun 4/110, SunOS 4.0, 8 MBytes, Diskless. Server: Sun 3/260, SunOS 4.0, 8 Mbytes. Description: The 4/110 is used as the Applications Development machine in Deakin University Computing Services. The majority of develepment the applications team involves itself in is Unify and Accell database work. The problem is that Unify routines which attempt to access any database hang. The following messages appear on the console of the Server when ever a unify program hangs. RPC: unable to send. rpc.lockd unable to contact local statd. req discard due status monitor problem. Attempts to kill and restart the lockd or the statd or both has no effect on the problem. Rebooting the client has no effect. However whenever the problem exists the the shutdown procedure produces the following messages on every shutdown. Portmapper not responding; still trying. Portmapper not responding; still trying. CAUTION: some process(es) wouldn't die. There are two of the portmapper lines per hung unify job. During attempts to get the client up and working properly with Unify and Accell, the following message has appeared. 3 not supported in nlm_call. This may not be associated but the problem did not occur until we tried to mount all our filesystems on our server and clients with option "grpid" set. But since then the problem has occured in both environments. The only way I have been able to get the 4/110 client up and working properly since then has been to kill and restart the lockd and statd on the server *while the client is running* and then reboot the client. Note also that we run unify and accell on several Sun 3/60's running SunOS 4.0 served by the same server without any difficulties under either directory scheme. The version of unify that we are using is 1.4. compiled for SunOS 3.2 for the Sun 4 and SunOS 3.4 for the Sun 3's. Craig Bishop ARPA: craig%lupus.deakin.cc.oz.au@uunet.uu.net UUCP: ...!uunet!munnari!lupus.deakin.cc.oz!craig ------------------------------ Date: 21 Jul 88 16:11:54 GMT From: pyramid!leadsv!laic!root@decwrl.dec.com (Operator) Subject: minor problem logging in to Suns via DNI Whenever I log into my Suns from a VMS account via Sunlink/DNI, the rows and cols in stty are often set to a wierd size (0, 34, are common for rows). Even though I do a tset for a vt100, the stty settings are stilled messed up. Does anyone know any way to fix this? As a side, note, when I log in this way, the type of terminal the .login sees is "su"! So taking one of the template tset lines in the .login and changing "dumb" to "su" works great. [[ These values are "left over" from the last person that used the pty. If you want the default values (that is, those specified in termcap), enter the command "stty columns 0 rows 0". --wnl ]] ------------------------------ Date: Thu, 21 Jul 88 11:10:50 -0400 From: Henry B.J. Krempel <krempel@pacrat.npac.syr.edu> Subject: gcc question Is it true that you still can't use gcc to compile a kernel? Henry B. J. Krempel <krempel@pacrat.npac.syr.edu> Northeast Parallel Architectures Center (NPAC) Syracuse University 250 Machinery Hall Syracuse, N.Y. 13244 ------------------------------ Date: Wed, 20 Jul 88 09:34:43 PDT From: jonab@cam.unisys.com (Jonathan P. Biggar) Subject: Sun OS 4.0 Source Distributions? Has anyone out there received their Sun OS 4.0 Source Distribution yet? Jon Biggar jonab@cam.unisys.com ------------------------------ Date: 20 Jul 88 22:51:15 GMT From: decwrl!pyramid!comdesign!pst@ucbvax.berkeley.edu (Paul Traina) Subject: sunlink/DNA & printers? We have sunlink/dna on our sun's (DECnet) and DECnet on our vaxen. I thought I once saw a way to copy files from the vax to a device on the suns (if the device was supported by a spooler). Is this the case? We'd like users to be able to copy a file to a printer owned by the Sun, e.g. copy file.txt canary::"/dev/ttyb" or copy file.txt canary::dev:ttyb How is this supposed to work? Paul Traina - {uunet|pyramid}!comdesign!pst - comdesign!pst@pyramid.com ------------------------------ Date: Wed, 20 Jul 88 13:19:53 EDT From: gfr%wolfgang@gateway.mitre.org (Glenn Roberts) Subject: Microsoft Windows and the 386i? I am in the process of trying to wean some of my group members from their PC's (I plan to give 3 of them 386i's). The 386i's will help with work that will reside on our 4/260 (programming and simulation work), but my users make extensive use of Excel, Microsoft's spreadsheet/graphics program that runs under Microsoft Windows. Since the only color emulation provided with the 386i is CGA (and in a very small window at that!), I'm concerned that this important capability will be essentially lost when we move to the 386i's. Does anyone know if Sun (or someone else) has plans to write a Microsoft Windows driver for the 386i's 1152x900 color screen? This would be great! ... and seems to me to be quite doable. If not, are there other solutions I should be looking at? (I suppose I could buy a VGA card and monitor and sit it beside the Sun, but that seems like a hardware solution to a software problem!) Glenn Roberts, MITRE Corp., McLean VA (703)-883-6820 gfr%wolfgang@gateway.mitre.org ------------------------------ Date: 21 Jul 88 14:24:21 GMT From: mkkam@wael.cs.uh.edu (Francis Kam) Subject: troff to postscript? Is there any PD troff to postscript filter out there that makes use of SunOS 4.0 troff's support of postscript printers? At first I thought that this version of troff will output in postscript directly. Thank you for any information. PGH 550 Francis Kam Computer Science Department Internet: mkkam@sun1.cs.uh.edu University of Houston CSNET: mkkam@houston.csnet 4800 Calhoun Phone: (713)749-1748 Houston, TX 77004. ------------------------------ Date: Thu, 21 Jul 88 16:57:46 EST From: munnari!lupus.cc.deakin.oz.au!craig@uunet.uu.net (Craig Bishop) Subject: Public Domain Franz Lisp on SunOS 4.0? Has anyone hacked this to work? Craig Bishop ARPA: craig%lupus.deakin.cc.oz.au@uunet.uu.net UUCP: ...!uunet!munnari!lupus.deakin.cc.oz!craig ------------------------------ Date: Thu, 21 Jul 88 13:49:11 EDT From: adam@arclight.tn.cornell.edu (Adam W. Feigin) Subject: Wanted: Third-party disk info for Sun 3/60 I remember there being a flurry of requests for info about 3rd-party hard disks for Sun3/(5,6)0 awhile back. I didn't have Sun then, so I passed them by. Now I find myself looking for another SCSI disk for our 3/60, and would appreciate a summary of information regarding 3rd-party SCSI disks for the Sun3/60. I'd appreciate if someone would send it to me if they've archived it, or point me to where I might obtain this info. Thanx in Advance. Adam W. Feigin Graphics Workstation Consultant Cornell National Supercomputer Facility Internet: feigin@tcgould.tn.cornell.edu UUCP: {allegra,decvax,rochester,uw-beaver}!cornell!batcomputer!feigin BITNET: feigin@crnlthry ------------------------------ End of SUN-Spots Digest ***********************