Sun-Spots Digest, v6n278
William LeFebvre
Sun-Spots-Request at Rice.edu
Mon Oct 31 08:01:00 AEST 1988
SUN-SPOTS DIGEST Sunday, 30 October 1988 Volume 6 : Issue 278
Today's Topics:
Re: C/A/T troff to ditroff
Re: PostScript printers for Suns
Re: TTY Windows in Sunview
Re: Large screen display for SUN video output
Re: Using Return-Path: for replies
SunOS Source
top10 under SUN-OS 4.0?
Testing sendmail?
Problem with PANIC: free
Problems with dump on 4.0
Problems with telnet pc-nfs 3.0
Looking for troff previewer for Sun's
Send contributions to: sun-spots at rice.edu
Send subscription add/delete requests to: sun-spots-request at 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 at rice.edu" or mail the word "help" to the same address
for more information.
----------------------------------------------------------------------
Date: Mon, 24 Oct 88 08:14:19 CDT
From: apctrc!drd!mark at uunet.uu.net (Mark Lawrence)
Subject: Re: C/A/T troff to ditroff
Thallata sells a cat2dit filter as part of their devps package. There are
many of us folks who would like to use the USENET archive package TPSCRIPT
but are stuck with troff output. Greg, you might consider posting your
filter to comp.sources.unix as the requisite companion piece to TPSCRIPT.
Mark
tulsun!drd!mark at Sun.COM
DRD Corporation mlawrence at jarsun1.ZONE1.COM
(918)743-3013 drd!mark at apctrc.UU.NET
okstate!romed!drd!mark at rutgers.EDU
------------------------------
Date: Mon, 24 Oct 88 08:24:51 CDT
From: apctrc!drd!mark at uunet.uu.net (Mark Lawrence)
Subject: Re: PostScript printers for Suns
I had a doozy of a time getting it installed, but once installed ....
NEC LC-890 Silent Writer
two hoppers (each holds half a ream or so)
Serial, parallel and Appletalk interfacing
3 MB of memory
35 resident fonts
HP Laserjet & Diablo emulation modes
~US$4900
Turns out that the serial port on the printer returns a signal level that
the Sun serial port won't register. Implication, XON/XOFF flow control
doesn't work. Solution - go buy a serial to parallel convertor/buffer box
at a PC store (~US$100) which speaks XON/XOFF to the Sun in acceptable
signal levels and provides a parallel connection to the printer. Works
Fine.
Mark
tulsun!drd!mark at Sun.COM
DRD Corporation mlawrence at jarsun1.ZONE1.COM
(918)743-3013 drd!mark at apctrc.UU.NET
okstate!romed!drd!mark at rutgers.EDU
------------------------------
Date: Tue, 25 Oct 88 07:44:56 EDT
From: Chuck Musciano <chuck at trantor.harris-atd.com>
Subject: Re: TTY Windows in Sunview
Page 180, SunView Programmer's Guide, 15 October 1986, in bold type, no
less:
You can only have one tty subwindow per process.
A subwindow requires a number of file descriptors, and a TTY window
requires a few more, since it handles stdin, stdout, and stderr of the
enclosed tty process. I would guess that a TTY window uses five
descriptors. I would also guess that the TTY is not cleaned up correctly
on exit, and those descriptors are not reclaimed until the whole
application terminates.
Chuck Musciano
------------------------------
Date: Tue, 25 Oct 88 00:59:05 EDT
From: attcan!utzoo!henry at uunet.uu.net
Subject: Re: Large screen display for SUN video output
>Does anyone have any info on taking the video output of a Sun 3/xx (color
>and/or mono) and feeding it to a large screen projection system (6ft.)
It depends on what kind of projection system you are talking about. If
it's a standard projection video setup, it's hopeless: the video scan
rates are incompatible, period. Scan conversion would be needed, and that
gets pricey.
You can get/rent video projectors which will deal with high scan rates,
however. At CHI+GI 87, we used a Hughes projector which worked pretty
well. I don't think those beasts are cheap, though, and they can be a bit
tricky to deal with (ours came complete with an engineer, who was very
helpful). Also, as far as I know they're strictly monochrome.
Henry Spencer at U of Toronto Zoology
uunet!attcan!utzoo!henry henry at zoo.toronto.edu
------------------------------
Date: Tue, 25 Oct 88 00:58:59 EDT
From: attcan!utzoo!henry at uunet.uu.net
Subject: Re: Using Return-Path: for replies
>not all uucp mailers change the "From:" line in the mail header to reflect
>passage through the machine. So the address there ends up being useless.
>This is indicative of poor system/network management. --wnl ]]
The problem here, actually, is the attempt to mix RFC822 format with the
old uucp format. Either one is entirely self-consistent, and the right
way to deal with the combination would have been to convert at gateways.
Unfortunately, what we actually have, courtesy of those wonderful people
at Berkeley, is a hybrid mess.
Changing any header line is a dangerous and doubtful thing to do. The
right thing to do to a "From:" line depends on its contents. In
particular, if it contains a legal domain address and the ultimate
addressee understands such addresses, IT IS A MAJOR MISTAKE FOR MAILERS
ALONG THE WAY TO MESS WITH IT. Uucp mailers should change the "From "
line (not the "From:" line) and only the "From " line; this is consistent
with the old uucp standard (which many sites have no choice but to
continue using) and is also consistent with the hoped-for future
environment in which "From:" is entirely domainist.
[[ You're right. It's a mess. I didn't mean to come down hard on
system/network managers unnecessarily. I just deal with fixing up bad 822
headers every day, and it gets annoying. --wnl ]]
Henry Spencer at U of Toronto Zoology
uunet!attcan!utzoo!henry henry at zoo.toronto.edu
------------------------------
Date: Tue, 25 Oct 88 13:34:58 PDT
From: chrisw at sun.com (Chris Wellens)
Subject: SunOS Source
To: SunSpots,
There has been concern and confusion expressed over the availability and
intentions of Sun with respect to the SunOS source code product. We would
like to clarify the situation by explaining what our source policies and
intentions are, and further, to express what has been happening with the
source release for SunOS 4.0, specifically.
It is, has been, and will remain Sun's policy to provide a high quality
source product for SunOS to Sun's customers.
The release of SunOS 4.0 introduced some new procedures and revealed some
internal problems that have hampered distribution of the release. We'd
like to address these one by one, and explain our response to them.
(1) The ordering process for the several SunOS source products had
confused internal procedures. This was causing some customers to get the
source code for versions of the operating system other than what they
expected.
We have now expanded our order entry system to properly support the
availability of multiple source products simultaneously.
In the future you will be able to order the current release, and the
previous versions of SunOS source.
(2) Internally, Sun has not handled this product in a standard fashion.
Earlier in our history, we had so few requests for source, that each
request was handled on an exception basis. With our rapid growth, we
found ourselves with a large volume of source orders that we were simply
not equipped to handle.
We have created a special sales guide that will be available to our field
sales force in November. This guide spells out in great detail the
procedures and paperwork required to order source code, including the AT&T
requirements and prerequisites. What this means to you is that your sales
rep will be able to provide you with the correct information to help you
place the order.
For example, we have a section explaining the prerequisite AT&T source
license for the SunOS source version you require:
SunOS Release AT&T Source License
3.2 System V Release 2.0
3.4 System V Release 3.0
3.5 System V Release 3.0
SYS4-3.2 (for Sun-4) System V Release 3.0
4.0 System V Release 3.1
NOTE:
-If System V Release 3.2 is required for future SunOS releases, commercial
and federal accounts will also need a sublicensing agreement with AT&T.
This is new AT&T requirement.
-SunOS source is not yet available on the Sun386i; we plan to make it
available.
As you know, SunOS is derived from AT&T's UNIX. As with all UNIX
licensees, Sun is obligated to follow the rules and regulations set forth
in our agreement with AT&T. This precludes our providing automatic source
updates, as a given source product may require proof of an updated AT&T
Source License Agreement.
(3) A decision to introduce a higher-quality source product has
introduced a delay between binary and source availability.
We believe the procedures we have introduced in the production of the 4.0
source product add significantly to its final quality. We appreciate that
any delay between the availability of source and binary version of the
same release can create problems, and are looking at ways to reduce this
delay in future releases.
The changes we have made should help solve your current problems with
SunOS source code. Your first point of contact should be your Sun Sales
Representative. We encourage you to talk to your representative about any
other problems or issues that might arise so we can continue to improve.
Marleen McDaniel Cynthia Typaldos
Director Of Marketing Director of Marketing
Education Products Division Software Products Division
------------------------------
Date: Fri, 21 Oct 88 10:42:42 GMT
From: mcvax!ecn-nlerf.com!wim at uunet.uu.net (Wim Rijnsburger)
Subject: top10 under SUN-OS 4.0?
One of our popular public domain programs, "top10" (display and update
information about the top cpu processes) does not compile under SUN-OS
4.0:
"top10.c", line 398: warning: illegal array size combination
"top10.c", line 399: warning: illegal array size combination
"display.c", line 303: PZERO undefined
"display.c", line 304: NZERO undefined
"display.c", line 360: PZERO undefined
"display.c", line 361: NZERO undefined
Does the author of this great program (or perhaps our Sun-Spots editor :-)
have any suggestions? We use version 2.1 of top10.
[[ The astute observer already knows that they are one in the same. You
need the newest version of top: version 2.5. It supports SunOS 4.0 (and
hopefully beyond). It is stored in Rice's archives under "public" as four
separate shar files: "top.shar.01" through "top.shar.04". It can be
retrieved via anonymous FTP from the host "titan.rice.edu" or via the
archive server. For more information about the archive server, send a
mail message containing the word "help" to the address
"archive-server at rice.edu". --wnl ]]
Wim.
Wim Rijnsburger e-mail: mcvax!ecn!wim
Netherlands Energy Research Foundation, ECN
P.O. Box 1, 1755 ZG Petten(NH), Holland phone : +31 2246 4336
------------------------------
Date: Mon, 24 Oct 88 15:15:59 PDT
From: versatc!tran at sun.com (Tony Tran 982-4317)
Subject: Testing sendmail?
How does one test sendmail thoroughly (i.e. all address formats, as well
as error loops)
Tony Tran
Versatec, Inc.
{sun|pyramid|ames}!versatc!tran
------------------------------
Date: Mon, 24 Oct 88 11:37:17 PDT
From: ucdavis!csusac!csun!polyslo!gshute at ucbvax.berkeley.edu (Glenn C. Shute)
Subject: Problem with PANIC: free
Has anyone else come across this problem:
dev=0x306 block=5831 fs=/blackbird
PANIC: free: freeing free frag
This has happened twice on a 3/280 running 4.0 but only when all 6 3/50
(diskless) and both 3/60 we being heavily used.
Any pointers appreciated
Glenn C. Shute Computer Science Department Cal Poly, SLO. Ca.
gshute at polyslo.CalPoly.EDU or {csun,voder,trwind}!polyslo!gshute
------------------------------
Date: Mon, 24 Oct 88 12:49:58 -0100
From: Ian Domville <mcvax!stl.stc.co.uk!id at uunet.uu.net>
Subject: Problems with dump on 4.0
Having upgraded to 4.0, I was ready to start the backups running. I had
seen the exhilarated articles on sun-spots declaring how wonderful it now
is and I read the manual page. Great I thought, no more specifying
ridiculous lengths to fool it into using all the tape. So you can
understand my disappointment when it failed to work like it promised.
There were two problems. First of all, I had trouble writing the tapes.
Then I had trouble reading them.
In the old days of 3.5, using 600' cartridges, I used to say :
/etc/dump 0ucbsf 1750 5100 /dev/nrst0 /dev/rxy<filesystem>
The 5100 is 600 (tape) * 9 (tracks) * .94 (fiddle factor). The 1750 was
recommended to me and greatly increased the speed of reading/writing. I
used to pack 6 dumps (/, /pub, /usr and 3 client partitions) onto 1 tape.
Our user files ran across two tapes. So I was quite happy with a)
multiple dumps per tape and b) multiple tapes per dump.
Having read the manual, I decided to use :
/usr/etc/dump 0ucbstf 1750 600 9 /dev/nrst0 /dev/rxy<filesystem>
I suspect the t option is unnecessary, but it shouldn't harm. Dump
estimated 1.06 tapes for ~66MB. Unfortunately, this complained about a
write error at 5460 feet! I tried again with a different tape, but got
the same problem. So I reduced the 600 to 575 and this time it worked,
but this is contrary to what I read on the net. It is irritating to waste
25' of tape.
The second problem is like this. I wrote two small dumps onto one tape.
I tried to read the second one with:
/usr/etc/restore ibfs 1750 /dev/rst0 2
Restore then demands the second volume. The first dump is perfectly
readable, as far as I can tell. So how can I safely put multiple dumps on
a tape? I really don't want to use one tape for only 6MB. Wasting 25' is
one thing, but 540' is another. It used to work before.
I would appreciate any suggestions I can get, particularly with the
second problem.
Regards,
Ian Domville
PHONE : PHONE : +44 279 29531 x2576
POST : STL Ltd., Old London Road, HARLOW, Essex, CM17 9NA, UK.
ARPA : id%stl.stc.co.uk at cs.ucl.ac.uk
JANET : id at stl.stc.co.uk
UUCP : id at stl.UUCP
------------------------------
Date: Thu, 20 Oct 88 17:29:10 +0100
From: mcvax!duttnph!tnhrwou at uunet.uu.net (Wouter Smaal Delft Univ.)
Subject: Problems with telnet pc-nfs 3.0
Recently we have updated pc-nfs to version 3.0 and 3C503 interface. We
discovered that telnet, rcp, ftp, and rsh does not works with the
Olivetti-M24 machines. Version 2.0 however, telnet etc., gives no problems
on the same type (M24) machines. With the pcnfs version 2.0 sun delivers
the 3C501 interface and with the 3.0 version sun uses the 3C503 board.
With version 2.0 and the 3C503 interface, telnet, rcp ftp and rsh works
fine. The 3C501 board in combination with pcnfs 3.0 telnet etc., works
also fine. The nfs server is a Sun4-280 with Sunos3.2.
On the Kaypro (really IBM alike ??) telnet of version 3.0 and the 3C503
booard gives no problems. It seems that version 3.0 of pc-nfs has only
problems with the Olivetti-M24 (in the USA AT&T 6300).
On suggestions of sunnl we did the following: We upgrade the Rom version
on the M24 machine to 1.43 and use the PAL PL-90. The version of the OS is
MS-DOS 3.10. However the result is that we still can not use telnet, rcp,
ftp and rsh with pcnfs 3.0 and the 3com503 board on our M24 machines. The
nfs functions are not a problem.
Who has any relevant suggestions to solve the problem, Sun-USA or UK perhaps?
Wouter Smaal (system manager)
Computational Physics group
Department of Applied Physics
Delft University of Technology
the Netherlands
------------------------------
Date: Mon, 24 Oct 88 11:25:01 PDT
From: ucdavis!csusac!csun!polyslo!gshute at ucbvax.berkeley.edu (Glenn C. Shute)
Subject: Looking for troff previewer for Sun's
Can anyone give me any pointers to troff previewers on Sun3's. Something
like texx for Latex.
Thanks--
Glenn C. Shute Computer Science Department Cal Poly, SLO. Ca.
gshute at polyslo.CalPoly.EDU or {csun,voder,trwind}!polyslo!gshute
------------------------------
End of SUN-Spots Digest
***********************
More information about the Comp.sys.sun
mailing list