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
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Bret Hughes
> Sent: September 13, 2000 4:47 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Problem with mgetty-1.1.22-1.5.x.i386.rpm
>
>
> "Owen V. Gray" wrote:
>
> > I had mgetty-1.1.14-5 working fine on my RH5.2 system.
> >
> > I updated to mgetty-1.1.22-1.5.x.i386.rpm, and got
> the following
> > in my logs:
> >
> > Sep 13 10:23:52 medarb mgetty[20714]: mgetty:
> experimental test
> > release 1.1.22-Aug17: Success
> > Sep 13 10:23:52 medarb mgetty[20714]: check for lockfiles:
> > Success
> > Sep 13 10:23:52 medarb mgetty[20714]: locking the
> line: No such
>
> big snip
>
>
> >
> > I have restored the old version, and it is working as it did
> > before the attempted upgrade.
> >
> > Is there something I was supposed to do to upgrade to the new
> > version, other than run "rpm -Uhv" on the new file
> and restore my
> > mgetty.config file?
> >
> > Owen
>
> Did you set up the /dev/modem symlink to the serial
> port that your modem
> is on?
>
> Bret
>
>
>
> _______________________________________________
> 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
