From: Lucio De Re <lucio@proxima.alt.za>
To: "Fco.J.Ballesteros" <nemo@plan9.escet.urjc.es>
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] waserror()/nexterror()
Date: Fri, 16 Jan 2004 11:38:45 +0200 [thread overview]
Message-ID: <20040116113845.O25947@cackle.proxima.alt.za> (raw)
In-Reply-To: <da7a0232b8e2e8b06744fc11db20b1f8@plan9.escet.urjc.es>; from Fco.J.Ballesteros on Fri, Jan 16, 2004 at 10:20:33AM +0100
On Fri, Jan 16, 2004 at 10:20:33AM +0100, Fco.J.Ballesteros wrote:
>
> Section on error handling in the Plan 9 kernel notes,
> or drop me a line off-list and I'll try to explain.
4.3 Error handling
Thank you. That will do for starters.
You may be able to help me with a totally different problem: I have
a set of VXL-Percios, thin client hardware that I'd like to have
running Plan 9. They are just SiS550s in a box, with the obvious
and not so obvious peripherals (2xUSB and no serial ports). 2ed
plan 9 kernel boots, but can't recognise the realtek ether chip,
whereas something very early in the 4ed kernel startup (before any
printed announcements) causes the kernel to reset the host.
I haven't quite been tempted to boot the 3ed kernel, nor to mess
around with kernel sources as I seem to have a rather confused
distribution on my production server.
It's just that debugging those first few procedures in main() that
precede setting up printing seems a formidable task. What can you
suggest?
In return, your notes ought to become a proper set of man pages,
the way the NetBSD folks have structured their section 9. If you
head in that direction, I'd love to help you.
++L
next prev parent reply other threads:[~2004-01-16 9:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 9:17 Lucio De Re
2004-01-16 9:20 ` Fco.J.Ballesteros
2004-01-16 9:38 ` Lucio De Re [this message]
2004-01-16 10:00 ` Lucio De Re
2004-01-16 11:49 ` Charles Forsyth
2004-01-16 15:37 ` jmk
2004-01-16 18:42 ` Lucio De Re
2004-01-16 20:42 ` jmk
2004-01-17 6:38 ` Lucio De Re
2004-01-16 15:42 ` ron minnich
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=20040116113845.O25947@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
--cc=nemo@plan9.escet.urjc.es \
/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).