From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] vga and ethernet
Date: Sat, 4 Aug 2001 03:09:14 +0200 [thread overview]
Message-ID: <046801c11c82$13dad800$3cf7c6d4@SOMA> (raw)
In-Reply-To: <9kcj9u$s37$1@inputplus.demon.co.uk>
> > I read something that stuck with me forever -- one's programs will be
> > much more readable if ambiguity over character interpratation (l vs 1
> > vs I, O vs 0 in some fonts, etc) is avoided.
slam the wrong thing into a pdp 11 kernel segment permission/mode
register and your kernel crashes. mine did. all due to a zero/O
problem. at least the rl-02's didn't get smashed.
next prev parent reply other threads:[~2001-08-04 1:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 16:53 baldwin
2001-08-01 17:59 ` andrey mirtchovski
2001-08-03 9:05 ` Ralph Corderoy
2001-08-04 1:09 ` Boyd Roberts [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-08-01 17:09 Dean Ash
2001-07-31 19:07 [9fans] vga and Ethernet Dean Ash
2001-07-31 12:04 [9fans] vga and ethernet presotto
2001-07-31 3:41 Dean Ash
2001-07-31 4:08 ` Lucio De Re
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='046801c11c82$13dad800$3cf7c6d4@SOMA' \
--to=boyd@fr.inter.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).