Has anyone on the list updated mgetty on a RH5.2 box to
mgetty-1.1.22-1.5.x.i386.rpm without encountering the
difficulties described in my original post?
Owen
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Charles Galpin
> Sent: September 14, 2000 1:05 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Problem with mgetty-1.1.22-1.5.x.i386.rpm
>
>
> The issue with using /dev/modem or /dev/ttyS2 is with
> sharing. You just
> have to be consistant with which one you use, because
> if you mix and
> match, each seperate program will not "place nice"
> with the others. If you
> use the smae name across the board, then they will
> cooperate with each
> other (as best they can anyway)
>
> hth
> charles
>
> On Thu, 14 Sep 2000, Bret Hughes wrote:
>
> > "Owen V. Gray" wrote:
> >
> > > No, I don't use a /dev/modem symlink. The mgetty
> documentation
> > > recommends against using it, and mgetty-1.1.14
> works fine using
> > > /dev/ttyS2 directly. I've looked at the
> documentation for the new
> > > version, and it does not seem to have changed in
> this regard.
> > >
> > > Is there something about the redhat-added patches that now
> > > requires this?
> > >
> > > Owen
> >
> > Not that I know of, I just remembered there was and
> issue with some
> > programs needing it.
>
>
>
> _______________________________________________
> Redhat-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
