From: grog at lemis.com (Greg 'groggy' Lehey)
Subject: [COFF] 21st Century Equivalent to 'learn'?
Date: Fri, 6 Mar 2020 14:14:12 +1100 [thread overview]
Message-ID: <20200306031412.GF85938@eureka.lemis.com> (raw)
In-Reply-To: <E8E8CA50-7AEA-4893-8045-7DF3D51C35D6@alchemistowl.org>
On Thursday, 5 March 2020 at 22:23:31 +0100, Arrigo Triulzi wrote:
> Someone (sorry, lost the message by deleting it and discovered I
> don't archive COFF...) mentioned that "learn" is still around in BSDs
> but I didn't find it in either FreeBSD or OpenBSD (base or
> packages). Where should I look? Or was it a "compile it off
> 4.4BSD????
Interesting. I took a quick look around my (FreeBSD) machine and
located a directory /home/src/OpenBSD/3.0-RELEASE/usr.bin/learn/,
dating from October 2001. It no longer compiles with clang, but a
quick attempt with gcc and without (clang) default flags at least
produces object files.
I've put a tarball at http://www.lemis.com/grog/src/learn.tar
Greg
--
Sent from my desktop computer.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200306/a45749e4/attachment.sig>
next prev parent reply other threads:[~2020-03-06 3:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 3:49 wkt
2020-03-04 6:23 ` spedraja
2020-03-04 6:55 ` thomas.paulsen
2020-03-04 9:53 ` wkt
2020-03-04 19:31 ` dave
2020-03-05 1:00 ` wkt
2020-03-05 12:43 ` jpl.jpl
2020-03-05 21:23 ` arrigo
2020-03-06 3:14 ` grog [this message]
2020-03-06 9:10 ` akosela
2020-03-07 21:50 ` dave
2020-03-07 22:05 ` clemc
2020-03-07 23:02 ` dfawcus+lists-coff
2020-03-08 0:02 ` clemc
2020-03-06 3:39 ` bakul
2020-03-12 20:53 ` rtomek
2020-03-08 3:39 rudi.j.blom
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=20200306031412.GF85938@eureka.lemis.com \
--to=coff@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).