Re: modem locking .. I am missing something!

[raoul@earfull.meei.harvard.edu]

-----BEGIN PGP SIGNED MESSAGE-----



Jonathan wrote:
   On Wed, 21 May 1997, Todd T. Fries wrote:

   > holly# ls -l /dev/modem
   > lrwxrwxrwx   1 uucp     uucp            9 May 20 17:19 /dev/modem -> /dev/cua0

   Have you got another process using /dev/cua0? ie getty?

   [As an aside, I am of the opinion that a symbolic link from /dev/modem
    to /dev/cua0 is a bad idea since any lock files generated by any
    *getty programs will have a name that doesn't easily indicate just
    which device it is acutally locking]

I agree also, conceptually. However, a whole stack of linux programs
assume that your modem is on /dev/modem and take hand configuration to
convince otherwise, including "seyon". It's often easier to assume
that the user has linked this correctly than to re-configura any new
software, and so that other users don't have to remember where the !#$
modem line is.

However, there is no reason you can't stash a little "/dev/modem.README"
file with a pointer to the machine's correct serial line and lock file
type....

			Nico Garcia
			Engineer, CIRL 
			Mass. Eye and Ear Infirmary
			raoul@cirl.meei.harvard.edu


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQCVAwUBM4R2Bz/+ItycgIJRAQFwRwQAnyFnwu6O8w0iR2YS+6F7RuTVBOiFTP7Z
9jn8Ju7wMZ5gJkn2NOHDOx22MDUro9fBdTwpaAMVBhVxtU8i7DAckGnZr/NCG6cl
TDDuvFL1J6INlGxCblxs49bZ0thFM9MmFfkBvGxdHtnylNgUxhzBYnhS5cH2VZ81
X/6ND7OQZ6Q=
=09tW
-----END PGP SIGNATURE-----