HDTenEightyP/NetNews huggingface dataset:
From: bill@bilver.uucp (Bill Vermillion)
Subject: Re: How does a mortal become a UNIX WIZARD ?
Organization: W. J. Vermillion - Winter Park, FL
Date: Sun, 22 Nov 1992 18:11:00 GMT

In article <1992Nov22.102949.94692@slate.mines.colorado.edu> mbarkah@slate.mines.colorado.edu (Ade Barkah) writes:
>Simon Tooke writes:

>: Ade Barkah writes:

>: > So, oh, mylord, how does a mortal become a Unix Wizard ?

>: Wizard Pills.

>Now, man, where'chu get them 'Wizard Pills' stuff from. Gemme
>a-o 'bunch of them 'izzard Pils and I sho' can sell 'em faster
>then crack.

Wizard Pills come from the same distributor as Smart Pills.

And if you don't know the story about 'smart pills' - I feel
sorry for you :-)

-- 
Bill Vermillion - bill@bilver.oau.org  bill.vermillion@oau.org
                - bill@bilver.uucp 
                - ..!{peora|tous|tarpit}!bilver!bill

Newsgroups: comp.unix.sysv386
From: larry@gator.rn.com (Larry Snyder)
Subject: Re: SCO uugetty makes dialout flaky
Organization: The Gator Conferencing System 219-289-3745 
Date: Sun, 15 Nov 1992 18:21:12 GMT

chip@chinacat.unicom.com (Chip Rosenthal) writes:

>Can anybody suggest a workaround for this?  Can anybody suggest
>a reasonable getty to use?  (And how come nobody has stumbled on
>this before?  My excuse is that I never tried to do any heavy
>duty comm work with SCO Unix until this week.)

karl@ddsw1.msc.com has a replacement for getty called TROLL
which does a lot more than getty -- consuming less memory.

TROLL will handle all the locking, accept and act upon modem
return (result) codes (ie: CONNECT FAST, etc) with a complete
installation defined script

-- 
Larry Snyder                                    internet: larry@gator.rn.com
keeper of the Gator                                  uucp: uunet!gator!larry
Newsgroups: comp.unix.sysv386
From: ed@maxed.amg.com (Ed Whittemore)
Subject: Re: How to setup ISC3.0 for use with >16MB ??
Organization: American Micro Group, Ft. Lee  NJ
Date: Sat, 21 Nov 1992 14:57:12 GMT

In article <sledge.722194151@messua> sledge@messua.informatik.rwth-aachen.de (Thomas Bueschgens) writes:
>
>Hi folks,
>
>the subject explains my question good. Just today I've bought my 486/33
>16 MB and in total I'm in possession of 20 MB. So far, so good.
>The BIOS and DOS (flames > /dev/blackhole) just recognizes the total
>amount of memory, but using ISC I just get 16 MB.
>What about my 4 MB on bank Nr 0 ??
>A kernel with >16 - 32 MB is allready build, but no change.
>
>Anybody out there who just had this problem , too ??
>
>Any help appreciated, please via Email.
>
>Thanks in Advance    Thomas
>

This question seems to get answered twice a week. Anyway with ISC 3.0
on ISA machines you do NOT get more than 16 MB--it wiil not be
recognized. On EISA machines with and IDE or EISA SCSI or other disk
controller not limited to the first 16 MB of memory, you can get more,
up to 512 MB, I think. But if you have an ISA SCSI board, e.g., an
Adaptec 1542B that does DMA and doesn't have 32 bit addressing, ISC
will recognize this, and truncate available memory to 16 MB.

-- 
Ed Whittemore   uunet!maxed!ed   ed@maxed.amg.com
American Micro Group, Inc.   201-944-3293
Newsgroups: comp.unix.sysv386,comp.unix.questions
From: jboggs@umaxc.weeg.uiowa.edu (John D. Boggs)
Subject: Re: How does a mortal become a UNIX WIZARD ?
Organization: University of Iowa, Iowa City, IA, USA
Date: Fri, 20 Nov 1992 14:19:23 GMT

From article <Mf30lBO00VI=41tGYT@andrew.cmu.edu>, by Geoffrey Spear <gs32+@andrew.cmu.edu>:
> 	Also, read the jargon file and start using obscure hacker jargon all
> the time.  It will at least make you *seem* to be a wizard of some sort,
> at least to those who have no idea what you're talking about and who are
> afraid to admit it :)

Plus there's the fact that some poet (Auden?) said that we all pretend to
be something before we really are it, so yeah, pretending to be a Unix 
wizard is a step in the right direction.

> "You're redlining my bogometer!"
                       ~~~~~~~~~
Hey!  You making fun of my name??!

-John D. Boggs     uunet!erato!jdb

Xref: sparky comp.unix.sysv386:16732 comp.unix.sys5.r4:587
From: davidsen@yeti.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.sysv386,comp.unix.sys5.r4
Subject: Installing non-standard net cards on Dell
Date: 23 Nov 92 17:25:54 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY


  I had a little learning experience this weekend trying to install a
WD8013 (16 bit enet card) at a non-standard address with Dell V.4 rel
2.2. The stuff in the manual is all correct, but you might spend a lot
of time reading between the lines on this. Also, if you do it wrong it
blows away your root filesystem (I verified this three times), so you
might want to see how I did it.

Why do it fancy?
================

  Several of my home systems share a configuration which allows me to
minimize hardware cost, but which uses up the interrupts on the 8 bit
bus. My config looks like this:

	int	card

	2	bus mouse
	3	serial (16550)
	4	serial (16550)
	5	tape controller (at io 338)
	6	ESDI disk
	7	parallel

	10	wdn net card
	11	aha1540

  Because I have no room to use the low interrupts Dell checks as
standard, I wanted to put the io at 240, the int at 10, the transfer
buffer at d0000.

How to do it
============

  These steps in this order:
	1. Remove the card and install Dell UNIX. If you have it
	   installed you have done this.
	2. Edit the sdevice.d/wdn file to force the int and io
	   addresses. See the Dell manual for the format, My
	   last five fields were
		10	240	25f	d0000	d3fff
	3. Edit the sdevices.d/eth586 file to disable all devices.
	   Change the first Y to an N.
	4. Run idbuild
	5. Shutdown the system - installs the new kernel
	6. Boot the system - builds kernel environment
	7. Shutdown the system (again)
	8. Power off
	9. install the card

  Steps 6 and 7 are not really obvious from the documentation!

Notes:

  I couldn't make this work by editing the wdn/space.c file in the
obvious way, although I certainly tried. I got the kernel in a condition
where shutdown would work with the card installed.

  Alway back up your system when doing something simple like this. Even
though you know it's trivial and you won't hurt anything... do it
anyway. My incremental produced about 280MB of stuff I had changed since
the last full dump five weeks agao. I would rather load from tape than
regenrate that info (computer generated images).

  About the third time I reinstalled, I begain to wonder if I could
patch the boot floppy to not retension the tape every flaming time I ran
install. I actually did a physical copy of the floppy to the hard disk
of another machine and looked for the retension stuff. I finally left it
alone, having pleanty of time Sunday afternoon to go watch the football
games.

-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
Newsgroups: comp.unix.sysv386
From: ed@maxed.amg.com (Ed Whittemore)
Subject: Re: How to determing the size of you swap space?
Organization: American Micro Group, Ft. Lee  NJ
Date: Mon, 23 Nov 1992 00:28:59 GMT

In article <1eg9k5INNsuj@uwm.edu> peter@miller.cs.uwm.edu (Peter J Diaz de Leon) writes:
>When installing Unix, how does one determine the
>size of the swap space?  Also is it possible to
>figure out once you have allocated swap space
>how much of it is being used?
>
>
>-Peter
>(peter@miller.cs.uwm.edu)

You need swap space for 2 reasons:

1) to swap to

2) to write out a dump in case of a panic and crash

If you are running your system with some processes swapped and your
system comes down, and your swap space is not at least equal to the 
size of swapped processes and the amount of memory you have, your
panic dump will happily write over the end of your swap space and
into your next filesystem.

Pick a swap space size that accommodates both of the above, at least
1.5 X memory, maybe 2 X.
-- 
Ed Whittemore   uunet!maxed!ed   ed@maxed.amg.com
American Micro Group, Inc.   201-944-3293
Newsgroups: comp.unix.sysv386
From: staceyc@sco.COM (Stacey Campbell)
Subject: Re: Video problems with ODT 2.0
Organization: The Santa Cruz Operation, Inc.
Date: Thu, 19 Nov 1992 20:03:53 GMT


In article <1992Nov19.142019.17840@crd.ge.com> davidsen@crd.ge.com (bill davidsen) writes:
>  We recently tried to install the advanced video drivers on an SCO ODT
>2.0 system and got a make failure partly through the kernel build. It
>seems that the sdevice file has a few lines of garbage in it, and when
>we clear the garbage the make process nicely puts them back in.

The AGA EFS doesn't get into sdevice.d territory, and we've never seen
this problem in the (seemingly endless) test installs we did before we
shipped this EFS.

>  We were using sysadmsh to do it, and we've installed the same software
>on two other identical machines, so I don't see much room for
>incompatibility or operator error.

Do you have the same problem on the other machines?

>  If anyone has an idea how to salvage this machine other than a
>complete reinstall and recustomization, please let me know.

Your sdevice file is a conglomeration of the files in /etc/conf/sdevice.d,
it's pretty likely that one of those files contains the mess you are
seeing.  If you manage to find the culprit, fix it up, then relink the
kernel.  It would also be interesting (at least for me ;-) if you could
reinstall the AGA EFS and see if the problem reappears.  Other than
asking the kernel for privileges to scribble on physical memory and
access i/o ports (/etc/conf/pack.d/cn/class.h) the AGA EFS generally
keeps clear of the kernel directories.
-- 
          Stacey Campbell - staceyc@sco.com - uunet!sco!staceyc
Newsgroups: comp.unix.sysv386,comp.unix.sys5.r4
From: sam@csi.compuserve.com (Sam Neely)
Subject: Re: tar problems
Organization: CompuServe Incorporated
Date: Tue, 17 Nov 1992 17:47:14 GMT

In article <1992Nov12.164004.9850@netnews.whoi.edu> gie@charon.er.usgs.gov (Gerald I. Evenden) writes:
>I am having problems with tar files created under Dell SVR4-i2.2 not
>un-tar-ing properly on other systems.  More specifically, directories
>in the tar file will *NOT* expand to a directory, but instead get
>created as an executable, zero length file.  Some detective work has
>shown that the name field in the SVR4 tar is not suffixed with a "/"
>as in a non-SVR4 tar and mode value also differs.  I have also used the
>latest version of GNU's cpio with "-H tar" and get the same results
>as with the SVR4 tar.  Foreign tars have always been successfully
>processed by SVR4, but the other direction is a bust.
>
>This seems to be a bug/problem related to issue 2.2 because I do not
>remember having this trouble with issue 2.1 last spring.
>
>It is interesting that GNU cpio and Dell tar tend to agree on format.
>
>Any comments or workarounds would be appreciated.

There is a new version of tar for issue 2.2 on dell1.dell.com in
the support2.2 directory, if memory serves me correctly.  Snarf
and install this and you should be happier.  (I sure was after I
installed...)

	- Sam
-- 
Sam Neely, CompuServe Incorporated                  +1 614 457 8600 (voice)
5000 Arlington Centre Blvd, Columbus, OH  43220     +1 614 457 0348 (FAX)
Electronic Mail:  InfoPlex: >CSI:SAM      Internet: SAM@CSI.COMPUSERVE.COM
To err is human, to forgive is against company policy
Newsgroups: comp.unix.sysv386
From: jrohr@rasc.com (Jay J. Rohr)
Subject: Re: What's happening to ISC UNIX?
Organization: Rohr Applied Systems Corp, Sterling VA
Date: Sun, 22 Nov 1992 14:27:16 GMT

In article <1992Nov22.051548.13038@toolz.uucp> todd@toolz.uucp (Todd Merriman) writes:
>>I understand that ISC-3.0 has since been released. Is it an improvement over
>>the previous one? Is this the latest version available?
>
>3.0 is the latest version.  The takeover by SunSoft has confused

3.0.1 is the latest release

>
>No.  And, there is no ksh.

ksh is included, i believe in 3.0 as well

>
>>Has VP/ix been improved to provide Windows 3.0/3.1 support?
>
>The documentation states that Windows can be run in real-mode,
>but I found that the Windows 3.1 install program crashes VPIX
>immediately.  VPIX performance has decreased noticably since 2.2.   
>

VPIX will run Windows 3.0 but not 3.1 ( ISC 2.2 would also run Windows 3.0
with an applied patch - sorry I do not remember the number.)
I am told that an update to VPIX is in the works. It may run Windows 3.1 but
protected mode OS within protected mode OS will be tricky.

>>Is there driver support for CD-ROM drives?
>
>The High Sierra file system is supported (but not from within VPIX).
>

have not tried this yet 

>
>I was so disatisfied with my upgrade to ISC 3.0 that I asked
>SunSoft for my money back, and I explained to them in writing

I have been having some problems (the jury is still out as to the resolution)
but Tech Support has elevated the problem to the developers to try and get
resolution. If I do not get resolution I will join the flame.

-- 
jrohr@rasc.com                  +---+    ^    +----  +----
Jay J. Rohr                     |   |   / \   |      |
Rohr Applied Systems Corp.      |---+  /---\  +---+  |
Sterling, Va.                   |  \   |   |      |  |
Newsgroups: comp.unix.sysv386
From: fisher@ncselxsi.uucp (Chuck Fisher)
Subject: UPS, SCO and automatic shutdown
Organization: National Computer Systems, San Jose, CA  95131
Date: Mon, 16 Nov 1992 15:16:30 GMT

We're currently running an Everex system with a 486/33 CPU and SCO Unix
3.2.4.  We're considering purchasing a UPS (recommendations, anyone?)
and was wondering if any one has implemented an automatic shutdown (or
halt) when the UPS detects a power outtage.

We want to set up Unix-based turn-key systems for end-users who have
little computer expertise with high reliability.  UPS is one way of
acheiving that goal by ptentially allowing for a "smooth" shutdown of
the system.  Automatic backups using DAT cartridges is another aspect
we're considering.

Thanks,
Chuck
-- 
Chuck Fisher                                        (800) 359-7997 Work
ncselxsi system administrator                       (415) 964-2819 Home
uucp:  ...!netcom!ncselxsi!fisher
Newsgroups: comp.unix.sysv386
From: fred@genesis.demon.co.uk (Lawrence Kirby)
Subject: Using 16550AFN with SCO 3.2.4 
Distribution: world
Organization: BT
Date: Mon, 16 Nov 1992 01:08:08 +0000


In article <46W8U3G@geminix.in-berlin.de> gemini@geminix.in-berlin.de writes:

>
>jochen@busybit.mrz.sub.org (Jochen Fahrner) writes:
>
>>In article <1992Nov08.112542.1189@lasernet.co.za> aris@lasernet.co.za (Aris> Stathakis) writes:
>>
>>   >Q2:  Is it possible that this will solve my problem?
>>
>>   I'm running two V.32 modems on an AST 4-port that uses 16450's and I
>>   don't lose any characters (running stock 3.2.2 drivers).  I know of
>>   people that did have problems and installed 16550's and it helped.
>>
>>   You could also try using FAS under 3.2.4 which would improve performance
>>   even more, and give you full-duplex RTS/CTS flow control.
>>
>>Don't use FAS with SCO Unix ! You will get a lot of problems and you
>>really will not need FAS !
>
>The kernel crash problems are gone with FAS 2.10, as far as I know. And
>the FAS problem you've reported wasn't confirmed by any other SCO UNIX
>user. And I myself also couldn't reproduce it. So I declared it a site
>specific problem and didn't persue it any longer. If this bugs you that's
>your problem. However, please don't jump to conclusions and claim that
>your (still unidentified) problem applies to all other SCO UNIX machines
>in the world. There are lots of SCO UNIX users who have FAS installed
>and don't have any problems with it.
>
>>The SCO sio driver *has* 16550 Support.
>>Since release 3.2v4.0 Fullduplex hardware flow control is also
>>implemented.
>
>I'd say that FAS still has many important features that sio doesn't have.
>It may be true that the person who started this thread doesn't need FAS
>for his/her application, but the assumption that FAS doesn't gain you
>anything on SCO UNIX in general would be wrong.
>
>For instance, does sio allow 57600 and 115200 bps? Does it have built-in
>modem line sharing for dialin and dialout (no uugetty hack necessary)?
>Does it have DCD drop sensing on the dialout device, too? This is
>important for uucico dialouts.
>
>      Uwe
>

I stumbled on this thread having just get an Internet connection. I did
mail you from Compuserve a week or 2 ago about problems I'm having with FAS
and SCO 3.2.2.

FAS 2.09 locks the machine up occasionally so I stopped using it. FAS 2.10
desn't seem to lock the machine up but it does sometimes lock the port up
and the process with it. Control signals DTR,DSR,RTS,CTS are all high and
no amount of kill -9 or >> portname will free it. I never get this problem
under FAS 2.09 or SCO's driver. The problem seems to occur when the port
is transmitting data rather than receiving. A modem dialler is particularly
badly hit by it.

-----------------------------------------
Lawrence Kirby | fred@genesis.demon.co.uk
Wilts, England | 70734.126@compuserve.com
-----------------------------------------
Xref: sparky comp.unix.sysv386:16691 comp.unix.sys5.r4:576
From: ric@cs.arizona.edu (Ric Anderson)
Newsgroups: comp.unix.sysv386,comp.unix.sys5.r4
Subject: SUMMARY: Making stty werase work in a user program.
Keywords: WERASE, RPRNT
Date: 22 Nov 92 06:32:42 GMT
Followup-To: /dev/null
Organization: U of Arizona CS Dept, Tucson

In article 28831, I wrote:
- 
- On two different SVR4's I use (ESIX and DELL), the stty word erase
- character (werase, default is Control-W) and the stty reprint line
- character (rprnt, default is Control-R) (described in termio(7) as
- well as in stty(1)) are not processed when a simple program using
- ordinary "fgets()" calls is run.
- 
[stuff deleted]
- Does anyone know what settings will make werase and rprnt function
- as advertised in programs other than ksh?
- 
The correct answer came from:
    guy@auspex.com (Guy Harris)
who said in part:
- From the SunOS 4.1.1 TERMIO(4) manual page (I think the SVR4 "ldterm"
- "tty driver" STREAMS module is derived from the SunOS 4.1[.x] one):
- 
-      If IEXTEN is added to the local modes (this is the default),
-      then all of the special characters are in effect.  If IEXTEN
-      is cleared from the local modes,  then  only  the  following
-      POSIX.1  compatible  specials  are  seen  as specials: INTR,
-      QUIT, ERASE, KILL, EOF, NL, EOL, SUSP, STOP, START, and CR.
- 
- So, unless IEXTEN is set, none of the control characters not mentioned
- in POSIX 1003.1 work; neither "word erase" nor "reprint" are mentioned
- there.  (The idea is that any program that wants to make absolutely,
- positively, sure that the tty driver isn't intercepting any characters
- not mentioned in 1003.1, so that it doesn't get surprised by control-R,
- say, not getting through the tty driver to it, would turn IEXTEN off.)
- 
	stty iexten
under DELL SVR4 did indeed do the trick. 

Ric (<ric@cs.arizona.edu> "Ric Anderson", speaking for himself)
Newsgroups: comp.unix.sysv386
From: sts6f@vortex.mech.virginia.edu (Sonya T. Smith)
Subject: enscript on SVR4
Organization: University of Virginia
Date: Mon, 23 Nov 1992 19:04:50 GMT

I would paareciate it if someone would email my the address of a site where I can get
a copy of enscript for SVR4.  This is my favorite text-2-ps formatter and I would like
to have a copy for my machine instead of uploading to the nearest Sun or RS6000.

Thanks in advance,
Sonya
-- 
-------------------------------------------------------------------------------
S.T. Smith                           |"I am afraid that I rather give myself
Department of Mechanical,            | away when I explain. Results without    
   Aerospace and Nuclear Engineering | causes are much more impressive"
University of Virginia               |
Charlottesville, VA 22901            | - Sherlock Holmes                       
-------------------------------------------------------------------------------
Newsgroups: comp.unix.sysv386
From: teddybur@netcom.com (John Sanger)
Subject: /boot & /dos
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
Date: Mon, 16 Nov 1992 00:07:49 GMT

The published solution to the >32 meg dos partition boot problem is to copy
the SCO Unix r3.2.4 '/boot' & '/dos' files into my SCO Xenix r2.3.4 root
directory but for those of us who do not have a copy of SCO Unix it is not
possible to accomplish.

So could someone who has SCO Unix r3.2.4, please, email them to me.  I want
to make use of a >32 meg dos boot partition in my upgrade to a Intel 486
cpu and 543 meg hd.

Thanks for you efforts in helping with this problem.



Ciao!
	John S. :^)
	teddybur@netcom.com
__

Newsgroups: comp.unix.sysv386
From: andy@awds.imsd.contel.com (Andy Moskoff)
Subject: ISC 3.0 and ATI Graphics Ultra
Keywords: Keyboard, Xgp, ATI Ultra
Organization: GTE Federal Systems, Westlake Village, CA
Date: Thu, 19 Nov 1992 17:22:57 GMT


Hi,


Here is an interesting problem (and unsolved) with my ATI Graphics Ultra card and
the ISC 3.0 UNIX system. Yesterday, I built and installed a kernel for use with the
ATI card. I also, built the Xgp X11 server. I ran X11 (I use the tvtwm) with no problem.
However, when switching between virtual terminals (an X session and a console session)
the keyboard hung up. I noticed this when going BACK to the X11 session. To solve
the problem albeit in a very crude manner, I pulled out the keyboard connector and
plugged it back in, viola!, keyboard works. Now, does anyone know what could be the
problem? Did I configure the ATI card incorrectly? I called SunSoft (Interactive)
they said that ISC 3.0 doesn't _officially_ support 8514/A boards!! WHAT!?!?!?!?
I was mislead by the sales rep. They also said that ISC 3.01 does support the 8514/A
cards. Here's my setup, any help would be appreciated:


	ADAPTEC 1542b I/O Base: 330 DMA: 7 IRQ: 11
	3COM ETHERLINK II I/O Base: 300 Memory Base: C8000 DMA: 1 IRQ: 3
	SERIAL PORTS: 3F8, 2F8 IRQ: 5
	PARALLEL PORT: 378 IRQ: 7 
	ATI VIDEO PORT: 2E0-2E8 Memory Base: A0000-C7FFF IRQ: Not Jumpered

Please send e-mail for responses. Thanks in advance.

-Andy
From: davidsen@ariel.crd.GE.COM (william E Davidsen)
Newsgroups: comp.unix.sysv386
Subject: Re: Using 16550AFN with SCO 3.2.4
Date: 19 Nov 92 14:13:35 GMT
Reply-To: davidsen@crd.ge.com (bill davidsen)
Organization: GE Corporate R&D Center, Schenectady NY

In article <46W8U3G@geminix.in-berlin.de>, gemini@geminix.in-berlin.de (Uwe Doering) writes:

| >Don't use FAS with SCO Unix ! You will get a lot of problems and you
| >really will not need FAS !

  Well, FAS solved problems switching between incoming and outgoing
calls, and uses less CPU than the SCO driver, but if you don't mind
fighting with lines which don't switch back to incoming after an
outgoing call, and only have one or two high speed lines, then you don't
*need* FAS.

| For instance, does sio allow 57600 and 115200 bps? Does it have built-in
| modem line sharing for dialin and dialout (no uugetty hack necessary)?
| Does it have DCD drop sensing on the dialout device, too? This is
| important for uucico dialouts.

  Sounds right to me. I can use some really uucp unaware software due to
extra devices. No lock files needed, thanks, all done at the driver
level. I can't say that the SCO driver is *bad*, but I can't rate it
higher than adequate, either. The one thing about the SCO driver is that
it seems to support more types of serial device than FAS, although you
have source with FAS.

  Sure wish FAS run with Linux.
-- 
bill davidsen, GE Corp. R&D Center; Box 8; Schenectady NY 12345
    Keyboard controller has been disabled, press F1 to continue.
Newsgroups: comp.unix.sysv386