From: ron minnich <rminnich@gmail.com>
To: Aharon Robbins <arnold@skeeve.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] whereis command
Date: Sun, 24 Apr 2022 08:59:57 -0700 [thread overview]
Message-ID: <CAP6exYLOsRcKkRZo12aABR1L_0a7xqNs+=jx_Q0va8vOJ-VxCw@mail.gmail.com> (raw)
In-Reply-To: <202204241548.23OFmGSC002546@freefriends.org>
Thanks.
I did find a newer-ish version and I always get a kick out of stuff like this:
free_dirlist(&ls, ALL_DIRS);
right before the call to exit ... an inappropriate response to an
inappropriate warning, I suppose
I once had an intern ask me "but if you don't free memory before the
program exits, then it can never get used again, right?" :-)
(and yes, I know, in the paleo era, that was in fact true)
I'll go try to find that archive ...
ron
On Sun, Apr 24, 2022 at 8:48 AM <arnold@skeeve.com> wrote:
>
> ron minnich <rminnich@gmail.com> wrote:
>
> > can someone point me at the earliest version of whereis? I first saw
> > it in 4.1, but maybe it came sooner. Also, if you've got a link to man
> > pages, thanks in advance.
> >
> > I'm trying but failing to find it. My daughter says I suck at web
> > search, which, given where I work, is a bid sad :-)
>
> Looks like 2.79 BSD. From the TUHS archives:
>
> $ tar -tzvf 2.79bsd.tar.gz | grep /whereis
> -rwxr-xr-x 0/0 4412 1979-04-21 06:34 bin.v6/ucb/whereis
> -rw-r--r-- 0/0 1692 1981-01-13 17:37 man/whereis.u
> -rw-r--r-- 0/0 4519 1981-01-13 17:37 src/whereis.c
> -rw-r--r-- 0/0 3851 1979-04-19 07:04 upgrade/src/whereis.c
>
> Hope this helps.
>
> Arnold
next prev parent reply other threads:[~2022-04-24 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 15:24 ron minnich
2022-04-24 15:48 ` arnold
2022-04-24 15:59 ` ron minnich [this message]
2022-04-24 16:31 ` David Barto
2022-04-24 18:38 ` John P. Linderman
2022-04-24 16:27 ` Diomidis Spinellis
2022-04-24 16:48 ` Clem Cole
2022-04-24 16:54 ` Clem Cole
2022-04-24 17:39 ` ron minnich
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='CAP6exYLOsRcKkRZo12aABR1L_0a7xqNs+=jx_Q0va8vOJ-VxCw@mail.gmail.com' \
--to=rminnich@gmail.com \
--cc=arnold@skeeve.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).