HDTenEightyP/NetNews huggingface dataset:
From: jonas@sisu.se (Jonas Lagerblad)
Subject: Re: Weird Problem (50 MHz, SCSI)
Keywords: SCSI, file corruption
Organization: Swedish Institute of Systems Development
Date: Wed, 14 Oct 1992 22:08:47 GMT

In article <Bw227w.6Bw@cs.vu.nl> versto@cs.vu.nl (C Verstoep) writes:
>Hi,
>
>The last couple of days I have (as of now unsuccessfully) tried to install
>386BSD0.1 on my new system.
>
>My setup is as follows:
>	- 50 Mhz local bus UMC mother board
>	- 16 Mb memory, 70ns SIMMs
>	- Adaptec 1542B scsi controller
>	- Fujitsu 2624F 520 Mb scsi disk.
... Problem description omitted ....
>
>By the way, with **DOS5.0 I didn't have this kind of problems, but I guess
>that doesn't say much.  A colleague of mine has the same system at home,
>with similar problems.
>
>Does anyone here have a clue about what could be the cause of all this?
>
>Thanks,
>Kees Verstoep (versto@cs.vu.nl)
I have had quite a lot of problems with two different 50 Mhz cards, I have 
traced the problem to the cache memory, which I don't think behaves quite 
all right when using a DMA driven disk controller. In my case the cache memory
has an access time of 20 ns and the tag ram 15 ns, and since the cycle time
of a 50MHz CPU is 20ns I think it should be quite tight to have 20 ns access 
time on the memory (even without needing to do a cache lookup). And when
the situation is even worse when DMA cycles might appear which might confuse
the cache logic this might cause memory corruption.

I posted an article to this newsgroup a week ago inquiring if anyone
besides me have had problems with their 50MHz boards and I have got approx.
10 answers where most people have had some strange memory problems, most 
of them had a SCSI controller.

My problems have disappeared totally since disabling the cache, but I have 
ordered new faster cache memory, and is eagerly waiting for it to arrive.
According to one of the hardware manuals for my DX50 cards the cache memory
should have 15 ns access time and the tag rams 12 ns. (The times can be read
on the chips which typically have some marking 67256-20 where -20 indicates
the access time of the ram, the number before the dash usually have something
to do with the size of the ram. The number I wrote here have no relevance at
all with anything). The cache and tag rams can usually be easily found, since
there usually are 8 cache rams and 3 tag rams which are not soldered, and sit in
a tight formation. (In my case under the power supply :-)

So my advice is to try to disable the cache, and see what happens.

Best Regards
-- 
Jonas Lagerblad
Phone Office: +46-31-830250 Home: +46-31-205955 Car: +46-10-2846031
FAX:	+46-31-831047
email:	jonas@sisu.se
From: guido@gvr.win.tue.nl (Guido van Rooij)
Newsgroups: comp.unix.bsd
Subject: uid's under Xfree
Date: 7 Oct 92 19:37:14 GMT
Organization: Guido's home 486 box

I noticed a strange behaviour when i did a talk to another user on my machine.
I was logged on using X, under xdm, say as user 'foo'. However when i did
that talk request, talk said: respond with talk root@<machine>
I dont know where exactly talk gets its uid from, but something serious
is wrong here. Maybe I gave the wrong programs an suid bit...
The programs involved are xdm, X386 and xterm. Only X386 and xterm have sbits
set. Isn't this correct? 
The output of id  also seems correct (it doesn't say i have uid 0).

Can anyone explain this?

-Guido
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: XFree86 and mice
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Date: Mon, 12 Oct 1992 07:15:27 GMT

In article <27444.9210120541@thor.cf.ac.uk> spedpr@thor.cf.ac.uk (Paul Richards) writes:
   I've just installed the new X server and I can't get any mice to work.
   I've tried a genius mouse with the mousesystems option and a logitech
   mouse with logitech and neither work.

   The server starts up prints the stippled background and the mouse cross
   and then just sits there. The cross doesn't respond to the mouse and the
   keyboard appears to be dead.  Any ideas?

Try using kermit or tip to see whether characters are read from the
com port when the mouse is moved.  Rich

   My card is an Orchid Prodesigner.

   -- 
     Paul Richards at Cardiff university, UK.

     spedpr@uk.ac.cf.thor	Internet: spedpr%thor.cf.ac.uk@nsfnet-relay.ac.uk
     UUCP:     spedpr@cf-thor.UUCP or ...!uunet!mcsun!uknet!cf!thor!spedpr
   +++
From: bs@Germany.EU.net (Bernard Steiner)
Newsgroups: comp.unix.bsd
Subject: Re: HELP: wiped out my DOS partition
Date: 13 Oct 1992 10:27:50 GMT
Organization: EUnet Backbone, Dortmund, Germany
Distribution: world
NNTP-Posting-Host: walhalla.germany.eu.net

In article <16808@ksr.com>, dean@ksr.com (Dean Anderson) writes:
> The PC BSD's should look at the dos partition table and create multiple
> logical disk drives, one for each partition.

I beg to differ.
There is no such thing as a "dos partition table" on either of my drives :)

> This has the following benefits:
> 1. Doesn't change machine independent code.  This makes it easier to
> integrate future changes to BSD code, and contribute changes back to
> Berkeley.

Well, the code you propose *is* sort  of machine-dependent, isn't it ?
I mean, I don't have DOS.

> 2. Makes it possible to mount Dos "drives".  A dos vfs is needed.

I recently re-compiled mtools to read the C: drive on some other machine.
The only thing that you really need is yet another definition (disklabel)
for all your DOS fdisk partitions. On a *HUGE* drive you may run into
problems since the number of partitions on a drive is restricted to
eight (if I recall correctly), and on your primary BSD drive at least (I
imagine) the a,b,c and d partitions are pre-allocated (though only c and d are
magic). This doesn't hold for a secondary drive where you are free to use
a and b as you like.

How about making dos vfs aware of the d "partition" only and telling each dosFS
its offset and length ?

> 3. Makes it possible to ignore that dos exists and use the whole drive
> without a dos partition table.  This is particularly attractive is you
> have a large disk,  because dos will not work happilly with disks of
> greater than 1024 cylinders without a lot of egregious hacking which
> ultimately hurts ufs performance.

Huh ? As I said before, DOS doesn't exist, there's no dos partition table...
But then I don't quite understand what you're getting at here.


Cheers,
	Bernard
-- 
Bernard Steiner, FB Informatik/IRB, Uni Dortmund,    vox +49 231 755 2444
Postfach 500500, D-W-4600 Dortmund 50, Germany       fax +49 231 755 2386
bs@Germany.EU.net          ...!uunet!unido!bs

*III  And they gave it Instructions, but knew it not. } From The Book of Nome,
*IV   It is, they said, a Box with a Funny Voice.     }      Mezzanine v.III-IV
Newsgroups: comp.unix.bsd
From: jnpotts@iastate.edu (James N. Potts)
Subject: 386bsd: keyboard & emacs
Organization: Iowa State University, Ames IA
Date: Thu, 8 Oct 1992 06:11:46 GMT

I just got emacs up and running on my machine, and I must say that I'm quit
impressed with it's performance.  However, I am having one problem.  I've been
unable to correctly bind the cursor keys.  Just what sort of control sequence
do these suckers send?  I was assuming the ESC [ A for up business, but that
doesn't seem to work.  I am missing something here?  Do I need to *shudder*
edit the termcap and add something?

Thanks for any help!

James

-- 
_____________________________________________________________________
James N. Potts          |  "To err is human.  To get multiple UAE's 
jnpotts@iastate.edu     |   requires MS Windows."
tabp6@isuvax.iastate.edu|                      - Me
Newsgroups: comp.unix.bsd
From: anything@max.u.washington.edu
Subject: [XFree86]XOpenDisplay cannot open display :0
Organization: 
Date: Wed, 7 Oct 1992 22:08:00 GMT

for some reason I cannot get XFree86 to start. I am using the old
Beta version (1.0.2a) but still it should work. it starts. the screen
blanks and then synchronizes but remains blank and the keyboard is
unresponsive. my equipment is a Diamond Speedstar Plus v5.01 (et4000) and a NEC
multisync II. here is a dump of /usr/X386/lib/X11/xdm/xdm-errors

X386 Version 1.2E 1.0.2a  / X Window System
(protocol Version 11, revision 0, vendor release 5000)
VGA256: et4000 (mem: 1024k numclocks: 16)
VGA256:   clocks: 25 28 81 69  0 29  0  0 13 15 41  0  0  0  0  0
error (pid 87): IO Error in XOpenDisplay
error (pid 85): Display :0 cannot be opened
X386 Version 1.2E 1.0.2a  / X Window System
(protocol Version 11, revision 0, vendor release 5000)
error (pid 89): IO Error in XOpenDisplay
error (pid 85): Display :0 cannot be opened
X386 Version 1.2E 1.0.2a  / X Window System
(protocol Version 11, revision 0, vendor release 5000)
error (pid 91): IO Error in XOpenDisplay
error (pid 85): Display :0 cannot be opened
X386 Version 1.2E 1.0.2a  / X Window System
(protocol Version 11, revision 0, vendor release 5000)
error (pid 93): IO Error in XOpenDisplay
error (pid 85): Display :0 cannot be opened
error (pid 85): Display :0 is being disabled


Don Levinson
anything@max.u.washington.edu
alt: levinson@halcyon.com
Newsgroups: comp.unix.bsd
From: rich@Rice.edu (Richard Murphey)
Subject: Re: /usr/X386/lib/X11/xinit/"files" not there in new X386.
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University
Distribution: usa
Date: Wed, 7 Oct 1992 06:15:29 GMT

In article <1at4gkINN129@gossip.pyramid.com> dinesh@pyramid.COM (Dinesh Jalisatgi) writes:
    As the subject line says there seems to be /usr/X386/lib/X11/xinit directory missing from the

    the new release. Wouuld some kind soul mail me the xinitrc and other files so I can 

    successfully  start startx.

/usr/X386/lib/X11/xinit/xinitrc isn't installed by default.  It's
intended to be customized for each site, so in general you don't want
to overwrite it upon installation of a new release.

xinit and startx should work without it.

Here's a copy.  Rich
----------------------------------------------------------------
#!/bin/sh
# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/usr/X386/lib/X11/xinit/.Xresources
sysmodmap=/usr/X386/lib/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
    xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
    xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
    xmodmap $usermodmap
fi

# start some nice programs

twm &
xclock -geometry 50x50-1+1 &
xterm -geometry 80x50+494+51 &
xterm -geometry 80x20+494-0 &
exec xterm -geometry 80x66+0+0 -name login
Newsgroups: comp.unix.bsd
From: a5050@uwovax.uwo.ca
Subject: Corruption in BIN01.56
Organization: University of Western Ont, London
Date: Wed, 7 Oct 1992 16:45:56 GMT

I had problems when FTP'ing the last file of each distribution set from 
agate to a vax machine. When comparing the file sizes they would be different
For some reason when transfering the files the Vax machine would change the
size of the file, which would cause the extract process to bomb saying
the last file of each distribution set was corrupt. I solved this problem
by setting the transfer to BINARY then set type to IMAGE, this resulted
in the proper number of bytes to be copied.
	Hope this helps
	A.Allison 
	allison@gaul.csd.uwo.ca


Newsgroups: comp.unix.bsd
From: julian@tfs.com (Julian Elischer)
Subject: Re: kernel too large to load
Organization: TRW Financial Systems
Distribution: comp
Date: Fri, 16 Oct 1992 04:04:23 GMT

In article <BOOT.92Oct15130622@donald.osf.org> boot@osf.org writes:
>
>What's the simplest fix if I build a kernel which the boot program
>claims is too large to load? Also, is there any way to go into the
>kernel debugger initially via the boot program? 

the simplest fix is to leave out stuff you don't need
the biggest thiong that can easily be left out is ddb (the kernel debugger)

(assuming you have it), the kernel debugger can be entered by typing -d
to the boot: prompt in the new bootblocks.

Bill Jolitz tells me he is now running kernels loaded above 1MB
that will allow them to be > 640k.

>
>
>-- Bruce
>--
>Bruce Bauman	email: boot@osf.org		phone: 617-621-7205
>Open Software Foundation, 11 Cambridge Center, Cambridge, MA, 02142
BTW bruce, All the scsi drivers I have put on the net here
run without modification under OSF/1.. you guys want 'em, let me know
and I can give you the version of sd.c that goes with osf/1 as well.



+----------------------------------+       ______ _  __
|   __--_|\  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: peter@wiesel.cosy.sbg.ac.at (Peter Burgstaller)
Subject: New XFree86 starting problems
Organization: University of Salzburg / Austria
Date: Fri, 9 Oct 1992 10:26:14 GMT

Hi again!

First, THANKS to all who mailed and newsed!
Now I'm a little bit closer to the solution!

Second: path settings are O.K
	
Here is the result of xdm -nodaemon:

error (pid 88): Can't create/lock pid file /usr/X386/lib/X11/xdm/xdm-pid

But this file exists and has rw permissions for root.
If I delete this file the same thing happens.

Here is the result of xinit >>& xinit.log

XFree86 Version 1.1 / X Window System
(protocol Version 11, revision 0, vendor release 5000)
Configured drivers:
  VGA256 (256 colour SVGA):
      et4000, et3000, pvga1, gvga, ati, tvga8900
VGA256: et4000 (mem: 1024k numclocks: 16)
VGA256:   clocks: 25 28 33 37 41 45 57 65 13 15 17 18 20 23  0  0
VGA256: SpeedUp code selection modified because virtualX != 1024
VGA256: SpeedUp mode selected (Flags=0xf)
failed to set default font path  
'/usr/X386/lib/X11/fonts/misc/,usr/X386/lib/X11/fonts/75dpi/'
Fatal server error:
could not open default font 'fixed'
XIO:  fatal IO error 32 (Broken pipe) on X server ":0.0"
      after 0 requests (0 known processed) with 0 events remaining.
      The connection was probably broken by a server shutdown or  
KillClient.

After that I looked into the fonts directories and found all fonts  
compressed, so I thought maybe I should uncompress them, but this
ends in the same result!

You can see that the clocks aren't 36, 40 or 50 so I changed a little
the values of the 800x600 mode (thats the standard mode for this card)
to

"800x600"	40  800 841 968 1056	600 601 605 628

the screen flips to grafix-mode but apparently with wrong timings

Hey dudes help me to make it through!

- Peter 8*(
--
/-------------------------------------------------------------------\
| Peter Burgstaller| Student of Computerscience			    |
| (peter@cosy.sbg.ac.at)| in Salzburg, Austria (Europe)		    |
| "So Long, and Thanks for All the Fish" (Douglas Adams)	    |
\-------------------------------------------------------------------/
From: shin@nc.u-tokyo.ac.jp (Shin Yoshimura)
Newsgroups: comp.unix.bsd
Subject: Re: X11R5 S3 server for 386bsd 0.1
Date: 16 Oct 92 11:12:58 GMT
	<1992Oct15.141329.11997@rtpnc.epa.gov>
Distribution: comp.unix.bsd
Organization: UTnet Network Operation Center, The University of Tokyo, Japan.
X-Md4-Signature: 3ef85ef85dab25e5649efcedb5db957a

>>>>> On 15 Oct 92 23:13:29 JST, fty@bizarre.rtpnc.epa.gov (Frank Terhaar-Yonkers) said:

>> Amancio's S3 server is archived at: sunvis.rtpnc.epa.gov:~/pub/386bsd/X

I've got it and tried.  But it doesn't work.  Error messages are as follows.

---------------------------
S3 0.0 / X Windows System
(protocol Version 11, revision 0, vendor release 5000)


 clock value: 0 

 clock value: 0 

 clock value: 0 

Fatal server error: Mode couldn't be resolved: "1024x768"
-------------------------- 

My S3 VGA board is "ColorView" made in Taiwan, with 86C911 and 1MB
memory.  It works well with the driver for Diamond Stealth in Win 3.0.

--
$@5HB<!!?-(J
$@El5~Bg3X(J
From: fty@bizarre.rtpnc.epa.gov (Frank Terhaar-Yonkers)
Newsgroups: comp.unix.bsd
Subject: Re: X11R5 S3 server for 386bsd 0.1
Date: 15 Oct 92 14:13:29 GMT
Distribution: comp.unix.bsd
Organization: United States Environmental Protection Agency

Amancio's S3 server is archived at: sunvis.rtpnc.epa.gov:~/pub/386bsd/X

Article  hasty@netcom.com (Amancio Hasty Jr) writes:

> 	X11R5 S3 Server 0.0 for 386bsd 0.1 
> [ lot's of description deleted ]
> I expect to build the 8514/a server for 386bsd 0.1 sometime
> this week.


-- 
-------------------------------------------------
Frank Terhaar-Yonkers	fty@bizarre.rtpnc.epa.gov
Unisys/U.S. EPA		(919)541-2297
Newsgroups: comp.unix.bsd,comp.windows.x
From: rivers@ponds.uucp (Thomas David Rivers)
Subject: Re: XFree86 dumping core on 386BSD...
Date: Wed, 14 Oct 1992 10:20:48 GMT


Well, I'd like to follow up my own posting with some more information.

I'm using an older CompuAdd HI-REZ et4000 card w/ 1meg of memory.  It 
doesn't have all the dot-clocks the newer ones do, so I have to use 
1024x768 interlaced.

Anyway, I found that using a virtual screen of 1152x900 causes ico to
crash the server; using a virtual screen of 1024x1024 does not, and
not using any virtual screen whatsoever does not.

So, to reproduce the problem, use an interlaced 1024x768 mode, and a
virtual 1152x900 screen; then run ico - it should cause the server to
dump core.

	- Dave Rivers -
	(rivers@ponds.uucp)
From: veit@du9ds3.uni-duisburg.de (Holger Veit)
Newsgroups: comp.unix.bsd
Subject: Re: Could the passwd/crypt changes be included in the patch kit?
Date: 8 Oct 92 09:13:04 GMT
Organization: Uni-Duisburg FB9 Datenverarbeitung
Distribution: usa
Reply-To: veit@du9ds3.uni-duisburg.de
NNTP-Posting-Host: du9ds3.uni-duisburg.de

In <1992Oct8.014729.17211@fcom.cc.utah.edu> terry@cs.weber.edu (A Wizard of Earth C) writes:

>In article <1992Oct7.161805.21244@rwwa.COM> witr@rwwa.com writes:
>>In article <1992Oct6.152823.3185@sci34hub.sci.com>,
>>  gary@sci34hub.sci.com (Gary Heston) writes:
>>
>>| The only bypass is for someone outside
>>| the US to write the code, and make it available on a ftp site also outside
>>| the country. 
>>
>>So then, if there were a patch that included a dummy module with comments
>>pointing to such a place, a patch could be distributed, right?
>>
>>So, Terry?  Want to include this in the next Patchkit Beta?

>Can't.  Someone might ftp it from outside the US.

Just curious, there was once a pointer by cgd to extract this crypt from some
package publicly available from uunet. Has it been removed? If so,
there is a copy of this file available at ftp.uni-duisburg.de in
/pub/unix/386bsd-0.1/unofficial, if anyone is in need for encryption.
The algorithm is basically PD, since the scheme and the sboxes have been
published in Scientific American, so I don't understand this paranoic
behavior of the US government (I believe nobody does). The above site is
outside the US, and I won't accept any request of anybody to remove this
file from there, since I have not stolen it anywhere but obtained from a
legal and official site.

>I'll look into getting a license myself, but I doubt that anonymous FTP will
>be an allowable distribution mechanism even if I had one, nor would a news
>posting.

This is a problem for US, but not for the rest of the world.

>					Terry Lambert
>					terry@icarus.weber.edu
>					terry_lambert@novell.com

Holger

-- 
|  |   / Dr. Holger Veit         | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
|  | /   Dept. of Electr. Eng.   |   Sorry, the above really good fortune has
|  |/    Inst. f. Dataprocessing |      been CENSORED because of obscenity"
From: terry@cs.weber.edu (A Wizard of Earth C)
Newsgroups: comp.unix.bsd
Subject: Re: How do I enable COM3 and COM4?
Date: 15 Oct 92 16:29:22 GMT
Article-I.D.: fcom.1992Oct15.162922.24566
Organization: Weber State University  (Ogden, UT)

In article <1992Oct15.014800.729@skitzo.dseg.ti.com> dittman@skitzo.dseg.ti.com (Eric Dittman) writes:
>How do I enable COM3 and COM4 in the binary distribution of 386BSD 0.1
>from agate.berkeley.edu?  Or do I have to do this from the source?

You have to modify the configuration file, config, and rebuild the kernel.
Amacio Hasty (I believe) has put together a "minimum required sources"
tar archive on agate and elsewhere for the rebuilding of kernels for those
with only 40Meg of disk.


					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: rich@Rice.edu (Richard Murphey)
Newsgroups: comp.unix.bsd
Subject: Re: Starting XFree861.1
Date: 14 Oct 92 18:08:41 GMT
Article-I.D.: kappa.RICH.92Oct14120841
	<1992Oct14.121140.28035@autelca.ascom.ch>
Reply-To: Rich@rice.edu
Organization: Department of Electrical and Computer Engineering, Rice
	University

In article <1992Oct14.121140.28035@autelca.ascom.ch> nbladt@autelca.ascom.ch (Norbert Bladt) writes:
   scotty@gagetalker.com (Scott Turner) writes:

   >In article <Bvsr9F.CFv@cosy.sbg.ac.at> peter@wiesel.cosy.sbg.ac.at (Peter  
   >Burgstaller) writes:
   >|> Then I started xinit (also startx) then I got the following 
   >|> Message!
   >|> 
   [ XFree86 starting problem deleted - NB.]

   >Ah, know it well, spent _hours_ on this one myself. It's
   >probably yer mouse. I've got the patched kernel (beta-1) and
   >re-mknod'd my serial ports and I wound up having to use com2
   >to get to com1. :) Of course that was _AFTER_ I figured out
   >I wasn't supposed to be using tty0! Too many hours on the 
   >commercial unixes...
   [ some text deleted - NB. ]

   After reading this (and the README file which came with the patchkit) I
   think I need some help with the setup of the com-ports after applying
   all the patches in the patchkit.

   The information part for the com-port patch (select and re-numbering the
   ports) just contains:
	   "You have to re-mknod your com ports"
   This text without instructions how to do it, is a very useful hint, but
   is not enough for me.

The 386BSD kernel binary distribued with XFree86 is configured for two
com ports.  To create the ports with the proper major and  minor
device numbers use:

mknod /dev/com1 c 8 1
mknod /dev/com2 c 8 2

This will be configured by the x386install in the next release.

   I have 2 com-ports installed on my system but never used one.
   However, I will try to compile X11R5, apply the diff's for XFree86-1.1, etc.
   and will want to use my mouse on one of those com-ports for X. Now, if I do
   have to re-mknod my com-ports how would I do it (I know how it works and which
   program to call, though) ?
   I saw that there was no new "/dev/MAKEDEV" in the patch. So, unless the
   major or minor device-numbers didn't change, I don't need to do new
   mknod's, right ?

   It all burns down to the simple questions:
	   What are the major / minor device numbers for the "new" com-ports ?
   or in other words:
	   Are the major numbers the same (I guess so) or what are they ?
	   Are the minor numbers 0 for com1, 1 for com2, etc. ?

   If somebody can tell me (and other new users of XFree86) what do to exactly
   AFTER you have applied the patches, I am sure, it will save some troubles.

If you use the kernel patches distributed with XFree86, Use the same
numbers as above for the com ports.

I haven't verified that Terry Lambert's patch kit uses the same
numbers, but I would guess that it does.  Rich


   Thanks in advance,

   Norbert.
   -- 
   Norbert Bladt, Ascom Autelca AG, Worbstr. 201, CH-3073 Guemligen, Switzerland
   Phone: +41 31 999 65 52			FAX: +41 31 999 65 44
   Mail: nbladt@autelca.ascom.ch   UUCP: ..!uunet!mcsun!chsun!hslrswi!aut!nbladt