HDTenEightyP/NetNews huggingface dataset:
From: cage@cbnewsd.cb.att.com (charles.gerlach)
Subject: Re: NFS for a 3B2 SYSV R3.2.[23]
Organization: AT&T
Distribution: na
Date: Wed, 26 Aug 1992 23:15:43 GMT

In article <1992Aug21.161815.1888@sparky.imd.sterling.com> jeff@IMD.Sterling.COM (Jeff Mosher) writes:
>
>
>Is NFS available for a 3B2 600G running SYS V R3.2.2 or 3.2.3 UNIX and
>where can I get it if it is?
>
>
>A related question: Is NFS available for the 3B2 600GR (RISC based)
>running SYSV R4?

Hopefully the following information answers your questions.  If you
can't get the packages through the sales force or you have questions
that they can't answer, I would contact the product manager, Kristin
Schneider, at (708)-979-1017.
 
The latest SVR3 3B2 NFS is Release 1.3.  This package requires SVR3.2 
or newer and TCP Release 3.2.  It will not work with SVR4.  The NCR 
product ID is C274-0NB3- 0000.  

NFS does come bundled with SVR4 for RISC-based 3B2's. TCP/IP, on the
other hand, does not and has to be purchased separately.

			Chuck Gerlach
			NCR MCPD-Naperville
			..!att!iwcs!cag or cag@iwcs.att.com
Xref: sparky comp.sys.att:2086 comp.unix.solaris:178 comp.unix.sysv386:13550
From: stanonik@nprdc.navy.mil (Ron Stanonik)
Newsgroups: comp.sys.att,comp.unix.solaris,comp.unix.sysv386
Subject: SVR4 - initializing TERM
Date: 25 Aug 92 21:43:50 GMT
Organization: Navy Personnel R&D Center

We'd like to initialize the TERM environment variable based on
the tty port.  In bsd and sunos this can be set in /etc/ttys
and /etc/ttytab, respectively.  In SVR4, however, ttymon
doesn't seem to provide a way to do this.  The per-service
config file didn't work; ie, pmadm -g -p porttag -s svctag -z conffile,
where confile contains "assign TERM=vt100".  Any suggestions?

Thanks,

-- 
Ron Stanonik
stanonik@nprdc.navy.mil
ucsd!nprdc!stanonik
Newsgroups: comp.sys.att
From: ami@gmuvax2.gmu.edu (Ami Motro)
Subject: Re: telnet causing 3B2/600 to crash
Keywords: telnet 3B2 crash
Organization: George Mason University, Fairfax, Va.
Date: Tue, 1 Sep 1992 20:40:50 GMT

There was discussion here recently about telnet causing system panics.
and a suggestion to set IP_TTL= oxff in /etc/master.d/ip

My problem was different.  For a long time I was only able to telnet only to
some sites off campus.  For all others I would get almost instantly
"connect: connection timed out".

Because I also remember crashing my system when telenetting into it from
afar, I decided the problems might be related, and made the above change.

And -- voila! -- the rest of the world is now telnet'able

Maybe others who have experienced my problem could benefit from this tip.

Ami

PS. I am using Wollongong TCP/IP Win/3b Rel;ease 3.2 on a 3b2/310
Newsgroups: comp.sys.att
From: root@candle.uucp (Bruce Momjian)
Subject: Multiple lp requests cause mail report
Organization: a consultant's basement
Date: Tue, 1 Sep 1992 01:41:47 GMT
X-Newsreader: Tin 1.1 PL5


If I issue several print requests via 'lp', I get the following mail
message sent to root.

The first couple jobs print, then the printer stops, then starts up a
few minutes later.  Print jobs are supposed to spool, one after each
other.  I am running AT&T 386 Unix SVr3.1 and an IBM Proprinter II.

How do I fix this?  Where do I look?

-------------------------------------------------------------------
Subject: Problem with printer printer

The printer printer has stopped printing for the reason given below.
Fix the problem and bring the printer back on line.
Printing has stopped, but will be restarted in a few minutes;
issue an enable command if you want to restart sooner.
Unless someone issues a change request

	lp -i printer-1315 -P ...

to change the page list to print, the current request will be reprinted from
the beginning.

The reason(s) it stopped (multiple reasons indicate repeated attempts):

Failed to open the printer port.
(Device busy)


-- 
Bruce Momjian                      |  830 Blythe Avenue
root%candle.uucp@bts.com           |  Drexel Hill, Pennsylvania 19026 
                                   |  (215) 353-9879(w)  853-3000(h)
Newsgroups: comp.sys.att,gnu.gcc.help,gnu.g++.help
From: greg@gallifrey.ucs.uoknor.edu (Greg Trotter)
Subject: Needing GNU compiler for ATT 6386/25 running UNIX
Followup-To: poster
Summary: I need it precompiled
Organization: A Planet Of His Own
Distribution: na
Date: Wed, 26 Aug 1992 01:46:08 GMT

Help!

I'm running UNIX on an AT&T 6386/25 critter. I need a C or C++ compiler.
At present, I have no compiler -- so GNU source code is pretty useless
for me. If anyone has a precompiled version to send me, I'd be eternally
grateful.

						- greg
Newsgroups: comp.sys.att
From: Rusty Hodge <rhodge@amgen.com>
Subject: TCP/IP for 3B2/310
Organization: Amgen, Inc.
X-Useragent: Nuntius v1.0
Distribution: usa
Date: Fri, 28 Aug 1992 23:55:02 GMT

I am looking for TCP/IP for the 3B2/310.  If anyone can point me in the
right direction
for obtaining it, I would greatly appreciate it.

Rusty Hodge (310) 478-8798
rustyh@sam.amgen.com
Newsgroups: comp.sys.att,comp.unix.solaris,comp.unix.sysv386
From: dzik@access.digex.com (Joseph Dzikiewicz)
Subject: When to port to Solaris 2.x
Organization: Express Access Online Communications, Greenbelt, MD USA
Date: Fri, 28 Aug 1992 12:49:30 GMT


We have a Sun application, and are giving some thought to when we
should port to Solaris 2.x.  Does anyone know when Sun intends to
ship new SparcStations with 2.x?  Does anyone have any other ideas
on when 2.x will achieve a significant presence?  (Porting our
software is the least of our problems: we have done ports to
several UNIX machines.  I am mostly interested in when we should
dedicate a Sun to 2.x, and when we need to find a C compiler for
it.)

Thanks,
Joe Dzikiewicz
From: hak@alf.cooper.edu (Jeff Hakner)
Newsgroups: comp.sys.att
Subject: Re: NFS for a 3B2 SYSV R3.2.[23]
Date: 24 Aug 92 02:01:24 GMT
Organization: The Cooper Union ( NY, NY )

in article <1992Aug21.161815.1888@sparky.imd.sterling.com>, jeff@IMD.Sterling.COM (Jeff Mosher) says:
> X-Md4-Signature: c1fbb653de735e9de192c7adec456b5b
> 
> 
> This may be a FAQ, so forgive me (i.e. set your flame throwers to low).
> 
> Is NFS available for a 3B2 600G running SYS V R3.2.2 or 3.2.3 UNIX and
> where can I get it if it is?
> 
> The 3B2 experts tell me that the 3B2 600G is really a 3B2/1000 model 80 if
> that makes any difference...
> 
> A related question: Is NFS available for the 3B2 600GR (RISC based)
> running SYSV R4?
NFS is included in SVR4.  However, I haven't seen the R3000 SVR4 binaries
so I can't tell you if NFS has been unbundled by AT&CR.
Newsgroups: comp.sys.att
From: hc05@rexago8.uucp (Beirne Konarski)
Subject: Re: shl error on 3B2-400
Reply-To: beirnek@summitis.COM
Organization: Summit Information Systems
Date: Fri, 28 Aug 1992 20:41:33 GMT

dcb@kopachuk.uucp (David Breneman) writes:

>So, here's the problem.  I've got a 3B2-400 running 3.1 and
>when I try to use layers, here's what I get:

>$ shl
>no control channels available (errno=6)
>$ 

>There are plenty of sxt devices in the /dev directory (sxt000 thru
>sxt057) and /dev/sxt directory (000 thru 057).  It doesn't work
>when I'm root, either, so I can't see it's a permissions problem.
>Anybody know what's going on here?  Error number 6 is supposed to
>be "No such device or address".  Thank you one and all for any advice.

When we get that error we remove and reinstall the User Environment Utilities.
I don't know what the actual problem is but this gets shl to work.

Beirne
-- 
-------------------------------------------------------------------------------
Beirne Konarski			| Reading maketh a full man, conference a
beirnek@summitis.com 		| ready man, and writing an exact man.
				|	-- Francis Bacon
From: cage@cbnewsd.cb.att.com (charles.gerlach)
Newsgroups: comp.sys.att
Subject: Re: NCR/AT&T Part Number for WIN/TCP 4.0 Upgrade ???
Date: 26 Aug 92 22:52:24 GMT
Distribution: na
Organization: AT&T

In article <1992Aug12.155050.23408@xenitec.on.ca> merce@xenitec.on.ca (Jim Mercer) writes:

>i hear that there is a WIN/TCP upgrade to 4.0 for the 3B2.
>
>anyways, my NCR contact tells me his life would be alot easier if he had some
>NCR part/library number for this upgrade.
>

I really hate to confuse everyone with a few facts, but every good thing 
must end sooner or later.  The following is information as I know it on 
AT&T's products.  Before making any serious commitments I would check 
with your salesman or the product manager.
 
The latest release of  3B2 TCP/IP for SVR3 is Release 3.2.  Since it was 
released several years ago, there have been a number of patches to 
correct problems either reported by customers or discovered during 
work on the SVR4 versions.  These patches are available from the NCR 
support organization.  The NCR product ID for the R3.2 TCP/IP package is 
C274-0TB3-0000.  
 
Release 3.2 TCP/IP will work on anything from SVR3.1 to SVR3.2.3.  
There appears to be some confusion concerning release numbering.  The 
OS release and the TCP/IP release are not tied together.  Release 3.2 is the 
third major release of the TCP product we've made.  Also, be careful 
comparing Wollongong's release numbers with AT&T/NCR's.  The 
numbering schemes are not necessarily in sync.
 
I am unaware of any formal release of patches for this product, but I have 
not followed these products closely since the beginning of the year when 
my group transfered development responsibility to another NCR site.  I 
expect either the support groups or the Federal Systems channel has 
packaged and numbered the patches, but I'm not sure.
 
There is a Release 4.0  of TCP/IP.  This package will only work on SVR4.  
In order to use it your 3B2 must be 3B2 R3 (RISC-based).  Release 4.0 
will not work on any other 3B2's.  The product ID for the 4.0 TCP/IP 
package is C903-0046-0000.
 
If your NCR contact has any questions concerning either of the products or 
the applicability of either to your situation, please have him call the 
product manager for these two  products: Steve Long at (619)-693-
5531.   
 
The latest SVR3 3B2 NFS is Release 1.3.  This package requires SVR3.2 
or newer and TCP Release 3.2.  The NCR product ID is C274-0NB3-
0000.  Kristin Schneider is the product manager for this package and she 
can be contacted at (708)-979-1017.

Hopefully this information will help resolve your questions.

			Chuck Gerlach
			NCR MCPD-Naperville
			..!att!iwcs!cag or cag@iwcs.att.com
From: mgriffin@matt.ksu.ksu.edu (Mark Griffin)
Newsgroups: comp.sys.att
Subject: Increase size of MAXUSERS
Date: 3 Sep 92 14:20:42 GMT
Organization: Kansas State University
NNTP-Posting-Host: matt.ksu.ksu.edu

Every night mail is sent from diskacct to root with the following message:
diskacct: Increase size of MAXUSERS
We have over 1500 accounts on our system, but I have looked and looked for
a MAXUSERS parameter to set, but have not found one.  I cannot find anything
in the documentation about this either.  Can anyone tell me where this should
be set.

-- 
.   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .  .
Mark Griffin, Sys Admin, Fort Hays State University      |It is always better to
Internet:mgriffin@matt.ksu.ksu.edu Bitnet:mgriffin@ksuvm |do, than be done to.
.   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .   .  .
From: rrezaian@austral.chi.il.us (Russell Rezaian)
Newsgroups: comp.sys.att
Subject: 3B2 SCSI config file question.
Keywords: 3B2 SCSI CONFIG
Date: 30 Aug 92 20:48:12 GMT
Organization: DOC Data Processing Systems

I have a question about the SCSI config files on a 3B2.  I have added a
small SCSI drive to the system to provide added space, and speed up a few
operations.  I followed the procedure described in the FAQ file, and things
went smoothly, for the most part.  Unfortunatly, the FAQ left one or two
questions still unanswered.

The drive is installed, and seems to be working fine so far, BUT  I still
get a small set of error messages on boot up, and I think they might be
realted to a guess I made as I was installing the drive.

In the /usr/lib/scsi directory there is a file called tc.index which lists
all the recognized scsi devices and references between them and one of
three other files in the directory.  Those files are called sd00.0 sd01.1
and sd01.2.

The sd0x.x files all are text, and appear to contain SCSI control config
information.  I randomply picked one of these when installing the drive,
and I am not sure whether it was the right one.

If someone can tell me just what these files are, and what the
differences between them mean (and especially how to determine which one
to use for a given device) I would very much appreciate it!
--
Russell Rezaian			|  rrezaian@austral.chi.il.us
From: rdc30@nmrdc1.nmrdc.nnmc.navy.mil (LCDR Michael E. Dobson)
Newsgroups: comp.sys.att
Subject: Re: NCR/AT&T Part Number for WIN/TCP 4.0 Upgrade ???
Date: 25 Aug 92 17:22:12 GMT
Distribution: usa
Organization: Naval Medical Research & Development Command

In article <1649@netsys.NETSYS.COM> len@netsys.NETSYS.COM (Len Rose) writes:
>Basically I was just repeating what I had been told by Wollongong here in
>Palo Alto ... I spoke with a guy named Kurt. I seem to remember the product
>announcement for it back when I was running info-3b2 mailing list. I was
>very surprised to say the least.
>
>On another note, what the heck is the latest release of win tcp for the
>3B2 anyway? I am having nasty problems with named, and ftp ... I just 
>brought my 3B2/600 up on the Internet and it's been a terrible experience.
>
I believe the latest WIN/3B release for SysVR3.2 is Release 3.2 Update 1.3,
at least that was what came with the latest update tapes I got a couple of
months back.  It can even do anonymous ftp although I sometimes find ftpd
sessions hanging around.

Mike
-- 
LCDR Mike Dobson, Sys Admin for | Internet: rdc30@nmrdc1.nmrdc.nnmc.navy.mil
nmrdc1.nmrdc.nnmc.navy.mil      | UUCP:   ...uunet!mimsy!nmrdc1!rdc30
AT&T 3B2/600G Sys V R 3.2.3     | BITNET:   dobson@usuhsb or nrd0mxd@vmnmdsc
WIN/TCP for 3B2  R3.2           | MCI-Mail: 377-2719 or 0003772719@mcimail.com
Newsgroups: comp.sys.att
From: merce@xenitec.on.ca (Jim Mercer)
Subject: Re: Sync-ing system clocks over StarLAN
Organization: Reptilian Research, Kitchener, Ontario, CANADA
Date: Thu, 27 Aug 1992 05:35:59 GMT

In article <16849C680.R1004@vmcms.csuohio.edu> R1004@vmcms.csuohio.edu writes:
>     That looks fine, except some of my machines don't have
>remsh on them since I never bought WIN/TCP for them (SysV R3.1 and
>R3.2).
> 
>    I don't trust UUX to do a good job.  Running StarLAN 3.2 if
>that matters.
> 
>    Am I stuck with syncing machines with the wristwatch method?

hunt up the r-utilities that were ported to Starlan on the 3b1.

shouldn't be too much to port it.

-- 
[ Jim Mercer   Reptilian Research  merce@iguana.reptiles.org  +1 519 893-6085 ]
[             I don't want to work for a company that has a CIO.              ]
[              Disclaimer! I don't need no stinking Disclaimer!               ]
Newsgroups: comp.sys.att,comp.binaries.ibm.pc.wanted,comp.sys.novell,comp.protocols.tcp-ip.ibmpc
From: msc@ssigate.ssinc.com (Michael S. Cross)
Subject: Need NDIS driver for Starlan 10 Card
Followup-To: comp.sys.att
Organization: Systems and Synchronous Inc. (Naperville, IL)
Date: Wed, 26 Aug 1992 21:40:09 GMT


Hi all,

     I was wondering if anyone knew where we could get an NDIS driver
for DOS that supports the AT&T StarLan 10 Card.

If not, how about an ODLI driver for said card?

I don't necessarily need the source code, and it doesn't make any
difference if it is a PD/SW/commercial program at this point.
(and, yes, I already have the Clarkson Packet Drivers)

Please post your response (as opposed to just mailing it) because many
sites are having trouble reaching us via the UUMAPS.  I think I set the
followup-to line to comp.sys.att correctly ...

Thanks muchly.

Mike

-- 
Michael S. Cross         Work: msc@ssihub.ssinc.com               708-505-4508
      Home: 73750.1363@CompuServe.com  (but not exactly *proud* of it)
Systems and Synchronous Inc., 900 E. Diehl Rd, Suite 110, Naperville, IL 60563
__________________________To Live is to risk Dying____________________________
Xref: sparky comp.sys.att:2100 comp.unix.solaris:192 comp.unix.sysv386:13699
From: stanonik@nprdc.navy.mil (Ron Stanonik)
Newsgroups: comp.sys.att,comp.unix.solaris,comp.unix.sysv386
Subject: SUMMARY: SVR4 - initializing TERM
Date: 27 Aug 92 22:53:34 GMT
Organization: Navy Personnel R&D Center

The question was, "How do you initialize TERM in SVR4?".
In BSD you edit the /etc/ttys, in sunos you edit /etc/ttytab,
and in some SVR3's (apparently not on 3B2's, however) you
edit the /etc/ttytype.

In SVR4 on our 386, there is an /etc/ttytype, which /bin/login
apparently reads.

In some SVR4's (eg, from DG), the "assign TERM=whatever" in the
per service config file (eg, /etc/saf/<pmtag>/<tty>) works.

In Solaris 2.0, ttyadm has a -T option, whose value is inserted
into the appropriate /etc/saf/<pmtag>/_pmtab.

In SVR4 on 3B2's ... none of the above work.  Hack up a script
which figures it out and source it from every user's .login/.profile,
I guess.


From: mju@mudos.ann-arbor.mi.us (Marc Unangst)
	You're looking in the wrong place.  Try /etc/ttytype.

From: nto2584@dsaca1.dsac.dla.mil (Steven C. Payne)
	I did what you are trying by putting an entry in the profile
	which did a check on the tty, and based on that, it initialized
	the tty to whatever.

From: mcb@mach.eng.hou.compaq.com (Mike Busby)
	Under SysV.3 there was a file called /etc/ttytype that contained this
	info.  The structure was 'TERM tty', one per line.  For example:

From: ade@clark.edu (Adrian Miranda)
	Have you tried /etc/ttytype?  Seems to work for me.  I believe login
	is the program that actually looks at it...

From: Rick.McNeal@Central.Sun.COM (Rick McNeal)
	I just looked at the Solaris 2.0 source for ttymon and there's a
	-T flag which alows you to set the term type on the command line.
	I don't have the man pages handy to see if this is documented or not.

From: David.Miner@East.Sun.COM (Dave Miner)
	Below is an example which essentially worked at one point during
	development, and I presume still does though I haven't tried it in
	over a year.
	   System V traditonally had inittab to allow this functionality and
	   SunOS has ttytab.  In SVr4 you have to do something like the
	   following... (set terminal type for ttyb)

	   sacadm -a -p ttymon1 -t ttymon -c /usr/lib/saf/ttymon -v `ttyadm -V`

	   pmadm -a -p ttymon1 -s ttyb -i root -fu -v `ttyadm -V` \
	   -m "`ttyadm -d /dev/ttyb -l 9600 \
	   -s '/usr/bin/login -h {hostname} TERM=tvi925' -m ldterm -p
	   \"ttyb login: \"`"

-- 
Ron Stanonik
stanonik@nprdc.navy.mil
ucsd!nprdc!stanonik
Newsgroups: comp.sys.att
From: jeffrey@squid.tram.com (Jeffrey L Bromberger)
Subject: Contents/use of stuff in 3B2's libPW.a?
Organization: Tramway Unix Systems
Date: Wed, 26 Aug 1992 05:46:42 GMT
Summary: man pages for the rest of this stuff?
Keywords: CPLU 4.1 PWB

While looking for a pre-existing version of alloca for my machine (a
3b2/400 with CPLU 4.1), I started snooping through the libraries on
the system.  The one library with a lot of neat-sounding stuff was
libPW - the Programmers Work Bench.  Well, I went looking through the
man pages, and found awfully little on this stuff, and would like some
info on exactly what some of these routines do.  Here's what I found:

abspath.o - ?
anystr.o - ?
curdir.o - The directory (3X) routines?  Maybe more.
fdfopen.o - ?
giveup.o - ?
imatch.o - ?
index.o - BSD index routine?
lockit.o - ?
logname.o - ?
move.o - ?
patoi.o - something ascii to integer?
patol.o - something ascii to long?
regcmp - RegEx(3X)
regex.o - RegEx(3X)
rename.o - the missing rename(2) call?
repeat.o - ?
repl.o - ?
satoi.o - something ascii to integer?
setsig.o - BSD signal stuff?
sname.o - ?
strend.o - ?
substr.o - ?
trnslat.o - ?
userdir.o - Some novel way to access password file fields?
username.o - More password file mucking?
verify.o - ?
any.o - Used in anystr.o and verify.o above
xalloc.o - ? -----
xcreat.o - ?     |
xlink.o - ?      |  These all appear to go together
xopen.o - ?      |  into one suite of x? routintes
xpipe.o - ?      |
xunlink.o - ?    |
xwrite.o - ?     |
xmsg.o - ? -------
alloca.o - alloca - no man page for this BTW
cat.o - used by x? routines above
dname.o - used by x? routines above
fatal.o - used by x? routines above
clean.o - used in x? routines above
userexit.o - used in x? routines above
zero.o - ?
zeropad.o - ?

Can anyone out there fill me in on what I am most likely missing here?
They (AT&T) couldn't really have given a library without any
documentation on what the routines do, could they? 1/2 :-)
There is no guarantee that I hit upon all the "internal" routines.
Some may never have been meant to be called from anything other than
a preceeding library routine (like fatal and clean).

j
-- 
Jeffrey L. Bromberger ------- System Manager ------- Tramway Unix Systems
jeffrey@squid.tram.com      Anywhere!{van-bc,limbic,icus}!tram!jeffrey
Newsgroups: comp.sys.att
From: hak@alf.cooper.edu (Jeff Hakner)
Subject: Re: NFS & SVR4
Organization: The Cooper Union ( NY, NY )
Distribution: na
Date: Fri, 28 Aug 1992 02:32:54 GMT

in article <1992Aug26.231543.27530@cbnewsd.cb.att.com>, cage@cbnewsd.cb.att.com (charles.gerlach) says:
> 
> In article <1992Aug21.161815.1888@sparky.imd.sterling.com> jeff@IMD.Sterling.COM (Jeff Mosher) writes:
>>
>>
>>Is NFS available for a 3B2 600G running SYS V R3.2.2 or 3.2.3 UNIX and
>>where can I get it if it is?
>>
>>
>>A related question: Is NFS available for the 3B2 600GR (RISC based)
>>running SYSV R4?
> 
> Hopefully the following information answers your questions.  If you
> can't get the packages through the sales force or you have questions
> that they can't answer, I would contact the product manager, Kristin
> Schneider, at (708)-979-1017.
>  
> The latest SVR3 3B2 NFS is Release 1.3.  This package requires SVR3.2 
> or newer and TCP Release 3.2.  It will not work with SVR4.  The NCR 
> product ID is C274-0NB3- 0000.  
> 
> NFS does come bundled with SVR4 for RISC-based 3B2's. TCP/IP, on the
> other hand, does not and has to be purchased separately.
> 
> 			Chuck Gerlach
> 			NCR MCPD-Naperville
> 			..!att!iwcs!cag or cag@iwcs.att.com
Now that is truly funny!!  I can't imagine too many customers who
want NFS without TCP/IP!  

Incidentally, the TCP/IP that comes with SVR>=4.0 is not related
to the lousy Wollongongshow product which plagues pre SVR4 3B2s.
It is derived from Lachman Associates code, which is also the base
of the SunOS TCP/IP code, which is not surprising, considering the
history of SVR4.

As for the unbundling issue, one can get SVR4.1, Ehanced Security,
NFS and TCP/IP plus source code from USL.  This product is available
for 3B2 V3 computers running the WECO processor (that's right, the
original processor, not the RISC upgrade), and (get this!) 3B2 V2
computers (3B2/300,310 and 400).  I know this for a fact because I am
currently running SVR4.1ES on a 3B2/310.

The SVR4.1ES product has some nice additions over SVR4.0, including
B1 security.  You can also have a root file system of the SFS(
Secure File System) type, which gives you UFS-style arbitrary
pathnames, anti-frag, etc.  I believe that SVR4.0 had a bug which
prevented one from having a root filesystem of the UFS type (you
had to use S5), but perhaps that's been corrected by now.

At any rate, it would be nice if ATT/NCR could take this package
from US and resell it as a binary product for the 3B2 (yes, all
3B2s, not just V3RISC).  Just MHO.

--Jeff Hakner