From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] fresh compiled kernels no longer boot..?
Date: Mon, 26 Jan 2004 01:52:50 +0100 [thread overview]
Message-ID: <09e801c3e3a6$b9e9f620$67844051@SOMA> (raw)
In-Reply-To: <200401260013.i0Q0DBi08626@zamenhof.cs.utwente.nl>
> ... (and I'm pleasantly surprised that just adding some print statements
> and taking the serial cable was sufficient to locate the problem -
> though I'm sure in this sense it will not be representative)
never underestimate the power of judiciously placed print[f]'s as a
debugging tool.
next prev parent reply other threads:[~2004-01-26 0:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-25 22:05 Axel Belinfante
2004-01-25 22:37 ` David Presotto
2004-01-25 23:02 ` jmk
2004-01-25 23:12 ` Axel Belinfante
2004-01-25 23:43 ` Axel Belinfante
2004-01-25 23:52 ` jmk
2004-01-26 0:13 ` Axel Belinfante
2004-01-26 0:52 ` boyd, rounin [this message]
2004-02-11 23:30 ` matt
2004-02-12 2:54 ` boyd, rounin
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='09e801c3e3a6$b9e9f620$67844051@SOMA' \
--to=boyd@insultant.net \
--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).