[9fans] Authentication and "emu -d"

[Lucio De Re <lucio@proxima.alt.za>]

Sorry about cross-posting, I'll try not to make a habit of it.

I would like to start Inferno services on my 3ed Plan 9 compute server
using "emu -d".  Two things get in the way:

(a) the ID of the server is "proxima" not "inferno" and that means
that some facilities I previously set up are unavailable.
Authentication is one of these.  If I can track down the
authentication keyfile, I may be able to change its permissions, but
that seems insecure _and_ requires me to put the fileserver in "allow"
mode, a mild pain.  Is there a Plan 9 way of forcing "inferno" to
execute "emu" instead of "proxima", or should I resort to making
"inferno" the compute server owner (Plan 9 AUTH does not run on that
compute server, I still use 2ed AUTH)?

(hm: I did try auth/login - besides requiring to be interactive, it
complains about being run on a compute server :-(

OK, I have now reclassified the compute server so it is owned by
"inferno".  I hope I don't have cause to regret this.  Admittedly, it
does not seem important.

(b) The -d options is wrongly documented: it expects an argument, one
of 0, 1 or 2.  It seems 1 works OK, but I'd like to know what the
other values do.

Also, starting "emu -d1" from cpurc seems to do ugly things to the
keyboard/input interface, the console no longer echoes.  And output
should probably be redirected to a log file, too.  Something for the
manual pages?

++L