getty vs minicom
I have a debian 1.3.1 system on which I have a modem for
periodic remote access. Dial-in has worked nicely for some
time. However I needed to check/reset the modem
configuration, so I fired up minicom (cu isn't my cup of tea,
and I've previously used minicom to do this, but not on this
system) only to have it tell me that the port was in use.
If I deactivate the getty, minicom is quite happy to talk to the
modem, which lead me to check minicom's port lock file
settings.
It makes no difference whether I set the lock directory to
/var/lock or /var/spool/uucp (this system doesn't have a
/var/spool/uucp/lock directory).
Any ideas? BTW, minicom is v1.75 and getty is v1.45a
(according to dselect), and minicom was installed from
the package distributed as part of bo.
Arising from the above, I went looking for the source to
getty (agetty actually), and was disappointed to find that
there appears to be no readily accessible copy of getty's
source.
"dpkg --search /sbin/getty" tells me that the package is
"base/getty". If there is such a package, it doesn't exist
anywhere on the debian {web|ftp}site that I could find,
in either binary or source form. This applies to slink as
well as bo (I went and looked at the archives as well).
-
Andrew MacIntyre\ [EMAIL PROTECTED]
Planning & Licensing Branch \ Tel: +61 2 6256 2812
Australian Broadcasting Authority \ Fax: +61 2 6253 3277
Re: Re: getty vs minicom
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 . 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
Re: getty vs minicom
Miquel van Smoorenburg wrote: >According to Andrew MacIntyre: >> 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 . > >That is because that worked with the cua/ttyS devices (kernel based >locking between dialin/dialout) which has officially been deprecated >by the linux kernel developers. Thanks for the explanation. >> I use mgetty at home, but didn't really want to have to deal with >> its complexities for the situation at hand. > >Complex? Mgetty? mgetty -s 38400 /dev/ttyS1 ? Complex because I used the fax enabled version - it didn't sink in that there was a package without the fax support. >> 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. > >Source of both agetty and mgetty is available on all debian mirrors. Could you tell me where then please. AFAICT, getty is packaged as base/getty, however such a package appears not to exist, either source or binary. mgetty I found w/o any probs. BTW apologies if this message appears poorly formatted - I have attempted to manually format it but the web-based mail interface I'm using appears to not respect explicit CRs in a paragraph :-( Regards, Andrew MacIntyre <[EMAIL PROTECTED]>
Re: Re: getty vs minicom
On the bo (1.3.1) system I tried this on, I got: vesta# dpkg -S /sbin/getty getty: /sbin/getty Which as I said, lead me up a blind ally. >From your response, I have just tried: vesta# dpkg -s getty Package: getty Essential: yes Status: install ok installed Priority: required Section: base Installed-Size: 40 Maintainer: Guy Maor <[EMAIL PROTECTED]> Source: poeigl Version: 1.45a-3 Pre-Depends: libc5 (>= 5.4) Description: agetty, an alternative Linux getty agetty is the standard Debian getty. It is a SYSV/SunOS4 getty program with useful features for hardwired and dial-in tty lines. So the source package I should have been looking for was base/poeigl, which I have now found. Unfortunately the document I was following didn't warn of the possibility of the source package not being named the same as the binary package, and I missed the -s option to dpkg. Not to worry, case closed. Many thanks for your helpful response. am - - - - - - - - - - - - - - Original Message - - - - - - - - - - - - - - From: Miquel van Smoorenburg <[EMAIL PROTECTED]> Subject: Re: getty vs minicom Date: 07/19/99 18:34 According to Andrew MacIntyre: > >Source of both agetty and mgetty is available on all debian mirrors. > > Could you tell me where then please. AFAICT, getty is packaged as > base/getty, however such a package appears not to exist, either > source or binary. mgetty I found w/o any probs. It's in util-linux: % dpkg -S /sbin/getty util-linux: /sbin/getty For some packages the name is different from the source package; in that case, you'd have to do a 'dpkg -s binary-package' to find out the source package (it's the Source: line) but that's not the case for util-linux. The source package for util-linux is simply called util-linux. Mike. -- ... somehow I have a feeling the hurting hasn't even begun yet -- Bill, "The Terrible Thunderlizards"
