HDTenEightyP/NetNews huggingface dataset:
From: uucm000@uxa.ecn.bgu.edu (Tingli Pan)
Newsgroups: comp.unix.sysv386
Subject: Kermit for SCO
Date: 1 Oct 92 19:53:10 GMT
Organization: Educational Computing Network

I'm going to install kermit in our SCO in a Dec 486. I know the ftp site
is watsun.cc.columbia.edu. But I couldn't find the exact file for
kermit. Which directory in SCO should I put on the kermit and make it
available for every body.

Tingli Pan                           
Academic Computing Services          Internet: uucm000@uxa.ecn.bgu.edu
Northeastern Illinois University     Bitnet:   uucm000@ecnuxa.bitnet
From: bill@ricker.gwinnett.com (William L. Ricker)
Newsgroups: comp.unix.sysv386
Subject: Re: Looking for Posting on "Which 386 *nix do I buy"
Date: 24 Sep 92 04:47:41 GMT
Organization: The Software Foundry

steveh@zentronics.ca (Steve Haller) writes:
> Would someone be kind enough to email me or let me know of a source
> for obtaining the article describing the features/benefits, advantages/
> disadvantages, etc of the various 386 *nix packages.

I also, would be very interested in any info out there.

Thanks
bill

--
Bill Ricker
E-mail: bill@ricker.gwinnett.com
S-mail: 1280 West Peachtree Street #3110
        Atlanta, GA 30367
Voice:  (404) 321-4027
Newsgroups: comp.unix.sysv386
From: jle9162@zeus.tamu.edu (ECKHARDT, JASON LEE)
Subject: Terminals under SCO
News-Software: VAX/VMS VNEWS 1.41    
Organization: Texas A&M University, Academic Computing Services
Distribution: usa
Date: Thu, 1 Oct 1992 15:36:00 GMT

  How the heck do I get a serial terminal connected by null modem cable
to com2 on my SCO UNIX 3.2.2 system working? If I 'enable' it, all the
machine does is hang and needs rebooting. The same happens with a simple
'echo hello >/dev/tty2a.' Why!? 
I have tried this with 2 other unixes and they work fine...So what is it
about SCO thats different that I should know about? I now have 
fas 2.09 installed. Strangely enough, though, my modem works fine on
com1 or com2.
I've asked this a couple times here and on biz.sco.* with no reply.
Doesn't anyone use SCO and terminals that can tell me how they do it?

I don't need a tutorial, just why other unixes on the same machine work,
but SCO doesn't...

Stumped, Jason.
jle9162@venus.tamu.edu

Newsgroups: comp.unix.sysv386,comp.emacs,comp.sources.d
From: witr@rwwa.COM (Robert Withrow)
Subject: Re: Wangtek or Archive??
Reply-To: witr@rwwa.com
Organization: R.W. Withrow Associates
Distribution: usa
Date: Tue, 6 Oct 1992 13:52:00 GMT

In article <1992Oct5.225135.8660@acuson.com>, 
  liuwu@acuson.com (Wu Liu) writes:

| I've been told (but haven't verified one way or the other) that DC6250
| tapes cause wear patterns on the head that aren't the same as those
| induced by DC6150s.  It's recommended that you stick primarily with
| one type of tape or the other, rather than mixing the use of both.

This comes up every now and then.

My guess is that:

  1) Wear patterns are probably only significant for drives that receive
     heavy use (hour(s) per day).  The heads are rated for life at least
     in the high hundreds of hours.  They may be rated in the low thousands
     of hours.

  2) Wear patterns are probably only significant for drives that *primarily*
     use *one* type of tape.  Using 6250 primarily might cause problems 
     for the occational use of 6150 tape, and the converse.

  3) Random use of the various tape formats compatible with this drive
     probably randomizes head wear.  A drive used in such a way will likely
     be able to use all formats for the duration of the head life.

But then, I'm not an ME and I don't even play one... ;-)

-- 
 Robert Withrow, Tel: +1 617 598 4480, Fax: +1 617 598 4430, Net: witr@rwwa.COM
 R.W. Withrow Associates, 21 Railroad Ave, Swampscott MA 01907-1821 USA
Newsgroups: comp.unix.sysv386
From: howardl@wb3ffv.ampr.org (Howard Leadmon - WB3FFV)
Subject: Re: lpd for SCO Unix 3.2.4 wanted
Organization: Advanced Business Solutions, Inc.
Date: Sun, 27 Sep 1992 07:39:10 GMT

gandhi@cliff.se.hou.compaq.com (Deepak Gandhi) writes:
> In article <1992Sep23.051724.11982@wb3ffv.ampr.org> howardl@wb3ffv.ampr.org (Howard Leadmon - WB3FFV) writes:
> >call SCO about this.  We were trying to integrate SCO and Netware printing,
>                                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >and the TCP/IP update did the trick...
> 
> Can you post more details on what exactly this means?  Can you send print
> jobs using SPX/IPX from an SCO UNIX box?
> 
> Thanks.
> -Deepak

Well I will Email you more information (nothing really exciting), and will 
only post if more people are interested...

-------------------------------------------------------------------------------
Internet  : howardl@wb3ffv.ampr.org	|	Howard D. Leadmon
UUCP      : wb3ffv!howardl		|	Advanced Business Solutions
TELEX     : 152252474     		|	4107 Martin Avenue
FAX       : Temporarly Unavailable      |       Baltimore, MD 21236 
PACKET    : WB3FFV @ WB3FFV.MD.USA.NA   |       Phone: (410)-661-0447
From: chuckc@hpfcdc.fc.hp.com (Chuck Cairns)
Date: Wed, 30 Sep 1992 23:36:42 GMT
Subject: Re: Unix: Cacheing EISA SCSI vs. Non-cacheing EISA SCSI Controllers
Organization: HP Fort Collins, Co.
Newsgroups: comp.unix.sysv386

/ hpfcdc:comp.unix.sysv386 / ed@maxed.amg.com (Ed Whittemore) /  9:37 am  Sep 25, 1992 /
There have been some discussions about various EISA SCSI controllers
in some of threads in this and other groups lately, but I'd like to
specifically address the question of the performance of these disk
controllers, to see if anyone can establish any advantage of the
cacheing controller over the non-cacheing, in a UNIX environment.

 I can't see any way that a cacheing board could buy you very much over a 
 non cacheing board. These cacheing controllers are the "cat's meow" in 
 the MS/DOS world where real disk-cacheing OSes have not been available.
 In-memory cacheing  versus on-io-card cacheing seems to have always won 
 in the non-DOS comparisons I've hear of.

  Look at the path a Disk Read has to go through: 

  Disk Read -> "N" Meg cache in UN*X OS -> 1 Meg cache on SCSI card.

  So before the SCSI card even GETS A SHOT at the request, it has to have 
  missed the in-memory UN*X cache. The improvement, if any, must be minmal 
  unless the cache miss rate for the UN*X cache is poor and the cache hit rate 
  for the SCSI card cache is much better. I doubt that it will be better.

  On Write, UN*X  won't even post through (depending of course on the 
  particular flavor of UN*X) unless the info is structural or unless the 
  "syncher" or "init" has flushed. I don't know how 5.4 handles this.
  I suppose  tha if the flavor of UN*X is write-thru and tries to flush 
  on each write then the cacheing controller may help. This could cause 
  problems on a power-failure because UN*X systems try to prevent corruption
  by ordering writes properly. I doubt that the cards generally do this
  since it probably interferes with speed.

  A cacheing card with a battery might be interesting but then a UPS might 
  be more effective and cheaper. 

  My $.02
  Best regards,
  cc
Newsgroups: comp.unix.sysv386,bix.sco.general
From: keith@ksmith.uucp (Keith Smith)
Subject: Re: making a new root disk in SCO Unix 3.2v4.0
Organization: Keith's Computer, Hope Mills, NC
Date: Tue, 29 Sep 92 00:29:16 GMT

In article <3791@tiamat.fsc.com> jim@tiamat.fsc.com ( IT Manager) writes:
>We have a nachine that still has an MFM drive as it's root disk, but it does
>have a SCSI host adapter installed, so I'm planning to install another
>SCSI drive that will be the root drive.  As is typical, I want to do this
>with the least amount of effort possible.  So, my current plan is listed
>below.  My question to the net is - if I perform the steps below, should
>everything still work OK?  Does anyone have other suggestions?
>
>My plan:
>
>1) connect new SCSI disk to SCSI HA and set ID to 0
>2) tell CMOS that there is no C: drive installed (this will make the new
>	SCSI drive be the C: drive)
>3) boot from installation floppies and install the minimum amount of stuff to
>	get the disk working then shutdown
>4) tell the CMOS that there IS a C: drive, and boot off the old MFM drive
>5) add the new SCSI drive to the system like any other drive, but I'll
>	make sure divvy doesn't clobber anything previously created
>6) mount the "root" filesystem from the SCSI drive as /mnt
>7) find [all root filesys dirs, except mnt] -depth -print | cpio -pdmv /mnt
>8) unmount the SCSI filesystem
>9) repeat step 2
>10) boot from the SCSI disk and test

Yup,  That should do it, but I'd recommend getting Ctar for SCO.  It has
a nice utility for a system backup and restore to different media.
(Unlike good ole 'backup').  I have used it to do exactly what you
desire with *NO* problems.  Of course I had an 8mm tape to back up the
330MB drive, and moved to a 1G.  No hitches, no glitches.

>The areas I can see that there might be trouble are with directories like
>/dev and /etc/conf/*, which have stuff that will be different because of
>the changing of the root drive type.  Also, since this system uses full
>C2 security, I wonder if all of the files associated with that will get
>copied over OK (i.e. are there any "hidden" files associated with C2 that
>the find and cpio won't take care of?).

No, but.  Be sure to run fixmog.

>
>Any help or opinions would be appreciated.
>

Why not just mount the SCSI on the MFM?

-- 
Keith Smith          uunet!ksmith!keith            5719 Archer Rd.
Digital Designs      BBS 1-919-423-4216            Hope Mills, NC 28348-2201
Somewhere in the Styx of North Carolina ...
Newsgroups: comp.unix.sysv386
From: fred@cv.ruu.nl (Fred Appelman)
Subject: Re: xlock and SVR4 (two problems)
Date: Sat, 3 Oct 1992 18:28:09 GMT
Organization: University of Utrecht, 3D Computer Vision Research Group

In <1992Oct2.233024.15308@jpl-devvax.jpl.nasa.gov> mark@phineas (Mark R. Rubin) writes:

>
>  This works correctly under SunOS 4.1.2, but always fails (even if
>  given the correct password) under SVR4.
>

This is probably caused by the password shadowing. The passwords are not
stored in /etc/passwd, they are stored in /etc/shadow. The getpwnam
only looks in /etc/passwd. Do a 

	man getspent

for more information about the subjet.

>o Fortunately, I was able to use ALT+SYSRQ,H to return to my console
>  virtual terminal after xlock grabbed my machine and wouldn't accept
>  my password.  *Unfortunately*, this ability to switch vt's defeats
>  the whole purpose of running xlock in the first place.

What problems do you see here? The fact that somebody else can login on
your console doesn't violate the securiry, does it?

	Fred
Newsgroups: comp.unix.sysv386
From: jle9162@zeus.tamu.edu (ECKHARDT, JASON LEE)
Subject: Terminals on SCO, how?
News-Software: VAX/VMS VNEWS 1.41    
Organization: Texas A&M University, Academic Computing Services
Distribution: usa
Date: Tue, 29 Sep 1992 17:02:00 GMT

Ok, I am running on a 486/33 with SCO unix 3.2.2. I'm trying to get a dumb 
terminal (vt100 specifically) connected to com2 to work with SCO as a login
terminal. if I use enable, all SCO does is hang- it's so bad I have to reboot.
Even doing a simple 'echo hello there >/dev/tty2a' hangs the machine complete-
ly!
Now before you tell me my null modem cable, terminal, or computer is faulty,
listen: I have used the terminal successfully on the same machine, same com
port, on 3 different operating systems other than SCO (these were VM/386,
Coherent unix, and DOS). Only SCO doesn't work.

I have FAS 2.09 installed rather than the stock SCO serial driver..maybe this
is to blame? I tried increasing CLIST to 400 as per fas documentation, but
no luck. Now the funny thing is, I have a modem connected to the other port,
com1. If I do 'echo atdt44444 >/dev/tty1a' it sends it the modem just fine.
I have also used kermit successfully with the modem on com1. I have
FAS installed, because the SCO serial driver wouldn't even work with the modem
or kermit.

Someone please help! I left a message on the biz.sco.* groups, but have 
received absolutely no reply from them.

Thanks, Jason.

PS: The serial card is based on ns16450 and fas reports type=* correctly.
From: winslade@cwis.unomaha.edu (John Winslade)
Newsgroups: comp.unix.sysv386
Subject: Re: Getting COM2 to work in ISC 2.0.2
Keywords: COM2 ISC 2.0.2
Date: 5 Oct 92 16:43:26 GMT
Organization: University of Nebraska at Omaha

tempel@sun490.fdu.edu (Philippe N. Tempel) writes:

>I read about the sdevice(4) file information and added a second line to my
>/etc/conf/sdevice.d/asy file.  It looks like this:

>asy	Y	1	7	1	4	3f8	3ff	0	0
>asy	Y	1	7	1	4	2f8	3ff	0	0
>							^^^
>                                   what should this be?--/

>There is an interrupt vector conflict for the COM2 device.  I forgot the
>actual end I/O address for the second entry.  Does anybody know that value?

COM2: will normally use interrupt vector 3 and ports 2f8-2ff.  Although I
have switched to the HUB card and don't use the original COMx: ports, I
think those values should work.
 
Good day        JSW
From: larry@gator.rn.com (Larry Snyder)
Newsgroups: comp.unix.sysv386
Subject: Re: Unix "Lite" is not so light
Date: 3 Oct 92 22:47:09 GMT
Organization: The Gator Conferencing System 219-289-3745

peter@ferranti.com (peter da silva) writes:

>Base system running in 2MB RAM, 40 MB hard disk. Compilers or X in 4 MB.

You want all of 1992's features to run on 1987 hardware.

-- 
Larry Snyder                                    internet: larry@gator.rn.com
keeper of the Gator                                  uucp: uunet!gator!larry
From: rmk@rmkhome.UUCP (Rick Kelly)
Newsgroups: comp.unix.sysv386
Subject: Re: Unix "Lite" is not so light
Date: 4 Oct 92 04:57:16 GMT
Reply-To: rmk@rmkhome.UUCP (Rick Kelly)
Organization: The Man With Ten Cats

In article <id.RCRT.WZ@ferranti.com> peter@ferranti.com (peter da silva) writes:
>In article <2979@news.cerf.net> jde@esix.everex.com (Jeff Ellis) writes:
>> BTW What features are important for you people to buy 4.2? 
>
>Price competitive with OS/2 and NT.

Big price difference.  NT may end up in the $500+ range.

>Base system running in 2MB RAM, 40 MB hard disk. Compilers or X in 4 MB.

I hope that somewhere out there, in a dank basement, surrounded by junk
food wrappers and empty coffee cups, is a person who is obsessed with
developing a GUI system that is compatible with X-11 but 1/4 the size.

And I hope he's almost done. :-)

-- 

Rick Kelly	rmk@rmkhome.UUCP	unixland!rmkhome!rmk	rmk@frog.UUCP
Newsgroups: comp.unix.sysv386
From: jason@oaknet.chi.il.us (Jason Vanick)
Subject: Problem with floppy drives on at&t svr3.2.1
Organization: OAKNET - public access unix
Date: Thu, 1 Oct 1992 00:26:54 GMT

I have been having a problem with my floppy drives for somewhile now. I can
read and write to disks fine with cpio,tar,and almost anything else that will
write to a floppy, I can even make a file system on a floppy, but I cannot
format any floppies... this occurs on both the 3.5" and 5.25" drives on my
386sx/20mhz running AT&T Unix System V release 3.2.1. I've tried copying the
format command off of the original floppies, but that doesn't work... here's
what occurs if I try to format a disk.
# format -v /dev/rdsk/f0t
formatting.
Formatted 0 track: Please check floppy density
#
I'm positive that this is a high density floppy and it formats perfectly on
other machines (dos, sco unix, interactive)
Does anybody have any ideas what might be happening?
Thanks,
-- 
----------------------------------------------------------------------
Jason Vanick               | Operator of Oaknet - public access unix
jason@oaknet.chi.il.us     |         +1-708-425-8739 2400 Baud N 8 1 
----------------------------------------------------------------------
From: Thomas.Pfeiffer@p5.f2002.n241.z2.fidonet.org (Thomas Pfeiffer)
Newsgroups: comp.unix.sysv386
Subject: DOS Files
Date: 23 Sep 92 13:05:00 GMT
Article-I.D.: fast.717504040.F00003

Hi everybody,
I am working with SCO UNIX R3.2 on a Tandon 386 PC.
How can an UNIX application read files from a DOS
floppy disk drive ?

Is there any possibility to use doscp or something
like that, or a mechanism such as pcfs on SUN stations ?

Thanx in advance
Jim.

(2:241/2002.5)
From: tempel@sun490.fdu.edu (Philippe N. Tempel)
Newsgroups: comp.unix.sysv386
Subject: Trouble with idbuild(1M) in ISC 2.0.2
Keywords: idbuild ISC 2.0.2
Date: 2 Oct 92 00:19:18 GMT
Organization: Fairleigh Dickinson University

While using kconfig(1) to rebuild the kernel, I got the folowing error
message from idbuild(1M):

ERROR: '/etc/conf/pack.d/cpyrt/space.c' will not compile properly

I checked out the space.c file and its include file config.h for any syntax
errors.  I couldn't find any except for nested comments which I removed.
That was not the problem, however (I had a feeling it wasn't...).  Has
anybody ever run into this bug (or feature :-))?

While I'm on the kconfig topic, are there any other bugs with this and other
related utilities that I should know about?

Thanks,
Philippe

P.S. Thanks to all who helped me with the COM2 asy settings!
From: marrevola@iris-dcp.es
Newsgroups: comp.unix.sysv386
Subject: Colorado Jumbo250 tape drivers for SCO.
Date: 5 Oct 92 13:51:30 +0100
Organization: REDIRIS, Red Nacional de I+D

FTP site for Colorado Jumbo250 tape backup under SCO Unix System V?

I`ll be very grateful.

manolo@taf.fundesco.es


Newsgroups: comp.unix.sysv386
From: darcy@druid.uucp (D'Arcy J.M. Cain)
Subject: Re: Everex STEP display driver
Date: Mon, 5 Oct 1992 11:54:58 GMT
Organization: D'Arcy Cain Consulting

freb@goldfnch.mv.com (Karl Freburger) writes:
>I've seen a few requests for this driver go by, and I happen to have a copy
>of it, and it's pretty small, so here it is.  I hope that Steve Friedl
>(who appears to be the author) won't be upset by me doing this.  And

I reworked Stephen's code to add a few features.  It was submitted to
comp.sources.unix but it was only 3 or 4 months ago so don't expect it
soon.  Anyway you can ftp it from uunet.ca in distrib/druid/led.shar.Z.
Here is the Readme:


This driver is based on the driver written by Stephen J. Friedl
(friedl@mtndew.Tustin.CA.US).  I have made a few modifications:

  - The Makefile has been completely revamped.  Many small files
    are now created directly rather than being part of the shar
    distribution.  Type 'make what' for a list of the more
    important make options.

  - All code is fully ANSI compliant.

  - The driver supports multiple devices with device minor numbers
    corresponding to priority on the LED display.

  - The write function takes a regular stream of characters and
    displays them in scrolling fashion.  An ioctl performs the
    function performed by the original write function.

  - The ledtime program has been modified to use the ioctl so that
    the display of time doesn't chase across the LEDs.  A makefile
    option allows you to select 12 or 24 hour time styles.

  - The ledtime function uses /dev/ledclock which is minor 0.  This
    allows other programs to temporarily use the LEDs without
    having to stop and restart the clock display.

Note that if you do not have an ANSI compiler you will have to run
this through unproto or change it by hand.  I have attempted to cast
everthing that may cause problems due to any such change.

D'Arcy J.M. Cain
darcy@druid.com

-- 
D'Arcy J.M. Cain (darcy@druid.com)  |
D'Arcy Cain Consulting              |   There's no government
Toronto, Ontario, Canada            |   like no government!
+1 416 424 2871          DoD#0082   |
From: shih@madrone.eecs.ucdavis.edu (The Nomad)
Newsgroups: comp.unix.sysv386
Subject: Memory exhausted error?
Date: 29 Sep 92 06:04:12 GMT
Distribution: comp.unix.sysv386
Organization: U.C. Davis - Department of Electrical Engineering and Computer Science

Hello Netlander:

I am trying to compile ups on SVR5 and ran into this error

/usr/local/lib/gcc-lib/i386-att-sysv4/2.2.1/cpp: Memory exhausted.

I believe that there should be a variable I can set for max memory?
Any help/info is greatly appreciated!

Alan
From: "richard hajinlian" <richard.hajinlian@channel1.com>
Newsgroups: comp.unix.sysv386
Subject: unix sugestions on pc
Date: 1 Oct 92 03:54:57 EST
Reply-To: "richard hajinlian" <richard.hajinlian@channel1.com>
Distribution: comp
Organization: Channel 1 Communications

I'm looking for suggestions on which unix OS to use.  Any comments
will be greatly appreciated.  My hardware consists of:
386 40mhz cpu, 8m ram, 1gb disk, adaptec 1542b with a ati vga wonder +.
I'm looking for suggestions on a lan card.

I wish to learn X windows (motif if possable), TCP/IP sockets (I'll
get the second machine soon  $$$$ ouch!).  It would be nice if there was
a c(++) environment also.  And all this (TCP/IP and above software)
for under $1,000?  Tall order?

By the way .....snicker....can I use os2 boot mgr to run this stuff?

Thanks again in advance.

Rich (I don't know which platform to write my pencil tracking
      program in) Hajinlian.
--
Channel 1 (R)   Cambridge, MA
From: mpdillon@uuisis.isis.org (Michael Dillon)
Newsgroups: comp.unix.sysv386
Subject: Digiboard modem connections
Date: 29 Sep 92 07:07:51 GMT
Organization: International Shared Information Service (Ottawa)

I have two customers with modems hanging off of Digiboard
CX/CON concentrators. This model of Digiboard uses 16550A uarts
so it can handle top speed on all ports simultaneously. We
use Digiboard's reccommended 9 wire configuration on a 10 pin
RJ-45 connector. This, of course, includes full hardware
flow control. The modems are USR Courier v.32bis/v.42bis models
and the flow control is enabled on their end. The gettydefs
are set IXON -IXANY IXOFF  only so that users can use Ctrl-S/Ctrl-Q
interactively. Also -CLOCAL CTSFLOW RTSFLOW to turn on the
hardware flow control EXTB on Xenix, B38400 on SCO UNIX to
enable top speed that the modem is capable of pumping out
when transferring text with v.42bis compression. (This happens if
you are reading news and you press ENTER repeatedly about 50
times in a second. The text just flies through the link at 
nearly 3840 cps and you can capture it and read later).
 
This configuration works flawlessly with interactive links
from my home PC, with UUCP links to branch offices running
Xenix, and with Z-modem between my home system and the host
or from the host out to a branch (I use XC and SZ/RZ when I
dial from the host to a branch during working hours). 
 
Until we did this we had so many problems that the modem links
were virtually unusable. Now they work. Even though one branch
is still using Xenix 3.2.2 with a 16450 uart on tty1A and gets
lots of errors and retries, the data still goes through. Before
using CTSFLOW RTSFLOW on the host it wouldn't go.

If you want to set up hardware flow control on tty1A or 2A you
will probably only be able to use CTSFLOW -RTSFLOW. I have
come across one configuration (maybe a Digiboard PC/Xe???) where
I had to do the opposite -CTSFLOW RTSFLOW.
 
I used to believe that X-ON/X-OFF was sufficient but when I started
using speeds above 9600 bps I found that I was WRONG WRONG WRONG.