From: Sam Ducksworth <sam@ducksworth.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: worm problems
Date: Wed, 12 Dec 2001 06:39:07 -0600 [thread overview]
Message-ID: <Pine.BSF.4.33.0112120636490.2577-100000@lucifer.ducksworth.com> (raw)
In-Reply-To: <20011210004903.8211F199B9@mail.cse.psu.edu>
kenji,
thanks, i will give this a try and let you know my results.
--sam
On Mon, 10 Dec 2001 arisawa@ar.aichi-u.ac.jp wrote:
> Hello,
>
> For the safe of fs crash, I have written another backup tool.
>
> -WARNING-
> You should examine this tool carefully by yourself
> before you apply to your system.
>
--sam
next prev parent reply other threads:[~2001-12-12 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-10 0:48 arisawa
2001-12-12 12:39 ` Sam Ducksworth [this message]
2001-12-13 1:27 arisawa
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=Pine.BSF.4.33.0112120636490.2577-100000@lucifer.ducksworth.com \
--to=sam@ducksworth.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).