9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Authentication and "emu -d"
Date: Mon,  4 Jun 2001 11:45:57 +0200	[thread overview]
Message-ID: <20010604114557.D26399@cackle.proxima.alt.za> (raw)
In-Reply-To: <20010604091637.07ABF199D5@mail.cse.psu.edu>; from forsyth@caldo.demon.co.uk on Mon, Jun 04, 2001 at 10:12:34AM +0100

On Mon, Jun 04, 2001 at 10:12:34AM +0100, forsyth@caldo.demon.co.uk wrote:
> 
> that really is inferno-specific, so we'll answer it in detail on that list.
> 
> i'd thought we left -d deliberately undocumented
> but i see it is there in the manual page after all.
> 
Security by obscurity (or, in this case, "d" for disinformation :-)
You'll eventually be pleased to have been caught with your pants down,
the idea is good, definitely in the list of nice-to-haves.

> >>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
> 
> this is just the superficial reason i intended to leave it
> undocumented.  it was left in the code because one group might have
> been using it at the time, under Solaris, for which it was originally
> hacked in (where hacked is the right description), in a hurry.  i
> suppose you could wonder: if it can't cope with the console correctly,
> how is it likely to do on the hard bits?  that gets close to the
> truth.  it does only what it was intended to do,
> but doesn't go far enough, even though they did hire a web page designer!
> anyway, someone will send more about it to the inferno list later.


Well, _I'm_ using it, on a CPU server that sits practically headless
(and could be headless if I had more faith - Microsoft keep rattling
my faith and it bleeds over all the other OSs in my life :-)

It will be just fine the way it is, and as soon as "I can get my
pennies together for the source licence (TM)" I'll see if I can help
smooth some of the wrinkles out.

Just of the record , would "emu -d1 </dev/null >/dev/null >[2=1]"
break, or can I safely try it without losing what little mind I still
have left?

(My answer to that, in your shoes, might be "you tell us", but I'm
going to need some encouragement to tackle such obviously tangential
operations, I don't do elective surgery :-)

++L

PS: Re-reading your answer, it would seem that "emu" has two closely
coupled functions that could do with some decoupling, namely "dis"
emulation and graphics (I'm reading between the lines, I get the
feeling "emu -d"'s failing lies in the management of interaction with
its environment).  Perhaps discarding the graphics baggage is an
option?  Sounds tough to do, for little gain, but there's something to
be said for text-only interactions, and Plan 9 ain't going that way,
perhaps Inferno can.


  reply	other threads:[~2001-06-04  9:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-04  9:12 forsyth
2001-06-04  9:45 ` Lucio De Re [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-04 11:56 presotto
2001-06-04 10:06 forsyth
2001-06-04 10:36 ` Lucio De Re
2001-06-04  8:51 Lucio De Re

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010604114557.D26399@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).