![]() |
Locking issue. The configuration is referring to same device by two different names (/dev/modem and /dev/ttyS1), which plays small hell with the locks under /var/spool/locks (UUCP locking works badly unless all involved agree on what name to use for a device). The one thing doesn't see the modem locked cuz it's looking for a different device name, and insanity ensues. Quite frankly, I think the /dev/modem symlink misadventure in some distributions didn't do any favors for anyone. -Alan George Zeigler wrote: > > When I went to connect to the internet using kppp in the KDE > environment, I no longer could connect using /dev/modem . The log file > was blank. No AT lines or nothing. > I simply reset the modem to /dev/ttyS1 and no problem. > > I was not having this problem till I added the fx... line in inittab, > so faxgetty is causing the problem. I don't get it. I have my fax > configured direct to /dev/ttyS1 not to /dev/modem , so why would it be > interferring with my symbolic link to /dev/modem