As I was used to agetty and minicom cooperating nicely on an ancient Slackware box, I expected this to work on this much more recent Debian box <sigh>.
I use mgetty at home, but didn't really want to have to deal with its complexities for the situation at hand. The situation's more or less under control, so I won't worry about the problem further, although I was disappointed not be able to find the getty source package. Regards, Andrew. <[EMAIL PROTECTED]> - - - - - - - - - - - - - - Original Message - - - - - - - - - - - - - - From: Miquel van Smoorenburg <[EMAIL PROTECTED]> Subject: Re: getty vs minicom Date: 07/16/99 19:38 In article <[EMAIL PROTECTED]>, Marc Mongeon <[EMAIL PROTECTED]> wrote: >Andrew: > >I believe that this is exactly how lock files are supposed to work. When >getty is active, it is using the serial port, and no other application should >be able to access it. Well, yes, that's probbaly what it doesn, but it's not very smart. Use mgetty - it's smarter. It only creates a lockfile when someone dials in, and if it detects activity while a lockfile is already present it assumes you're using minicom on the serial port and just steps aside until you're done (when the minicom lockfile disappears). Mike. -- Beware of Programmers who carry screwdrivers. -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
