🚀 go-pugleaf

Joe Tseng <jtseng@gwyn.tux.org> writes:

>I was browsing through a post in the Red Hat users list (re: minicom) and
>this person mentioned mgetty being reserved for use on cua1.  

I do assume that you mean that mgetty controls the use of that port.
Otherwise the statement would be ridiculously incorrect - you may
run mgetty on any serial or ISDN port you want it to be listening to.

>Is it
>possible a process can block access to a card hanging off that port?

Sure. This is printed in three-mile-high letters in the mgetty
documentation, the Serial-HOWTO etc.

>The reason I ask is because I cannot change the com port jumper on my
>USR288 internal modem to anything other than com4.  If I did physically
>change the jumper configuration, my BIOS would bitch. 

And what is your problem now ?
If you have your internal modem setup as COM4, you'll need to
assign an unused IRQ to that port by using "setserial" .

BTW, if your BIOS does protest against anything else but COM4, you
may want to correct your BIOS settings. Or upgrade the BIOS.

Michael
-- 
   Michael Buchenrieder * mibu@scrum.muc.de / mibu@scrum.greenie.muc.de 
**************************************************************************
Satellite Safety Tip #4:
		If you see a bright streak in the sky coming at you, duck.