From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] retry with aescbc
Date: Wed, 16 Oct 2002 09:49:27 +0100 [thread overview]
Message-ID: <b97f16900ee7015e8ab5a81f1e1de6f0@caldo.demon.co.uk> (raw)
i suggested
>>> ramfs -m /n/kremvax >[2] /dev/null #suppress unmount message
>
> those that worry can include -p to make ramfs's memory private
> for the short time it lives.
but of course there was more to protect than just ramfs in that interaction.
next reply other threads:[~2002-10-16 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 8:49 Charles Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-18 3:02 Russ Cox
2002-10-16 8:29 Charles Forsyth
2002-10-16 2:48 rob pike, esq.
2002-10-18 2:59 ` Micah Stetson
2002-10-16 2:05 rob pike, esq.
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=b97f16900ee7015e8ab5a81f1e1de6f0@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).