From: Mike Markowski <mike.ab3ap@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Masscomp oops [was: Any Good dmr Anecdotes?]
Date: Fri, 29 Jun 2018 22:27:38 -0400 [thread overview]
Message-ID: <353c4003-d61c-356f-2601-53ce03453c68@gmail.com> (raw)
In-Reply-To: <20180630013128.GC18031@mcvoy.com>
On 06/29/2018 09:31 PM, Larry McVoy wrote:
> [...] (I was not a wizard but I've lived through, and
> written up, the process of restoring a Masscomp after having done some
> variant of rm -rf / so a stupid wizard wanna be?)
That reminds me of preparing a Masscomp to bring out in the field for
radar data acquisition. After some minor incident, I needed to run an
fsck when a cute, slender gal came into the lab. In my flustered state
hoping to start a witty conversation I typed mkfs... Unfortunately, no
wizards around, let alone dmr, to save the day - which turned into a
very late day. On the plus side, I ended up marrying the girl.
Mike Markowski
next prev parent reply other threads:[~2018-06-30 5:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 1:31 [TUHS] Any Good dmr Anecdotes? Larry McVoy
2018-06-30 1:45 ` Jon Forrest
2018-06-30 18:43 ` Steve Johnson
2018-06-30 2:27 ` Mike Markowski [this message]
2018-06-30 17:37 [TUHS] Masscomp oops [was: Any Good dmr Anecdotes?] Noel Chiappa
2018-06-30 19:13 ` Mike Markowski
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=353c4003-d61c-356f-2601-53ce03453c68@gmail.com \
--to=mike.ab3ap@gmail.com \
--cc=tuhs@minnie.tuhs.org \
/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).