9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dave Lukes <davel@anvil.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] port/devcons.c is not port-able
Date: Wed, 14 Jul 2004 15:04:58 +0100	[thread overview]
Message-ID: <40F53D8A.4080005@anvil.com> (raw)
In-Reply-To: <8475f74f8d5360fd4262360f61aae5fa@juice.thebigchoice.com>

Problem is, when there's a "panic: smashed stack" type condition,
after that, the only complexity that matters is the complexity of the
code path leading to the characters becoming humanly visible.

I tend to agree with (?jmk?) that serial lines and terminal servers are
the way to go for the moment:
the serial line gets the bits easily out of the danger zone (the dying
machine),
and you can then log them at leisure.

As to the future, I'm sure that we'll all have USB consoles in a few
years.  Oh, joy.

<thought>
Is there any space in nvram where one could dump the last N bytes of
console output?
At least that way you'd be able to see it eventually ...

Of course, what would be cool would be a "panic display": an lcd with
some nvram that keeps the last message in it.
</thought>

DaveL.

matt@proweb.co.uk wrote:

>Hi Ron,
>
>I thought it sounded like a good idea it's just not something I feel qualified to comment on
>
>being able to set consoles in plani.ini to console=+/tcp/host/875
>sounds like it adds flexibility while, if your coding assumptions are correct, it reduces complexity elsewhere
>
>m
>
>



  parent reply	other threads:[~2004-07-14 14:04 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 13:57 ron minnich
2004-07-14  1:24 ` Geoff Collyer
2004-07-14  2:10   ` ron minnich
2004-07-14  2:30     ` Geoff Collyer
2004-07-14  2:47       ` ron minnich
2004-07-14  2:34     ` andrey mirtchovski
2004-07-14  2:47       ` ron minnich
2004-07-14  2:51         ` Kenji Okamoto
2004-07-14  4:40           ` Dan Cross
2004-07-14 13:33           ` OT: " Dave Lukes
2004-07-14 14:08             ` ron minnich
2004-07-14 15:31               ` Jack Johnson
2004-07-14  5:00         ` Skip Tavakkolian
2004-07-14 10:34         ` matt
2004-07-14 14:04           ` ron minnich
2004-07-14 14:04           ` Dave Lukes [this message]
2004-07-14 15:03             ` ron minnich
2004-07-14 16:13               ` boyd, rounin
2004-07-14 14:52           ` boyd, rounin
2004-07-14  2:49       ` Kenji Okamoto
2004-07-14  4:36       ` Dan Cross
2004-07-14  2:38     ` Kenji Okamoto
2004-07-14  2:49       ` ron minnich
2004-07-14  5:15         ` Geoff Collyer
2004-07-14  6:36           ` Geoff Collyer
2004-07-14 13:47           ` ron minnich
2004-07-14 18:29             ` Dan Cross
2004-07-14 18:53               ` boyd, rounin
2004-07-14 19:42               ` ron minnich
2004-07-14 20:14                 ` Charles Forsyth
2004-07-14 20:19                 ` Frank Palazzolo
2004-07-14 20:18                   ` Charles Forsyth
2004-07-14 21:06                     ` Geoff Collyer
2004-07-14 21:31                   ` boyd, rounin
2004-07-14  4:31 ` Dan Cross
     [not found] <00aba352392cbadebd943e05d1e17412@plan9.ucalgary.ca>
2004-07-15  3:14 ` Geoff Collyer

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=40F53D8A.4080005@anvil.com \
    --to=davel@anvil.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).