HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: Large number of errors with Hylafax and ZyXEL Omni modem
- Subject: Re: flexfax: Large number of errors with Hylafax and ZyXEL Omni modem
- From: Nico Garcia <raoul@cirl.meei.harvard.edu>
- Cc: Hylafax Mailing List <flexfax@sgi.com>
- Date: Wed, 8 Apr 1998 11:38:17 -0400 (EDT)
-----BEGIN PGP SIGNED MESSAGE-----
On Wed, 8 Apr 1998, Robert Colquhoun wrote:
> Hi Nico,
> I can appreciate your problems with the redhat tools. But i honestly think
> you could make the situation alot worse if you start recommending cua over
> ttyS devices. If someone later loads a 2.1 kernel which alot of people are
> doing it is going to break badly, also when 2.2 is finally released hylafax
> will need also to be reconfigured.
Fair enough. But that configuration is done as a an after-installation
step, or (I think) should be. I'd prefer to let users use the modem
configuration tool and default minicom settings: if HylaFAX needs to
change with the 2.1 kernel, (which it probably will), I think the
/dev/modem notes can be re-written.
> Also i believe the latest Debian systems by default dont instantiate the
> cua devices so installing a hylafax rpm that there would be challenging for
> most users.
??? You mean they don't *have* one, or they use ttyS*, or what?
> As for PPP i have got a working setup that uses mgetty - incoming terminal
> and PPP sessions are handled automatically. I can send you the info if you
> want.
This would be good: I've got a working diald setup, which I'll add notes
about in the future to my web page. If your setup is better, or you've
noticed stuff I missed, I'd be delighted to get your notes and give
attributions.
Nico Garcia
Senior Engineer, CIRL
Mass. Eye and Ear Infirmary
raoul@cirl.meei.harvard.edu
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBNSuZzj/+ItycgIJRAQGoZAP/eZfVqiAkouii73RnwSGeMiBkKB5vL07g
gKwMwmFKEGxH/d6GxE+0ChqbpblIRa4YyqM/BE53jN0GYTly9IaXYIQtjBpi2IhE
7jlBs2kzt/Y90Gk07U9Qsnrt9TZW95q32ytG0o3m/7eguX0rKKseMmSpIBX1ncl5
znTETSG34L0=
=LghH
-----END PGP SIGNATURE-----