Sun-Spots Digest, v6n107
William LeFebvre
Sun-Spots-Request at RICE.EDU
Sat Jun 11 04:57:54 AEST 1988
SUN-SPOTS DIGEST Friday, 10 June 1988 Volume 6 : Issue 107
Today's Topics:
Re: Doing the unexpected
Re: Sun2 Monitor on Sun3
Trojan Horse: "turkey"
need SLIP for SunOS 4.0
Need advice on distributed networks and database systems
Fast bcopy() on Sun-4?
Fine Grained Time stamps?
A simple question: L3
OCR for Suns?
Pointer for Clearpoint?
Sunview vfont to Framemaker bfont?
Setup guide for Telebit TrailBlazers on Sun Workstations (LONG)
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: Fri, 3 Jun 88 09:44:44 MDT
From: woods at handies.ucar.edu (Greg Woods)
Subject: Re: Doing the unexpected
I don't understand what is happening. If I attempt to start a second
sendmail daemon on any machine I've ever used, including Sun-3's and 4's,
I get "bind: address already in use". I didn't think it was possible for
two daemons to bind to the same port. Am I missing something?
--Greg (woods at ncar.ucar.edu)
[[ That's what I think, too. But I wasn't sure enough about it to say
something out loud. As far as I know, you can't have more than one
process "listening" to the same port....can you? --wnl ]]
------------------------------
Date: Fri, 3 Jun 88 07:33:35 PDT
From: nemo at sun.com (Pat Serbanic)
Subject: Re: Sun2 Monitor on Sun3
>From: polish at lexington.columbia.edu (Nathaniel Polish)
>I am trying to put a screen from a Sun2 (Multibus) on to a Sun3. The
>connector is the same but it does not seem to work....
Nat, et al,
It's the same thing, but different, that's all, probably. You see, the
Sun2 Multi-Bus used a TTL video output, while the Sun2 VME and, so far,
Sun3 and 4 video (Monochrome) is ECL, plus the cable, while using
identical connectors and gray cable, is wired differently. If your old
Sun2 monitor was manufactured by Moniterm, you may be able to select the
ECL option on the neckboard, but you will still need an ECL Video Cable.
Contact your Sun Sales rep. Also, what is the matter with the monitor that
came with your Sun3?? Did somebody steal it? Or, possibly, do you have a
Sun3/260 or 280? If the latter, the old Sun2 will not work, due to the
high-res frame buffer in the 260/280 CPU.
Pat Serbanic
------------------------------
Date: Fri, 3 Jun 88 11:11:21 BST
From: Jeff Parker <mcvax!nw.stl.stc.co.uk!jmp at uunet.uu.net>
Subject: Trojan Horse: "turkey"
[[ This was forwarded from the Usenet newsgroup "misc.security". --wnl ]]
>From: David Wright <DWW at ash>
>From: iberall at RANA.USC.EDU
There is a program being passed around via ARPAnet (and also some other
computer networks) called "turkey".
The instructions that are sent with the program say that when compiled and
run the program will draw a nice picture of a turkey. I have been
informed that the program is a Trojan Horse. It does not draw a turkey,
but it does erase all of the unprotected files in your directory. You
might want to pass this information along to people you know who use the
networks.
------------------------------
Date: Fri, 3 Jun 88 09:27:48 PDT
From: weiser.pa at xerox.com
Subject: need SLIP for SunOS 4.0
In SunOS 4.0 line disciplines have gone away. SLIP is implemented as a
line discipline, so the current SLIP for suns won't work.
Instead of line disciplines there are System V streams. While this is
undoubtedly a good idea, it means SLIP needs to be so ported. Has anyone
done this or working on it?
-mark
------------------------------
Date: Thu, 2 Jun 88 21:44:19 EDT
From: berlin%bu-albert.BU.EDU at bu-it.bu.edu (David Fickes)
Subject: Need advice on distributed networks and database systems
We are running a rather extensive database (Ingres) system on our Sun
network. Most of the users are our Sun clients will be constantly
accessing this database system on read-only basis. Since we have usually
unused 3/50, I was considering off loading any of our database retrievals
from our server onto this one 3/50 by having all of our staff members rsh
or rlogin into this 3/50 to run their material. We are current running
thin-net and I am interested in any experience or pointers anyone has
concerning the performance impact of such a move. It seems slightly silly
to be shipping all of that data across the thin-net but it might make
sense if we upgrade that one segment to thicknet and it the server is also
busy with other tasks.
If we do off-load this processing, what daemons should I run on that one
3/50 and which ones should I consider killing off (besides sendmail and
lpd). Perhaps running more biod processes might help out?
Interested in any and all comments,
thanks, david
David K. Fickes Center for Einstein Studies/Einstein Papers Project
UUCP: ...harvard!bu-it!bu-albert!berlin Boston University
BITNET: clx95on at bostonu 745 Commonwealth Avenue
PHONE: (617) 353-9249 (617) 277-9741 Boston, MA 02215
------------------------------
Date: 2 Jun 88 23:24:47 GMT
From: stevo at jane.jpl.nasa.gov (Steve Groom)
Subject: Fast bcopy() on Sun-4?
I am looking for a faster version of bcopy() to run on a Sun-4 (under 3.2
right now, 4.0 soon). I know that this was discussed recently, but I
don't follow the net too closely. I'd appreciate direct responses with
references to where I can get source, if possible.
thanks in advance-
-steve
Steve Groom, MS 168-522, Jet Propulsion Laboratory, Pasadena, CA 91109
Internet: stevo at elroy.jpl.nasa.gov UUCP: {ames,cit-vax}!elroy!stevo
[[ I don't think anyone ever came up with one. We did decide that a bcopy
that was optimized for a Sun-3 is not necessarily (and, in fact, probably
not) near-optimal for a Sun-4. --wnl ]]
------------------------------
Date: Fri, 3 Jun 88 08:00:26 PDT
From: Russell Brand <brand at lll-crg.llnl.gov>
Subject: Fine Grained Time stamps?
I need to get timestamps on characters (either from the keyboard or a
generic serial line) coming into my sun. How can I get the finest
resolution? (Nearsest Microsecond would be nice)
thanks/wuthel ( brand at lll-crg.llnl.gov )
[[ The system call "gettimeofday" fills in a structure that contains
seconds and microseconds. I am not sure if it is true microsecond
granularity, however. I don't know if this helps you or not. --wnl ]]
------------------------------
Date: Fri, 3 Jun 88 11:57:16 CST
From: munnari!smokey.ua.oz.au!richard at uunet.uu.net (Richard Altmann)
Subject: A simple question: L3
Question: What does the L3 button (or the Props button if you have your
keyboard set for suntools) on the keyboard do?
I have looked through our manuals here, but to no avail.
Thanks in advance
Richard Altmann
------------------------------
Date: 3 Jun 88 08:22:00 EST
From: "Dave Anderer" <dave at vax.oit.udel.edu>
Subject: OCR for Suns?
I'm looking for Optical Character Recognition hardware and software for
Suns. Are there any suppliers of good, inexpensive packages?
------------------------------
Date: Fri, 03 Jun 88 09:04:20 PDT
From: jtuckett at venera.isi.edu
Subject: Pointer for Clearpoint?
Good Morning,
Would it be possible for you to provide a pointer to Clearpoint? I'd
really appreciate it.
Janna
[[ Toll free number: (800) CLEARPT (that's 253-2778)
Address: 99 South Street, Hopkinton, Mass. 01748-2204
---wnl ]]
------------------------------
Date: 2 Jun 88 10:18 +0100
From: SCHOPFER Olivier <schopfer%cui.uucp at relay.cs.net>
Subject: Sunview vfont to Framemaker bfont?
I'm looking for a utility for converting FrameMaker bfont screen fonts to
SunView vfonts, and reverse from vfont to bfont. Does anybody know of
such a program or have a description of the bfont format.
Please answer per mail to
Olivier Schopfer
Bitnet: SCHOPFER at CGEUGE51.bitnet
UUCP: schopfer at cui.UUCP
path: cernvax!cui!schopfer
------------------------------
Date: Thu Jun 2 15:12:49 1988
From: telebit!rls at ames.arc.nasa.gov
Subject: Setup guide for Telebit TrailBlazers on Sun Workstations (LONG)
Organization: Telebit Corporation, Cupertine, CA
The following is a revised version of a previously posted setup guide for
Telebit TrailBlazers and Sun Workstations to setup UUCP. Minor changes in
the modem configuration should allow this to work in more varied
situations.
Regards,
Richard Siegel Phone: (415) 969-3800
Product Manager UUCP: {sun,uunet,ames,hoptoad}!telebit!rls
Telebit Corporation ARPA: telebit!rls at ames.ARPA
[[ The remainder of this digest issue contains nothing but the mentioned
setup guide. If you are not interested, you may safely skip the rest of
this issue. --wnl ]]
=====================================================================
Telebit Corporation Revision 1.01 03 MAY 1988
=====================================================================
SETUP INSTRUCTIONS FOR TELEBIT TRAILBLAZERS and SUN WORKSTATIONS
The following examples should allow easy initialization of a Telebit
TrailBlazer Plus modem for use with UUCP on a current SUN 3 or SUN 4
workstation.
1. MODIFY KERNEL:
First, the kernel must be modified so that the modem can dial/answer calls.
cd /usr/sys/conf
cp GENERIC MODEM
------edit MODEM-- change:
device zs0 at obio ? csr 0x20000 flags 3 priority 3
to:
device zs0 at obio ? csr 0x20000 flags 0 priority 3
-----save the file.
/etc/config MODEM
cd ../MODEM
make
mv /vmunix /vmunix.old
mv vmunix /vmunix
---reboot the system----------
2. CREATE THE DIAL OUT DEVICES (if necessary):
This will create the entries in /dev/to dial out with the modem.
cd /dev
mknod cua c 12 128
mknod cub c 12 129
chmod a+wr cua cub
References to dialout ports in this document assume the ttya port "cua". If
you are connecting to ttyb, remember to substitute "cub" where appropriate.
3. MODIFY /etc/gettytab:
This allows modem operation at 19200 bps.
cd /etc
--- edit gettytab, add this entry to the list:
z|std.19200|19200-baud:\
:sp#19200:
--- save the file.
4. MODIFY /etc/remote
Add these entries (all characters are literal, i.e. the ^ is 'shift 6'
on the Sun):
hard:dv=/dev/cua:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
cua:dv=/dev/cua:br#19200:el=^C^S^Q^U^D:ie=%$:oe=^D:
5. CONFIGURE MODEM
If the modem is NOT fresh out of the box from the factory, the reset button
on the back of the TrailBlazer Plus should be pressed. Use a paperclip or
some handy tool like that to depress the small micro switch located
(recessed) through a small hole next to the RS232 serial connector.
Make sure the modem is powered ON when depressing the switch.
With the modem now reset, tip to the modem (use "tip hard" to talk at
9600 bps) and configure it with the command string below:
AT &F S51=5 S52=2 S54=3 S110=1 S111=30 S45=0 S58=0 S53=3 S66=1 Q6 &W <CR>
This string (the spaces are optional if you prefer to remove them) will:
- 1st (&F) recalls factory defaults (start with known configuration).
- 2nd (S51=5) sets the serial port to 19200 bps.
- 3rd (S52=2) says drop the connection when DTR is dropped to the modem
and reload the modem's stored EEPROM values (do a soft reset).
- 4th (S54=3) says pass BREAKs through the modem transparently.
- 5th (S110=1) enables data compression between TrailBlazers.
If desired, S110=0 will disable this feature.
- 6th (S111=30) enables UUCP "g" protocol support in the TrailBlazer.
- 7th (S45=0) disables remote access.
When the reset button is pressed, remote access is enabled to
allow easier customer support from Telebit. This is not the
case when the modem is originally shipped from the factory.
Remote access is not necessary for this application.
- 8th (S58=0) disables flow control.
The UUCP protocol support handles flow control instead.
- 9th (S53=3) sets DSR "ON" when modem is off-hook.
It also sets DCD "ON" when carrier is detected.
- 10th (S66=1) locks the interface speed.
- 11th (Q6) silences the modem when an inbound call arrives.
This prevents getty battles between the RING result code and
getty's echo of the same.
- 12th (&W) writes these new values into the EEPROM.
This saves the new values as the modem's power on defaults from
now until you change them again.
- 13th (<CR>) terminates the command to the modem.
After this, when you want to talk directly to the modem, use "tip cua"
to talk at 19200 bps, since you just set the interface speed to 19200.
NOTE: If you want to prevent anyone from connecting at other than
high speed (PEP mode), add "S50=255" to the above script to
force the modem to use only PEP mode. To allow dial OUT to
other speed modems, modify the L.sys script (noted below in
step 9) to:
hostname Any cua 19200 cua "" ATX0S50=0\r OK ATDNNNNNNNNNN\r CONNECT ""
""-\r-login:-\r-login:-\r-login: \r login: Uyoursysname ssword: XXXXXXXX
6. ENABLE GETTY FOR DIALIN:
cd /etc
--- edit ttys and change:
0fttya
to:
1zttya
--- restart getty on ttya:
kill -1 1
Don't forget to set your getty to include 19200 in its cycle.
You may have it trying 19200 first and moving to 2400 on the 1st
receipt of a break and to 1200 on the second receipt of break.
The order of the cycle is not important so long as the calling
system knows to send breaks until it sees the login sequence.
7. MODIFY /usr/lib/uucp/uucico TO RUN 19200 BPS:
To use uucico at 19200, you must modify the Sun version using "adb".
We will use the 4800 baud entry and replace it with 19200.
cd /usr/lib/uucp
cp uucico uucico.orig
adb -w uucico
20000?L 0t4800
--- at this point you'll get output something like:
20a0c:
--- so enter:
?DD
--- it will respond with ADDRESS:DATA like:
20a0c: 4800 12
--- so enter:
?W 0t19200 0t14
--- now type ^D. This completes the uucico modification.
NOTE: Don't forget to check the permissions and ownership of uucico.orig
to be the same as uucico.
8. MODIFY /usr/lib/uucp/L-Devices:
Add the following entry to your L-Devices file. Fill in the correct port #
DIR cua 0 19200
9. MODIFY /usr/lib/uucp/L.sys:
Don't copy this literally. Modify the info for your application.
Also note that this is ONE line of data, not two.
hostname Any cua 19200 cua "" ATX0\r OK ATDNNNNNNNNNN\r CONNECT ""
""-\r-login:-\r-login:-\r-login: \r login: Uyoursysname ssword: XXXXXXXX
NOTES:
hostname = THEIR System name
NNNNNNNNNN = THEIR System phone number
Uyoursysname = Your UUCP account on THEIR machine
XXXXXXXX = Your UUCP passwd on THEIR machine
You should now be able to run UUCP between two machines attached to your
modems just as you always have with slower modems. Enjoy the new world of
of high speed UUCP "g" via the Telebit TrailBlazer Plus.
Michael Ballard
Telebit Corporation
1345 Shorebird Way
Mountain View, CA 94043
{ames, uunet, hoptoad, sun, dwon}!telebit!modems
------------------------------
End of SUN-Spots Digest
***********************
More information about the Comp.sys.sun
mailing list