From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lucio De Re To: "Fco.J.Ballesteros" Cc: 9fans@cse.psu.edu Subject: Re: [9fans] waserror()/nexterror() Message-ID: <20040116113845.O25947@cackle.proxima.alt.za> References: <20040116111729.N25947@cackle.proxima.alt.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: ; from Fco.J.Ballesteros on Fri, Jan 16, 2004 at 10:20:33AM +0100 Date: Fri, 16 Jan 2004 11:38:45 +0200 Topicbox-Message-UUID: baa27756-eacc-11e9-9e20-41e7f4b1d025 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