HDTenEightyP/NetNews huggingface dataset:
From: sheldon@iastate.edu (Steve Sheldon)
Subject: New Install - Comments and Questions
Organization: Iowa State University, Ames IA
Date: Mon, 27 Jul 1992 17:49:26 GMT

Well, I've so far gotten everything to work.  It's been quite an
experience, lot's of fun anyway.

 I ended up doing the installation using the MCC-Interim release which
I ftp'ed from tsx-11.mit.edu's mirrors.  This worked great.  I was
able to easily set up my harddrive, and now can boot into the Linux
partition using shoelace, and everything.

 I also tried using the MJ distribution which I found on banjo.concert.net,
but things didn't go as smoothly.  For some reason I encountered two
problems with it.  Not major, as I was able to get around them.
1. It keeps giving an error something like 'setutent - utmp file does not
exist'.  I'm not sure what this means, otherwise things work.
2. There is a bug in the install script.  I don't have it handy, but when
copying the devices it changes directories to /mnt, and then does not
change back to the / root, so when it does the tar to copy over the
bin's and such, it can't find the directories, and fails.  Easy to fix,
I just had to add a 'CD /' in the script, fortunately there was an
editor on the disk so I could do this.

 I like the MJ distribution install scripts, it makes things a lot more
"user friendly".  At least until you get to the harddrive installation,
as this distribution does not provide for a way to automatically do this,
and refers you to use a DOS disk editor and manually do it, which is
definately not user friendly.

 So I'd have to say the MCC release was much friendlier, in that it
allowed me to setup everything from within Linux.

 However, the MJ distribution is has a more complete utilities package.  It
contains reboot and shutdown, and not to mention a better /etc/termcap,
and some other things.  So I like that about it.

 Each has it's positive points.  Merge the two together and you've got a
winner.  I just don't like having to do things manually, although it does
help in understanding.

 Now I have a couple of questions.

 1. Upon booting Linux it asks for SVGA modes.  I get 6 or 7 options.
Well I can get the 80 column modes to work, but not the 132 column.
When I select a 132 column mode, the screen stays the same (i.e. 80x25),
but internally it things it's right.  So if I selected something like
132x50, it thinks there is 50 lines, but I only see the top 25.
I'm using a Trident 8900 video card, with 256K of memory onboard, with
an Everex monochrome VGA monitor.  I get 132 column modes just fine using
DOS.  Has anyone else had this problem?

2. Is there some documentation for bash?  I was having some trouble 
setting the path, as the defaults are missing the current directory.
I tried SET, and this did not work.  But I found a profile script
in /etc, and it used EXPORT.  Upon trying this, it did work.
I don't play with shells too much, but this is different from the
shell's I'm used to. (csh I think)  So what else that I might use has
changed?

 Well thanks for any answers.  This looks great, and I really want to
thank everybody who's worked on this.

Steve
.sig file still under construction
From: lcj0@ns1.cc.lehigh.edu (Lutzer <R>/Deutschland.com)
Newsgroups: comp.os.linux
Subject: Re: 0.96c + X + Logi :-(
Date: 27 Jul 92 19:49:03 GMT
Organization: Lehigh University



Has anyone gotten their Logitech Bus Trackman to work with X?  I have another mouse to use in the interim, but would like the trackman back... :) I have tried the Xconfig options for bus mice, and have created the bus driver.... Any ideas?  E-mail or post appreciated... Thanks....
-- 


------------------------------------------------------------------------------
lutzer@plasma.physics.lehigh.edu
lcj0@Lehigh.edu                                 Lutzer (R)
                                                LUCC Student Konsultant
Newsgroups: comp.os.linux
From: jchaiken@nyx.cs.du.edu (Jarett  Chaiken)
Subject: Re: Spreadsheet for Linux
Organization: University of Denver, Dept. of Math & Comp. Sci.
Date: Thu, 30 Jul 92 17:59:26 GMT

Wow! I'm glad someone already ported sc for linux, I was just about to 
undergo that endevor myself


--
Jarett D. Chaiken
Newsgroups: comp.os.linux
From: steffen@gfz-potsdam.dbp.de
Subject: Re: clock.exe reboots system!
Reply-To: steffen@gfz-potsdam.dbp.de
Organization: The Internet
Date: Wed, 29 Jul 1992 06:11:13 GMT

RFC-822-Headers:
X-Mailer: ELM [version 2.3 PL11]

==================
X-Mn-Key: NORMAL
"Andrew F. Gunnesch writes :"

   RFC-822-HEADERS:
   X-Note1: Remember to put 'X-Mn-Key: normal' to your mail body or header


   Hi there.  My friend is trying to get X up and running on his 386-33,
   with BOCA et4000 board.  Whenever he runs clock.exe, his machine reboots!
   He tried the board and monitor on another machine, and this time clock.exe
   locked the machine up tight (needed to reset it).  Any ideas what might be
   going wrong?

   --andrew

clock.exe is (as I understand and use it) a DOS, not a Linux program. So if
you run it under Linux, there will be some conflicts between clock.exe
awaiting a real mode environment, and Linux running protected mode - and also
due to the diff of system calls.
Use clock.exe under DOGs only (if this is done, you can drop DOS :)

--
Steffen Grunewald | IP : steffen@gfz-potsdam.dbp.de | Phone : (+49)331-310526
GeoForschungsZentrum Potsdam,  Telegrafenberg A3,   O-1561 Potsdam,   Germany
#include <disclaimer.h>     /* >>> I don't like Mondays - and .sig's ! <<< */
From: barr@hardy.u.washington.edu (David Barr)
Newsgroups: comp.os.linux
Subject: Re: Install-Help
Date: 28 Jul 92 15:40:52 GMT
Distribution: na
Organization: University of Washington

asmith@cbnewsd.cb.att.com (arthur.c.smith) writes:

>root-image0.96c.Z from the pub/linux/images dir. When I try to uncompress
>boot-image0.96c.Z uncompress creates a file of size ulimit(2048K) and dies.
>Root-image0.96c.Z reports an error after about 5k is uncompressed. I can
>uncompress files that I compress. This is being done on a 3B2 and as far
...
>                          Thanks,
>                            Art  (asmith!nwsca@att.com)

Make sure that you ftp the file in binary mode.  At the ftp prompt,
type "binary" before you type "get root-image0.96c.Z," etc...

David
Newsgroups: comp.os.linux
From: INABU@ibm.rz.tu-clausthal.de (Arnd Burghardt)
Subject: Upgrading from 0.96c pl1 to 0.96c pl2 makes X11 hang
Organization: Rechenzentrum der TU CLAUSTHAL
Date: Fri, 31 Jul 1992 13:49:06 GMT

I'm using mcc-interim 0.96c, and made the upgrade to pl1.
It was not to much traffic, then I decided to go to pl2 (banjo.concert.net).
Compiling was no problem (german-keybord, boot from /dev/hda1).
I got the last mount (from banjo in incoming-dir).
Now come problems :
no way to mount the DOS-Partition (dev/hda4)
not any response from X11 anymore.
switching back to the old Image X11 works fine...
 
My System is a amd 386/40 - 8Mb-Ram -sigma-legend-II(et4000)
               Seagate St3144 130 Mb At-bus-HDD
               /dev/hda1 7Mb  - root
               /dev/hda2 16Mb - swap
               /dev/hda3 64Mb - usr and home
               /dev/hda4 38Mb - dos5.0
 
Has anybody similar problems - any solutions?
 
By the way is X11 not the heaven of windowing, but would be nice, if works...
 
 
Thanks for help
Arnd Burghardt
 
 
 
 
 
 
Arnd Burghardt
 
An der Tillyschanze 4           !
3392 Clausthal-Zellerfeld       !
Germany                         !  INABU@ibm.rz.tu-clausthal.de
+49 5323 1552                   !  INABU@sun.rz.tu-clausthal.de
 
Remenber what AL says : Save often, save early !
From: hyvatti@klaava.Helsinki.FI (Jaakko Hyvatti)
Newsgroups: comp.os.linux
Subject: Re: IRQs and 0.96c PL2. I'm still confused!
Date: 25 Jul 92 04:49:38 GMT
Organization: University of Helsinki

In article <p2hmsc_.james@netcom.com> james@netcom.com (James L. Paul) writes:
...
>Linux does this no matter how I have the IRQs set up. Why, and how
>do I fix it?

  At bootup linux uses 'standard' serial configurations. If you want to
alter this confguration, you've got to get setserial.tar.Z by Rick Sladkey
(jrs@world.std.com) from banjo.concert.net or tsx-11.mit.edu or
somewhere else.

  There is also a bug in 0.96c-pl2 which prevents one from configuring
serial devices that don't have the standard port addresses. This
shouldn't affect you, but in case someone else having that problem
missed my first post:

*** linux/kernel/chr_drv/serial.c.OLD	Sun Jul 19 08:45:41 1992
--- linux/kernel/chr_drv/serial.c	Sun Jul 19 08:45:44 1992
***************
*** 313,318 ****
--- 313,320 ----
  
  static void startup(unsigned short port)
  {
+ 	int count = 0;
+ 
  	outb_p(0x03,port+3);	/* reset DLAB */
  	outb_p(0x0f,port+4);	/* set DTR,RTS, OUT_2 */
  	outb_p(0x0f,port+1);	/* enable all intrs */
***************
*** 322,328 ****
  	inb_p(port+5);
  	do {		/* drain all of the stuck characters out of the port */
  		inb_p(port+0);
! 	} while (inb_p(port+5) & 1 == 1);
  	inb_p(port+2);
  	inb_p(port+5);
  }
--- 324,330 ----
  	inb_p(port+5);
  	do {		/* drain all of the stuck characters out of the port */
  		inb_p(port+0);
! 	} while (inb_p(port+5) & 1 == 1 && ++count < 16);
  	inb_p(port+2);
  	inb_p(port+5);
  }

-- 
Jaakko Hyv{tti			Jaakko.Hyvatti@Helsinki.FI
Karstulantie 8 B 30		hyvatti@plootu.Helsinki.FI
00550  Helsinki, Finland	+358-0-701 7810, -692 7466 (work)
Newsgroups: comp.os.linux
From: unixsys@ssg.com (Rick Emerson)
Subject: mailpak - where is it?
Organization: System Support Group
Date: Thu, 23 Jul 1992 16:25:32 GMT

Where's the latest and greatest mailpak and where is it?

Rick


| Richard B. Emerson     | Replies may be sent to:                         |
| System Support Group   |         unixsys@ssg.com  -or-  rick@ssg.com     |
| Post Office Box 180    |-------------------------------------------------+
| Lansdale, PA 19446 USA |     "If I knew what I was doing,                |
| Voice: 215.855.1607    |      I wouldn't do it." - Me                    |
Newsgroups: comp.os.linux
From: alatar@marcus.its.rpi.edu (Robert William Alatalo)
Subject: what SCSI drives does linux support?
Keywords: scsi linux
Date: Thu, 30 Jul 1992 03:37:05 GMT

What SCSI drives/controllers does linux currently support and will support in
the future?

please reply by mail: alatar@rpi.edu

Thank you.
From: bsp10@cd.amdahl.com (Byong Pak)
Newsgroups: comp.os.linux
Subject: Logitech bus mouse on linux 96cpl2
Date: 24 Jul 92 00:41:46 GMT
Reply-To: bsp10@duts.ccc.amdahl.com
Organization: Amdahl Corporation, Sunnyvale CA


I am trying to get my bus mouse to work on this kernal (actually, my bus 
mouse never really worked...)  But I am getting a interupt 5 overrun error
when I try the mouse program in X11/tst

Does anyone know how to take care of this?  or what this could mean?

Thanks
Byong


-- 
* Byong "the pakman" Pak             * These opinions are my own and do *
*        aka                         *   not reflect the opinions or    *
*  email:  bsp10@duts.ccc.amdahl.com *    policies of Amdahl Corp.      *
*  phone:  408-746-7871              *                                  *
From: pete@q106fm.UUCP (pete cervasio)
Newsgroups: comp.os.linux
Subject: Re: Keyboard bug?
Keywords: bug, yet another one, blame linus :-)
Date: Mon, 27 Jul 92 01:36:37 CDT
Organization: WKBQ-FM Engineering Department

joef@extro.ucc.su.OZ.AU () writes:

>   Bootup sequence: when it asks you to press return or any key to continue,
> if you happen to press 2 keys accidently, or a 'grey' key [ctrl, alt, caps-
> lock, etc] the keyboard will lock up.  I haven't even had a look at the 
> source of it yet, but I thought I better bring it up to make sure it's a 
> real bug.  It's happened on 2 other systems apart from mine, so it's not
> a hardware dependant bug.

I had this sort of thing happen to me... my keyboard was laying
catty-corner while booting up, and I hit the gray enter key over on the
side...  Good thing I've got a key that _always_ works.... a red one.

Pete C.


+----------------------------------------------------------------------+
| Pete Cervasio                | pete%q106fm.uucp@wupost.wustl.edu     |
| I fish, therefore I am.      | pete.cervasio@f1.n2250.z1.fidonet.org |
+----------------------------------------------------------------------+
Newsgroups: comp.os.linux
From: thoth@uiuc.edu (Ben Cox)
Subject: Re: xhetris
Originator: btc30679@uxa.cso.uiuc.edu
Reply-To: thoth@uiuc.edu (Ben Cox)
Organization: University of Illinois at Urbana
Date: Sat, 25 Jul 1992 16:36:07 GMT

thoth@uiuc.edu (Ben Cox) writes:

>xset compiles with no changes.  Look on export.lcs.mit.edu under
>/pub/R5untarres/mit/clients/xset (this may not be exactly the correct
               ^
Of course I meant untarred.

--
Ben Cox
thoth@uiuc.edu
Newsgroups: comp.os.linux
From: brudiakg@nyx.cs.du.edu (Ben Rudiak-Gould)
Subject: Re: X11 and Trident
Organization: University of Denver, Dept. of Math & Comp. Sci.
Date: Sun, 26 Jul 92 04:41:19 GMT

treason@hal.gnu.ai.mit.edu (Act of Treason) writes:

>I have found a file X386-Trident.tar.Z which explains in not so many words that
>you may compile X with this uncomplete driver and run X11 with a trident.  I 
>understand that it is uncomplete, and I would LOVE to try it out anyway.
       [snip]
>If anyone has compiled X with this driver, I would appreciate a copy if
>possible and will be indentured to you for it, none the less, I dont have
>enough disk to recompile all of X...

I would like to second this request.  The above is almost exactly the
situation that I find myself in.  Please don't mail any binaries to me,
but please do put them on one of the FTP sites.  Thanks!

--
Ben Rudiak-Gould
brudiakg@nyx.cs.du.edu
From: simonich@uservx.plk.af.mil
Newsgroups: comp.os.linux
Subject: Re: Installing from 0.96c root disk(success)
Date: 27 Jul 92 20:41:46 GMT
Organization: Phillips Laboratory - Kirtland AFB

In article <1992Jul25.233826.2624@athena.mit.edu>, balister@pdsrvr.salem.ge.com (Philip Balister) writes:
> Hi,
> 
> I've been installing my second linux machine from the 0.96c boot/root disks.
> I have the machine building the kernel and running X. Along the way I ran
> into a few minor problems:
> 
> 1) After installing the base system from trhe 0.96c root disk I installed
> the base and extra X packages. Success!
> 
> 2) Then I installed Gccv2.2.2. The following utilities are not on the root
> disk or the binutils package: ln, find, make, awk, grep. These are used in
> the install scripts. (cp --link works but I didn't want to hack the scripts)
> Should these be included in the binutils tar, the 0.96c root disk looks
> pretty full?
> 
> 3) The kernel stuff goes OK, excpet when compiling build.c. It looks for
> linux/include/fs.h, not around any more. After some research I patched it
> to use <sys/sysmacros.h> (The cdiffs follow)
> 
> Thanks to all working on this system, It is GREAT!
> 
> Philip Balister
> balister@salem.salem.ge.com
> 
> *** ./build.c	Sat Jul 25 19:13:47 1992
> --- ./build.c.old	Tue May 26 12:40:55 1992
> ***************
> *** 25,31 ****
>   #include <stdlib.h>	/* contains exit */
>   #include <sys/types.h>	/* unistd.h needs this */
>   #include <sys/stat.h>
> ! #include <sys/sysmacros.h> 
>   #include <unistd.h>	/* contains read/write */
>   #include <fcntl.h>
>   
> --- 25,31 ----
>   #include <stdlib.h>	/* contains exit */
>   #include <sys/types.h>	/* unistd.h needs this */
>   #include <sys/stat.h>
> ! #include <linux/fs.h>
>   #include <unistd.h>	/* contains read/write */
>   #include <fcntl.h>
>   
> ***************
> *** 69,76 ****
>   				perror(argv[4]);
>   				die("Couldn't stat root device.");
>   			}
> ! 			major_root = major(sb.st_rdev);
> ! 			minor_root = minor(sb.st_rdev);
>   		} else {
>   			major_root = 0;
>   			minor_root = 0;
> --- 69,76 ----
>   				perror(argv[4]);
>   				die("Couldn't stat root device.");
>   			}
> ! 			major_root = MAJOR(sb.st_rdev);
> ! 			minor_root = MINOR(sb.st_rdev);
>   		} else {
>   			major_root = 0;
>   			minor_root = 0;


I applied your fix to build.c with the following results:

	in file included from tools/build.c:25:
	/usr/include/stdlib.h:115: parse error before '*'
	/usr/include/stdlib.h:118: parse error before 'wchar_t'
	/usr/include/stdlib.h:121: parse error before '*'
	/usr/include/stdlib.h:123: parse error before '*'

(Note: I also changed one line in Makefilerror before '*'
  (Note: in Makefile:
	HOSTCC	=gcc -static
becomes
	HOSTCC	=gcc -static -I$(KERNELHDRS)
)

Any suggestestions?  Thanks
Newsgroups: comp.os.linux
From: bryan@uhura1.uucp (Bryan Curnutt)
Subject: Re: Need some help (info.) on background process, passwd, etc.
Reply-To: bryan%uhura1@uunet.uu.net
Organization: Stoner Associates, Inc./DREM Incorporated, Houston Texas
Date: Tue, 21 Jul 1992 04:01:46 GMT

In article <joef.711645207@extro.ucc.su.OZ.AU> joef@extro.ucc.su.OZ.AU () writes:
>elvis@uxh.cso.uiuc.edu (I am THE Elvis P.) writes:
>
>>	1) I can't seem to find any password program,
>
>tsx-11.mit.edu is a very nice site. I suggest you look in
>pub/Linux/Incoming and mget mj* 

Erm, perhaps you mean on banjo.concert.net?  There is no
pub/Linux/Incoming on tsx-11.mit.edu, unless I really missed
something.

I'd like to put in another plug here for Owen's MCC-Interim
distribution, whose base installation disks are available from
tsx-11.mit.edu under /pub/linux/mirrors/mcc-interim/0.96c/images,
among other places.  Very easy to install, and includes passwd,
ps, gcc, groff, and many other fine programs in working form.
Wonderful stuff.

And you won't even need to read the FAQ.  :-)  (<-- Note smiley,
denoting "I didn't really mean it!"  Please read the FAQ before
asking other questions, even though you can easily install the
MCC-Interim stuff without it.)
-- 
Any opinions above are mine, and do not necessarily reflect the views of SAI.

Bryan Curnutt                   | "I hope that UNIX is more like my diner
bryan%uhura1@uunet.uu.net       |  than like McDonald's." -- Doug McIlroy
Newsgroups: comp.os.linux
From: jes@grendel.demon.co.uk (Jim Segrave)
Subject: Re: Guidelines for reporting Linux bugs
Distribution: world
Organization: None
Date: Thu, 30 Jul 1992 00:41:28 +0000


In article <1992Jul28.134834.4764@dg-rtp.dg.com> welshm@snail.rtp.dg.com (Matt Welsh) writes:

> **** GUIDELINES FOR REPORTING LINUX BUGS ****
> 
> Last updated: 20 Jul 92
> 
> *** This file specifies how you should file bug reports and bug report
> *** updates (such as fixes and workaround reports). PLEASE READ before
> *** you do anything!! 
> 
> If you are having problems with Linux, the first thing you should do is
> POST your problem or possible bug to comp.os.linux or send it out on
> one of the several mailing lists. In this way, others can verify your
> problem and find out if it's actually a bug. 

NO! NO! NO!
The first thing is - check the FAQ.
Then, think about the problem yourself - I've seen some fairly silly
Help with ... reports which seemed to assume that 'GCC/Linux/any of a
large number of other utillities must be broken because they don't work
for me'. Use simple logic - the volume of traffic in this group
indicates that most things *do* work, so if they don't work for you the
most likely reasons are that you didn't understand the (sometimes
sketchy) documentation or you didn't follow it, or you are running an
old version of Linux/gcc/whatever and trying to run software set up for
a more recent version, etc.
If you still can't solve it, see if there's someone
knowledgable you can ask - colleague at work, fellow student, etc.
If all this fails, then post the problem.
The benefits are:
1) You'll learn more by trying to solve the problem yourself.
2) You'll understand the problem better if you really do need to post
the report, and your report will be clearer. You'll be able to save
everyone sending you stock answers like 0.95's tar is broken, etc.
because you will have checked the FAQ, chekced your version of tar, etc.
and your message will be able to say I'm running this version...
3) There will be less pressure to split comp.os.linux because there
won't be as many silly bug reports/help requests which really have been
answered over and over again.
4) The experts who can answer your questions will be less likely to have
become tired of answering repetitive pleas for help.

--
Jim Segrave (Segrave Software Services)     jes@grendel.demon.co.uk
From: axlas@acad2.alaska.edu (Leif A Sawyer)
Newsgroups: comp.os.linux
Subject: /dev/BusMouse ? Help!
Date: 21 Jul 92 17:00:51 GMT
Organization: Live Organ Transplants

Forgot to mention last time another problem.  Trying to get my
bus mouse to work.  Have a logitech trackman, and linux kernel finds
it correctly and init's it.  However, I don't seem to have a /dev/mouse
to correspond to it.  Any suggestions?  I RTFFAQ but didn't see anything 
on the bus mouse.

Thanks!

-- 
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
| Leif Sawyer -= AXLAS@acad2.alaska.edu | WWIVNet (The Patroler) -= 27@9702 |
| Try these also -= ASLAS@acad3.alaska.edu | BITNET -= AXLAS@alaska.BITNET  |
| USnail -= 3631 E. 42nd Circle #7 Anch, AK 99508 |  #define FLAME /dev/nul |
| "Views expressed by moi are not necessarily those Defined by my employer" |
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
Newsgroups: comp.os.linux
From: hpa@casbah.acns.nwu.edu (H. Peter Anvin N9ITP)
Subject: /dev/tty* naming conventions [long]; /dev/lp0
Reply-To: hpa@nwu.edu (H. Peter Anvin)
Organization: You must be kidding!
Date: Sun, 26 Jul 1992 19:51:37 GMT

First of all, a question: does anyone know of a problem with /dev/lp? in
Linux?  When booting up the system say /dev/lp0 is present, but anything I
output to /dev/lp0 does nothing for my printer.

Second, I was wondering about the naming conventions for /dev/tty*.

Function          BSD/Mach    Linux       IRIX (SysV)

Virtual console   console     console     console
Physical console  ?           tty0        contty
VTcon             ?           tty1-tty8   N/A
Serial port       ttya-ttyo   ttys1-ttys4 ttyd1-ttyd127
PTY master        ptyp0-ptyzf ptyp0-ptyrf ptc
PTY slave         ttyp0-ttyzf ttyp0-ttyrf ttyq0-ttyz99

The only problem with the Linux TTY naming scheme is that the serial ports
conflict with the namespace used for PTY slaves.  Even if the current Linux
major/minor scheme only allows 64 PTY's, that is enough to conflict with
the serial ports (the last 16 should be ttys?); and changing the
device-numbering scheme to allow a separate major number for PTY masters
and/or slaves is always a possibility.

Although 64 simultaneous logins can seem like more than a 386/486 would
ever handle; PTYs can be used quite copiously by programs such as screen
and windowing software; besides it is never a good idea to build in a limit
that cannot be further extended.

Finally, some software, notably xterm, don't like TTY names with more than
two characters after /dev/tty (see the -S option).  Therefore, it seems to
me as the BSD/Mach scheme would be the ideal; it would bring the added
advantage of making different TTY types easy to distinguish.

VTcons would be /dev/tty1 to /dev/tty8; could be extended up to /dev/tty99.

The serial ports would be /dev/ttya to /dev/ttyd; could be extended to
/dev/ttyo for up to 15 ports or to /dev/ttyz for up to 26 ports.

The PTYs would by /dev/ttyp0 to /dev/ttysf (with /dev/ptyp0 to /dev/ptysf
as the masters); this could be extended to /dev/ttyzf for a total of 176
PTYs with a new numbering scheme.  (SunOS uses /dev/ttyP0 to /dev/ttyTf to
extend up to 256 although these devices rarely come into use.)
-- 
INTERNET: hpa@nwu.edu   TALK:      hpa@casbah.acns.nwu.edu
BITNET:   HPA@NUACC     HAM RADIO: N9ITP, SM4TKN
IRC:      Scalar        NeXTMAIL:  hpa@lenny.acns.nwu.edu
This is a test of the emergency USENET system.