HDTenEightyP/NetNews huggingface dataset:
From: walter@lamar.ColoState.EDU (Brian J Walter (Brewing Chemist))
Subject: 386bsd cksum problems
Date: Thu, 21 Jan 1993 16:07:21 GMT
Organization: Colorado State University, Fort Collins, CO  80523

Howdy!
	Has anyone had problems with cksum errors when downloading the
	dist sets to an IBM RS/6000?  I downloaded all three dist sets
	from a couple different sites (agate and gatekeeper) and get
	a cksum error on EVERY file when running dcksum < MANIFEST.  Is
	the cksum command under AIX [3.2 I believe] operating on a 
	different algorithm, or, as a friend suggested, are all IBM
	machines just evil?

	-Brian

	P.S. I downloaded the rawrite and dist.fs files and created my
	     bootable, and all works fine.  Also, Yes, I did use ftp in
	     binary mode.

Brian J Walter            |Science, like nature, must also be tamed|  Relax,
Chemistry Graduate Student|with a view towards its preservation.   |Don't Worry
Colorado State University |Given the same state of integrity, it   |  Have A
walter@lamar.colostate.edu|will surely serve us well. -N. Peart    | Homebrew!

Brian J Walter            |Science, like nature, must also be tamed|  Relax,
Chemistry Graduate Student|with a view towards its preservation.   |Don't Worry
Colorado State University |Given the same state of integrity, it   |  Have A
walter@lamar.colostate.edu|will surely serve us well. -N. Peart    | Homebrew!
Newsgroups: comp.unix.bsd
From: bde@runx.oz.au (Bruce Evans)
Subject: [386BSD] Bug + fix: NAME_MAX off by 1
Organization: RUNX Un*x Timeshare.  Sydney, Australia.
Date: Fri, 22 Jan 93 18:21:48 GMT

File names of length NAME_MAX do not work in 386BSD-0.1.  Names of length
NAME_MAX - 1 are OK.  Reducing NAME_MAX by 1 to 254 would not help - it
would invalidate the documentation and reduce the actual maximum by 1.

This program demonstrates the bug:

---
NAME_MAX-test.c
---
#include <errno.h>
#include <fcntl.h>
#include <limits.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <unistd.h>

int errors;

void test(size_t component_length, int expect_error);

int main(void)
{
    test(NAME_MAX, 1);
    test(NAME_MAX + 1, 0);
    exit(errors ? 1 : 0);
}

void test(size_t component_length, int expect_error)
{
    int fd;
    char *name;

    name = malloc(5 + component_length);
    if (name == NULL)
    {
	perror("malloc");
	abort();
    }
    sprintf(name, "/tmp/%0*d", (int) component_length, 0);
    fd = creat(name, 0666);
    if (fd >= 0) {
	(void) unlink(name);
	fprintf(stderr, "%s: length %d didn't cause an error\n",
		expect_error ? "  OK" : "oops", (int) component_length);
	if (expect_error)
	    ++errors;
    }
    else {
	fprintf(stderr, "%s: length %d caused error `%s'\n",
		!expect_error ? "  OK" : "oops", (int) component_length,
		strerror(errno));
	if (!expect_error)
	    ++errors;
    }
}
---

This might be a fix:

*** vfs_lookup.c~	Wed Dec 25 09:24:09 1991
--- vfs_lookup.c	Tue Jan 19 21:25:50 1993
***************
*** 275,279 ****
  		ndp->ni_hash += (unsigned char)*cp;
  	ndp->ni_namelen = cp - ndp->ni_ptr;
! 	if (ndp->ni_namelen >= NAME_MAX) {
  		error = ENAMETOOLONG;
  		goto bad;
--- 275,279 ----
  		ndp->ni_hash += (unsigned char)*cp;
  	ndp->ni_namelen = cp - ndp->ni_ptr;
! 	if (ndp->ni_namelen > NAME_MAX) {
  		error = ENAMETOOLONG;
  		goto bad;
-- 
Bruce Evans  (bde@runx.oz.au)
From: julian@tfs.com (Julian Elischer)
Subject: Re: kernal switcher?
Organization: TRW Financial Systems, Berkeley, CA - 94704
Date: Sat, 23 Jan 1993 23:06:38 GMT

In article <QfLze7y00WBNI1LkYS@andrew.cmu.edu> "Alex R.N. Wetmore" <aw2t+@andrew.cmu.edu> writes:
>Is there any sort bootstrap for 386bsd that will let me choose which
>kernel to boot up (so it would boot 386bsd by default, but I could make
>something like 386bsd.x if I wanted to run X).  I would like to run the
>pcvt console driver, but I also use X sometimes (rarely, but enough that
>I don't want to trash it).  So, it would be nice to have two kernels
>compiled, one that runs pcvt, and one that doesn't so that I can run X.
>
>
>alex
>
The new bootblocks posted previously in c.u.b
and in ref.tfs.com:/usr/src/sys.extras/julian-bootblocks


do exactly this:

they also use BIOS for all ops so they will work for both 
SCSI and wd drives

julian
+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\
	  v

Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: [386bsd] X broken with new patchkit ?
Organization: Weber State University  (Ogden, UT)
Date: Thu, 28 Jan 93 17:56:19 GMT

In article <4374@wzv.win.tue.nl> guido@gvr.win.tue.nl (Guido van Rooij) writes:
>I installed the new patchkit a few days ago. I also had keycap-0.1.1 (codrv)
>installed. This used to work fine, but now that I've installed the new
>patchkit, the keyboard isn't functioning quite well anymore when using X.
>Symptoms are that after pressing a key you have to wiat several seconds
>for the key to become visible on your xterm UNLESS you move your mouse..
>then the char immediately shows up. Anyone having the same behaviour?

Obvious select() problem -- make sure the right device is selected in the
com driver (0 instead of 1 or 1 instead of 2.  This was in the previous
patch kit, and I don't think it was removed.

Until this is fixed by you, you will find your X server eating inordinate
amounts of CPU most of the time.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
From: junki@lut.fi (Juha Nurmela)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] Followup: WD8013 card
Date: 27 Jan 93 20:15:03 GMT
Organization: Lappeenranta University of Technology, Lappeenranta, Finland

In article <1993Jan26.205504.24467@fcom.cc.utah.edu>, terry@cs.weber.edu (A Wizard of Earth C) writes:
|> In article <C1FuJ7.4A9@rot.qc.ca> captain@rot.qc.ca (Andrew Webster) writes:
|> >The WD8013 does seem to exhibit odd behaviour as the kernel only detects
|> >the card from a cold boot / power up.
|> >One person who responded mentioned this problem.  It is wide spread?
|> >Is there a fix?
|> 
|> The problem is that a warm boot does not cause a card reset.  This is
|> arguably a defect in the card.
|> ...

Is there a reason for not using outb(0x64, 0xfe) in reboot ?
To my knowledge, this pulses the reset-line on the whole system
and everything resets to a known state (hopefully).
The 0x64 is on the keyboard chip ?

-- 
         juha nurmela, Adr. 54430 Hujakkala, Finland. Tel. 953 78022
                  eiku: skinnarilank. 28d10, Tel. 953 26292
Newsgroups: comp.unix.bsd
From: GSPIEGEL@bsa3.kent.edu (Greg Spiegelberg)
Subject: [386BSD] Quotas, maxusers, & sendmail
Keywords: 386bsd, quota, maxusers, sendmail
Organization: Kent State University, School of Business Administration
Date: Mon, 25 Jan 1993 15:39:47 GMT

Ok, so I rebuilt the kernel with the -DQUOTA option and the MAXUSERS = 20.
So why don't they work?  

Ok, I need to get the quota util's.  Anyone know where they can be found?

But the system is only allowing 4 users.  If we try logining in a 5th we get 
the "telnetd: All network ports in use." error.  We have enough tty devices 
in the /dev dir and the getty "seems" to be working fine.

Anyone else having these problems?

-Greg

BTW: Anyone have a working sendmail.cf file for internet access?
     Our mail is going to the wrong machines.
From: doyle@freya.cs.umass.edu (Jim Doyle)
Newsgroups: comp.unix.bsd
Subject: [386BSD] Reliability of GNU LIBC 1.05 ??
Date: 27 Jan 93 02:07:40 GMT
Organization: University of Massachusetts, Amherst


	Has anyone used gnu libc.a to recompile the Unix distribution in
386BSD? I would like to know of any problems in compatibility or difficulties
that people have encountered. 

	I am considering using the GNU libc to generate a 4.3bsd libc for
the MIPS R3000/2000 platform based on the Mach 3.0 UX39 Unix server. If
there are problems w/ the i386 - which uses mostly platform independent code,
then I want to anticipate them for MIPS.

..... Jim  Doyle
Newsgroups: comp.unix.bsd
From: sgccseh@citec.oz.au (Steve Hocking)
Subject: Re: [386BSD] gcc2 and -fPIC
Organization: CITEC
Date: Wed, 27 Jan 1993 03:31:41 GMT

cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou) writes:

>anybody gotten code compiled w/gcc2's -fPIC to assemble properly
>(or "at all") under 386bsd?

>if so, could you tell me what i'm doing wrong?

>gcc -c -fPIC -O foo.c
>just won't do it for me... 8-)

	Gas isnt up to handling some of the special requirements of PIC code
(something to do with certain psuedo ops I think) You'll need to hack GAS as
well if you're trying to get shared libs going (as well as ld).

>Chris G. Demetriou                                    cgd@cs.berkeley.edu

>"Sometimes it is better to have twenty million instructions by
>        Friday than twenty million instructions per second." -- Wes Clark
-- 
-----------------------------------------------------------------------------
          "Toddlers are the stormtroopers of the Lord of Entropy"

Stephen Hocking                                    sgccseh@citecuc.citec.oz.au
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.hardware
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.unix.bsd
Subject: Re: uugetty
Date: 24 Jan 93 17:59:13
Organization: Kernel Hackers 'r' Us
	<1993Jan24.234022.28980@fcom.cc.utah.edu>
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: terry@cs.weber.edu's message of Sun, 24 Jan 93 23:40:22 GMT

terry didn't say it, but you don't get that functionality from the
standard 386BSD serial driver, you need my hacked version... 8-)

available from agate.berkeley.edu:pub/386BSD/386bsd-0.1/unofficial/cgd
	       ref.tfs.com:~cgd/com

later,

chris
--
Chris G. Demetriou                                    cgd@cs.berkeley.edu

"Sometimes it is better to have twenty million instructions by
        Friday than twenty million instructions per second." -- Wes Clark
Newsgroups: comp.unix.bsd
From: dmuntz@quip.eecs.umich.edu (Dan Muntz)
Subject: Re: [386BSD] What ist the state of XS3 ?
Keywords: 386BSD, XS3
Organization: University of Michigan EECS Dept., Ann Arbor
Date: Thu, 28 Jan 1993 02:38:13 GMT

In article <scott.728179123@pita> scott@pita.cns.ucla.edu (Scott Burris) writes:
>kehr@rs3.hrz.th-darmstadt.de (Roger Kehr) writes:
>>- how stable ist XS3 for 386BSD ?
>
>I've been using XS3 for a few months now with an STB WIND/X board
>(911 based with Logitech mouse).  I've had no problem.  Things are stable
>enough that I never run in anything but an X11 environment anymore.
>

I was using XS3 with an Orchid F1280, but had to switch back to XFree86 and
my ET4000-based Orchid PD IIs.  I've had problems with fonts in some
cases, and xtroff was unusable (and I needed to use it).

  -Dan
   dmuntz@eecs.umich.edu

Newsgroups: comp.unix.bsd
From: osynw@gemini.oscs.montana.edu (Nate Williams)
Subject: ANNOUNCEMENT: PATCHKIT 0.2 is ALMOST OUT
Summary: Testing
Keywords: n
Organization: Montana State University
Date: Fri, 22 Jan 1993 23:11:26 GMT

Okay, here's the situation.

I am pretty sure I have most things whipped, but I would like people
who are having, or who have in the past have had troubles booting
386BSD 0.1 to try out my new installation kernel.

Also, if you think that one of these patches will break your machine,
try getting this new bootable and trying it out.  If I don't get
any large problems by the end of the weekend, I'm going to release
this version of the patchkit and then pass on the co-ordination
officially to the new guy.

This bootable is a copy of the generic Tiny-386BSD bootable that is
archived everywhere, with all of the DOCS deleted for space, but the
kernel contains all of the boot and kernel patches in the next version
of the patchkit with exception to the WD ethernet driver patches.

Hopefully this should fix most, if not all of the booting problems
people have reported.

Short summary:
-------------
1) Aha 1542A is now supported

2) Most MFM/IDE/ESDI disks should be recognized and should boot
   properly. (There is still the IDE problems with drive translation,
   unfortunately)

3) Hang after copyright bug should hopefully be fixed. (I had one machine
   here that it seemed to work on.  All the rest didn't have any problems)

4) Compaq/Gateway machines should be able to boot.

5) Many new kernel patches for stability.

6) Patchkit order re-vamping, to make installation easier, and to
   place emphasis on REALLY important patches.

7) Other little things, but overall I'm pretty pleased with it.  

There are a couple other things I would like to have done, but I kept
putting it off and putting it off, so I am finally going to get this out
of the door.

The location of the bootable image (needs to be written to a 5.25" or
3.5" floppy using rawrite, dd, etc) is located at:

agate.berkeley.edu:/pub/incoming/nate/dist.fs-patchkit-0.2

The nate directory under incoming is readable, so if you don't 
remember you should be able to see the file.

PLEASE, PLEASE, PLEASE - If you have problems, try this bootable
out.  I have been running around campus trying it on different
machines here, but we only have Zenith's and DEC machines mostly,
which doesn't even come close to checking out all of the different
possibilities that exist.


Thanks alot!!

Nate
-- 
osynw@terra.oscs.montana.edu |  A hacker w/out a home. 
work: (406) 994-5991         |  Keeper of the Unofficial 386BSD Bug Report
home: (406) 586-0579         |  Please send bugs and/or fixes you find.
Newsgroups: comp.unix.bsd
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: Where can I pick up the FAQ from?
Organization: Weber State University  (Ogden, UT)
Date: Sun, 24 Jan 93 22:38:27 GMT

In article <1993Jan23.232356.11328@delos.stgt.sub.org> migieger@delos.stgt.sub.org (Michael Giegerich) writes:
>Hi,
>
>>You might find the FAQ and BUGLIST (really an FAQ) on agate:
>>anon ftp agate.berkeley.edu; ~/pub/386BSD/386bsd-0.1/unofficial/{*FAQ,*BUGLIST}
>
>I wonder what could be the reason to keep the FAQ and the BUGLIST
>(and BTW, the patch-kit) "hidden" on agate.berkeley.edu; this
>forces many people without access to ftp-connections asking the
>same questions again and again...
>
>Any hints?

1)	It's out of date (I know, I wrote it; it's definitely out of date
	since the first patchkit release).
2)	It's going to be more out of date with the 0.2 patchkit release.
3)	It's going to be hopelessly out of date for the 0.2 386BSD release,
	and will probably have to be restarted.
4)	It's too large to fit through the 20k restrictors on non-network
	uucp connections for thing like uucp-based netnews -- thus it
	would never make it unless split up (something I'm doing as part
	of reorganizing it, but I'm having a hard time keeping up with
	the changes well enough to do a release).
5)	It's mirrored a lot of places, including to those with FTP mail
	servers (like ftp.uu.net and wuarchive.wust.edu)... so it's not
	really "hidden" anyway.
6)	The Jolitz's didn't produce the FAQ, BUGLIST, or patchkit; therefore
	they are unofficial; they go under the "unofficial" directory in
	the 386BSD heirarchy.
7)	Finally, you may have noticed that the 0.1 release of 386BSD
	requires access to a mirrored source tree to get anyway; even if
	done by mail archive server, this gives you access to the
	"unofficial" portion of the heirarchy.

I don't know what the position on mail-servers is on ref or agate, but I
*know* I can't run one here (WSU) or at work (Novell) to spend all day
sending FAQ's out.  Sorry.


					Terry Lambert
					terry@icarus.weber.edu
					terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
-- 
-------------------------------------------------------------------------------
                                        "I have an 8 user poetic license" - me
 Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------
From: pbd@runyon.cim.cdc.com (Paul Dokas)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] problem with new patchkit?
Date: 27 Jan 93 22:23:11 GMT
Organization: ICEM Systems, Inc.

In article <1993Jan27.191018.21657@bradford.ac.uk>, T.D.G.Sandford@bradford.ac.uk (TDG SANDFORD) writes:
|> tried to deinstall patch00603
|> 	reported "required by patch00602" so
|> tried to deinstall patch00602
|> 	succesfull
|> tried to deinstall patch00603
|> 	reported "user has deleted file (?cant remember?) - can't deinstall"
|> tried reinstalling patch00602
|> 	succesfull
|> tried deinstalling patch00603 again
|> 	reported "required by patch00055"

I had exactly the same problem.  It turns out that patch 602 and 603 patch
the same file (pccons.c) and they are mutually exclusive.  You'll notice
that in with pccons.c you'll also find pccons.pl[123] and pccons.rej.  The
patch 603 changes pccons.c and then bombs out leaving the .rej.

I rescued pccons.c by backing out 603 by hand (and luck).

BTW, I also had a couple of patch rejects (my fault) but patches didn't
say anything about them.  Shouldn't there be some kind of error or warning
if a .rej is created?
-- 
#include <std.disclaimer>
#define FULL_NAME                          "Paul Dokas"
#define EMAIL                              "pbd@runyon.cim.cdc.com"
/*            Just remember, you *WILL* die someday.             */
From: dfox@quack.sac.ca.us (David Fox)
Newsgroups: comp.unix.bsd
Subject: [386bsd] com-beta.tar.Z installation problems
Keywords: com-beta.tar.Z bidirectional comdriver
Date: 23 Jan 93 00:21:04 GMT
Organization: The Duck Pond public unix: +1 408 249 9630, log in as 'guest'.


I'm having some problems installing cgd's com driver.  Apparently due to
the inconsistencies (possibly?) between patchkit 0.1, which I have, and
patchkit 0.2, which I don't have, and apparently can't get yet), the
patch for com.c doesn't go all the way through.

Could someone who has installed this please mail me their
/sys/i386/isa/com.c file?  I'll take it from there.

Thanks.

-- 
------------------------------------------------------------------------
in real life: david fox            email: dfox@quack.sac.ca.us
5479 Castle Manor Drive,                  
San Jose, CA 95129                 "Thanks for letting me change some
USA                                 magnetic patterns on your HD" -me
408-253-7992                        
"You've just won an absolutely FREE trip to the Isles of Langerhans" -me
------------------------------------------------------------------------
Newsgroups: comp.unix.bsd
From: jkh@whisker.lotus.ie (Jordan K. Hubbard)
Subject: [386bsd] Mylex DCE376 controller using Julian SCSI, anyone?
Organization: Lotus Development Ireland
Distribution: comp
Date: Sat, 23 Jan 1993 03:51:51 GMT

Just for grins, I've thought about seeing how fast a DCE376 controller
(w/4MB cache) might be for a 386bsd system and I'm currently looking
at what's involved in adding in the appropriate driver layer for
Julian's new SCSI drivers.  Before I get serious, anyone ever looked
at this, or own a Mylex DCE376?

The things are hellishly fast on DOS systems, though DOS gains a lot by
having repetetive reads made cheaper.  I'm not sure how well 386bsd's
cache strategy and the DCE's would/will get along.

Comments (Julian?) welcome..

					Jordan
--
Jordan Hubbard		Lotus Development Ireland	jkh@whisker.lotus.ie
I DO NOT SPEAK FOR LOTUS - IT HAS PLENTY OF LAWYERS TO DO THAT FOR IT ALREADY
From: faldor@seq.uncwil.edu (Sherman Brown)
Subject: Could someone please send me the newest FAQ for 386BSD..?
Organization: Univ. of North Carolina @ Wilmington
Date: Tue, 26 Jan 1993 16:33:46 GMT

Title says it all...

thanx in advance,
Faldor

.___________________________________________________________________.
|               University of North Carolina at Wilmington          |
|                        faldor@seq.uncwil.edu                      |
|-------------------------------------------------------------------|
|  Alien Invasion Division : Integration/Substitution Group. (ISG)  |
.___________________________________________________________________.
Newsgroups: comp.unix.bsd,comp.sys.ibm.pc.hardware
From: ted@usasoc.soc.mil (Mr. Ted Nolan)
Subject: ATI Mach32 and Xfree86 or XS3?
Organization: SRI International
Date: Tue, 26 Jan 1993 16:27:04 GMT

Hello folks,

I'm plugging along in my quest to spec out a nice 486 system to get and
run 386BSD and X on.  I've seen a few advertisements for the ATI Mach32
video card.  It seems this is a local bus card that can do 1024x1280 in
256 color mode.  Does anyone know if this has an S3 or ET4000 chipset?
Can you run X on it?

				Thanks,

				Ted Nolan
				ted@usasoc.soc.mil
From: raz@sleeper.apana.org.au (Roland Turner)
Newsgroups: comp.unix.bsd
Subject: Re: [386bsd] patch-kit inconsistancy?
Date: Sun, 24 Jan 1993 01:47:42 GMT
Organization: Desolation Road Railfan BBS

terry@cs.weber.edu (A Wizard of Earth C) writes:

>>Should I uninstall the old ones before installing the new?  Is
>>patchkit-0.2.tar.Z more "official"?
>>
>>Help?

>You've been sneaking around, I guess.

>The 0.2 patchkit isn't released yet as far as I know.


In that case, someone has been spectacularly careless! Approx 36 hours prior to
the posting of your message (that which I am following up - can't be bothered
doing exact timezone conversions :-)) I was re-aquiring the src01 dist from
kirk.bu.oz.au (official site downunder, says so in DISTRIBUTION.SITES!) and 
decided to grab the patchkit whilst I was there as I couldn't remember where
I had put it. In doing so, I found 0.2 in the directory structure with YOUR
name on it (and 0.1 is now absent) and thought "Oh goody - I get to have an
up to date source tree!"

Even though I have an unnoficial pathkit, my system is FINALLY stable and 
usable. (It even recognises my second 200M drive. Joy!) Darn.


-- 
Bye for now.
        - Raz.

raz@sleeper.apana.org.au   (Roland Turner)   (OH) 61 2 319 5700
From: mycroft@hal.gnu.ai.mit.edu (Charles Hannum)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] Quotas, maxusers, & sendmail
Keywords: 386bsd, quota, maxusers, sendmail
Date: 25 Jan 93 17:58:07 GMT
Organization: /etc/organization
NNTP-Posting-Host: hal.ai.mit.edu


In article <GSPIEGEL.16.727976387@bsa3.kent.edu> GSPIEGEL@bsa3.kent.edu
(Greg Spiegelberg) writes:
>
> But the system is only allowing 4 users.  If we try logining in a 5th
> we get the "telnetd: All network ports in use." error.  We have
> enough tty devices in the /dev dir and the getty "seems" to be
> working fine.

You're looking at the wrong thing.  Your problem is that you haven't
configured the kernel for enough ptys.  In /sys/i386/conf/FOOBAR, you
should have a line like:

pseudo-device   pty             4

Change the `4' to whatever number of ptys you want available.  For 20
real users, I would suggest 32.

> Anyone else having these problems?

!I

> BTW: Anyone have a working sendmail.cf file for internet access?

The sendmail sources come with some examples and a simplified
configuration mechanism using m4.

-- 
 \  /   Charles Hannum, mycroft@ai.mit.edu
 /\ \   PGP public key available on request.  MIME, AMS, NextMail accepted.
Scheme  White heterosexual atheist male (WHAM) pride!
Newsgroups: comp.unix.bsd