From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] Console locking
Date: Sun, 3 Mar 2002 11:26:02 +0200 [thread overview]
Message-ID: <20020303112601.H6416@cackle.proxima.alt.za> (raw)
I'm sure I've asked this question before, but I can't seem to find
the answer anywhere:
Why were the console lock functions removed from the cpu and file
server in 3ed Plan 9? The details have been commented out so I
assume the decision was not utterly final and I'm curious about
the motivation(s) for it.
From where I sit, I don't have enough physical security in place
to protect the auth and file servers (I also like to think that I
don't need that level of protection), so the additional precaution
of locking the console would be quite useful. I'm putting it all
back for that reason and I wonder if that is a silly thing to do.
++L
next reply other threads:[~2002-03-03 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-03 9:26 Lucio De Re [this message]
2002-03-03 15:13 rob pike
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=20020303112601.H6416@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).