From: Katherine Barto <barto@kdbarto.org>
To: Norman Wilson <norman@oclsc.org>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] FreeBSD retires gets()!
Date: Tue, 26 Nov 2019 15:06:14 -0800 [thread overview]
Message-ID: <300A9E4F-27B8-4A1A-ADB2-A9220CC6CFF3@kdbarto.org> (raw)
In-Reply-To: <1574805575.17040.for-standards-violators@oclsc.org>
On Nov 26, 2019, at 1:59 PM, Norman Wilson <norman@oclsc.org> wrote:
>
> We also decided to retire the old Enigma-derived crypt(1),
> except we didn't want to throw it out entirely in case
> someone had an old encrypted file and wanted the contents
> back. So it was removed from the manual and the binary
> moved to /usr/games.
I particularly like that the old crypt was reduced to a game.
David
next prev parent reply other threads:[~2019-11-26 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 21:59 Norman Wilson
2019-11-26 22:31 ` George Michaelson
2019-11-26 22:32 ` Dave Horsfall
2019-11-26 23:29 ` Richard Salz
2019-11-27 0:29 ` Dave Horsfall
2019-11-26 23:06 ` Katherine Barto [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-26 21:10 Dave Horsfall
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=300A9E4F-27B8-4A1A-ADB2-A9220CC6CFF3@kdbarto.org \
--to=barto@kdbarto.org \
--cc=david@kdbarto.org \
--cc=norman@oclsc.org \
--cc=tuhs@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).