From: baldwin@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan9 can't fly
Date: Wed, 30 May 2001 19:27:27 -0400 [thread overview]
Message-ID: <20010530232728.B26E619A36@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 73 bytes --]
Viewing at 7, cremation at 10.
Donations to Matt in lieu of flowers.
[-- Attachment #2: Type: message/rfc822, Size: 2029 bytes --]
To: <9fans@cse.psu.edu>
Subject: [9fans] plan9 can't fly
Date: Thu, 31 May 2001 00:16:12 +0100
Message-ID: <002001c0e95e$84d28280$6401a8c0@freeze2k>
I was just carrying my plan9 box downstairs and slipped and fell.
I had to throw the PC so I could save myself and to stop it landing on me.
When it landed the case crushed the drives into the motherboard and now it
won't even power up.
Any ideas?
Matt
next reply other threads:[~2001-05-30 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 23:27 baldwin [this message]
[not found] <200105311301.OAA08128@pw001.proweb.co.uk>
2001-06-04 21:56 ` Matt
[not found] <200105310453.FAA22218@pw001.proweb.co.uk>
2001-05-31 8:59 ` Matt
-- strict thread matches above, loose matches on Subject: below --
2001-05-30 23:19 jmk
2001-05-30 23:16 Matt
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=20010530232728.B26E619A36@mail.cse.psu.edu \
--to=baldwin@vitanuova.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).