Is that what you were asking for?

Yes. Aaaaah. Urrrrrgh. It's constructing a lockfile name from the device name, and it's not dealing with the device being in a subdirectory of /dev.

Does anyone know how one is supposed to generate lockfile names from devfs device names?

In the meantime, you should use the backwards-compatibility stuff in devfsd to make it appear as /dev/ttyS<n>.

Peter