The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ggm@algebras.org (George Michaelson)
Subject: [TUHS] A man easter-egg (gimme gimme gimme)
Date: Wed, 22 Nov 2017 07:30:04 +0800	[thread overview]
Message-ID: <CAKr6gn0JVd6G66W3ye60pqvY=qY1zYW5uKOwxaAxXkdT-4EbDg@mail.gmail.com> (raw)
In-Reply-To: <CANV78LQzLQacgOhXqQarAChubfFt1_UkczD8Uzct6-Zu0miDQg@mail.gmail.com>

man woman
make love
cat "tin of catfood"

the first two were easter eggs. the last one was just assonance from
"cannot open" error message.

I think they were always tolerated.

But.. then not. The ADA compiler verification committee made York take

"congratulations, you have just invoked the most abstruse element of
the ADA specification"

out of the compiler messages section: it was tickling the test harness
and didn't meet compliance (or so I was told)

On Wed, Nov 22, 2017 at 7:07 AM, Charles Anthony
<charles.unix.pro at gmail.com> wrote:
>
>
> On Tue, Nov 21, 2017 at 1:03 PM, Edouard KLEIN <edouardklein at gmail.com>
> wrote:
>>
>> Hi all,
>>
>> An easter-egg in the version of man that is installed on the most popular
>> Linux distros has recently been discovered after being there for 6 years:
>>
>>
>> https://unix.stackexchange.com/questions/405783/why-does-man-print-gimme-gimme-gimme-at-0030
>>
>> It is for example discussed here:
>> https://news.ycombinator.com/item?id=15747313
>>
>> It makes man print 'gimme gimme gimme' if called at "Half past twelve", as
>> in the ABBA song.
>>
>> I check on BSD, but man seems to be a shell script on FreeBSD, so it's
>> immune from the easter egg:
>> https://github.com/freebsd/freebsd/blob/master/usr.bin/man/man.sh
>>
>> Do you have any UNIX easter-egg stories ? Putting some in, or discovering
>> one...
>>
>> Was this kind of humor tolerated in the professional settings where UNIX
>> first circulated, or was it frowned upon ?
>>
>
> I remember back in the late 90's, the man page for syslogd had a section
> about dealing with network attacks on syslogd servers; several approaches
> described, the last one reading something like
>
>> ....if all else fails, find a three for length of sucker rod* and have a
>> discussion with the user.
>>
>>
>>
>>  *Sucker rod: 3/4 threaded steel rod, used in oil drilling.
>
>
> It looks like someone edited it out of the man pages since then.
>
> -- Charles
>
>


  reply	other threads:[~2017-11-21 23:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21 21:03 Edouard KLEIN
2017-11-21 22:47 ` Charles Anthony
2017-11-21 23:00 ` Dave Horsfall
2017-11-21 23:07 ` Charles Anthony
2017-11-21 23:30   ` George Michaelson [this message]
2017-11-22  0:51     ` Dave Horsfall
2017-11-23 22:39       ` George Michaelson
2017-11-23 19:17     ` Ron Natalie
2017-11-23 21:22       ` Ralph Corderoy
2017-11-21 23:30   ` Henry Bent
2017-11-22  8:48 ` arnold
2017-11-22  9:50   ` Andreas Kusalananda Kähäri
2017-11-22 16:00   ` Ian Zimmerman
2017-11-22 16:11     ` arnold
     [not found]       ` <CANCZdfq=KBrpYsMq5BZxjTOce694qVaJ0Pp7aeKHV9ecsBD2YQ@mail.gmail.com>
2017-11-23 12:09         ` arnold
     [not found]   ` <CAJfiPzwvxRaQXanEmvkfeTKp=QMtiAFhCOaWDHyfHRihJ4_nFQ@mail.gmail.com>
2017-11-24 15:33     ` Nemo
2017-11-23 19:45 Noel Chiappa

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='CAKr6gn0JVd6G66W3ye60pqvY=qY1zYW5uKOwxaAxXkdT-4EbDg@mail.gmail.com' \
    --to=ggm@algebras.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).