9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] secstore
Date: Wed, 15 May 2002 10:14:03 -0400	[thread overview]
Message-ID: <cac815a6e9501b0a7ace81cf3e9a406d@plan9.bell-labs.com> (raw)

> Hm, I saw the idea in consolefs(?), but it seemed too good to be true.
> It would seem that with the trivial addition of /dev/null one could
> build an IRC-like facility too :-)

You should hack consolefs if you want a real IRC.  consolefs doesn't
tag what the individual users type with their id.  Also, /dev/null
isn't quite right.  Consolefs only broadcasts what comes out of the
console, i.e., the echo of the typed stuff plus output.  You'ld need
a /dev/echo.  However, if you just hacked consolefs, you could do
away with that and have a real IRC.

> I was considering very seriously going that route for my own array of
> low-power obsoletes, and my main client has a similar need with none
> of the ready expertise I can throw at my equipment.  We use a console
> switch, but that's more out of familiarity than convenience, although
> having a locked computer room does reduce the number of console
> accidents.

Our console server is in the machine room.  No sense putting it anywhere
else.

> The power panel has the advantage of allowing us to power down
> equipment when the UPS batteries risk running out, and power equipment
> back up in a chosen sequence.  You folks are lucky in that you seem to
> have a fairly homogenous system, my client lives in the twilight zone
> of SCO Server, NetBSD (various versions), WinNT and a poorly
> administered network of sundry Win95 workstations.  We seem to be in a
> truce period right now, but I don't expect it to last.

We just do the reset for our debugging machines.  A power panel that
we could remotely shut down would be nice too.  When we lose power someone
has to run in and shut down the machines before the UPS's give up.
Luckily, we only need that on our stand alone machines and the file
servers.  We also have a mixed environment.  Pretty much everything
imaginable is controlled by the plan 9 consolefs.  The admins liked
having secure access to the console server(s).  We have 3 of them now,
there are a lot of machines back there.  We did have to wire DTR high
on the consoles to some machines like the Sparcs, because if our console
server rebooted and DTR went down and up (or is it up and down), the
Suns also rebooted.


             reply	other threads:[~2002-05-15 14:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 14:14 presotto [this message]
2002-05-15 14:37 ` Lucio De Re
  -- strict thread matches above, loose matches on Subject: below --
2002-05-15 18:22 rsc
2002-05-15 16:31 presotto
2002-05-15 16:30 jmk
2002-05-15 16:23 presotto
2002-05-15 15:36 anothy
2002-05-15 15:02 presotto
2002-05-15 14:15 rob pike, esq.
2002-05-15 14:43 ` Lucio De Re
2002-05-15 13:33 presotto
2002-05-15 13:59 ` Lucio De Re
2002-05-15 12:33 presotto
2002-05-15 13:09 ` Lucio De Re
2002-05-15 12:26 nigel
2002-05-15 12:17 presotto
2002-05-15 11:58 nigel
2002-05-15 12:16 ` Lucio De Re
2002-05-15 11:55 presotto
2002-05-15 11:45 forsyth
2002-05-15 11:19 nigel

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=cac815a6e9501b0a7ace81cf3e9a406d@plan9.bell-labs.com \
    --to=presotto@plan9.bell-labs.com \
    --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).