mgetty-1.1.9 on Solaris2.5.1/Sparc

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

Martin Spott wrote:
> > Hmmm. I'd say "there is no lock file from Minicom with *that* name
> > here". [...]
> 
> This is quite true. The mgetty lockfile is this one:
> 
> -rw-r--r-- 1 root  root   11 Dec 17 17:56 LK.032.029.131073

This is how things on SVR4-derived things have to be (the lock file name
is made from major/minor device number and filesystem device number).

> The minicom lockfile looks to be this one:
> 
> -rw-r--r-- 1 martin user   26 Dec 17 17:56 LCK..b

This is broken.

> So how do I convince mgetty to accept these lockfile names ?
> I configured mgetty like this:
> 
> # define LOCK_PATH "/var/lock"
> # define LOCK "/var/lock/LCK..%s
> #define LOCKS_BINARY 0

On SVR4, things are done "automagically" in locks.c, I think you will have
to add an "#undef SVR4" to the top of locks.c to make it use standard file
names.

Far better, fix minicom (because SVR4 uucp and all other tools will rely
on the scheme that mgetty uses).

gert

-- 
USENET is *not* the non-clickable part of WWW!
           //www.muc.de/~gert/
Gert Doering - Munich, Germany      gert@greenie.muc.de
fax: +49-89-35655025    gert.doering@physik.tu-muenchen.de
.