From: aps@ieee.org (Armando Stettner)
Subject: [TUHS] Oldest Unix source code still in modern systems
Date: Mon, 21 May 2012 11:43:10 -0400 [thread overview]
Message-ID: <9F28D643-765D-4A49-B6B5-61A293DA936F@ieee.org> (raw)
In-Reply-To: <alpine.NEB.2.01.1205210950390.4116@t1.m.reedmedia.net>
I would have suspected the oldest source code still existing in systems would be along the lines
/*
* you are not expected to understand this.
*/
:)
aps
Sent from my iPad
On May 21, 2012, at 11:00 AM, "Jeremy C. Reed" <reed at reedmedia.net> wrote:
> On Mon, 21 May 2012, Warren Toomey wrote:
>
>> I was doing a trawl of related Unix source trees, and found that some early
>> C code from around 2nd Edition Unix is still in OpenSolaris today:
>>
>> http://minnie.tuhs.org/cgi-bin/utree.pl?file=V2/cmd/if.c
>>
>> Choose: Compare this file to OpenSolaris_b135/cmd/fmli/sys/test.c
>> and then click on the Side Scroll or the Printable button.
>>
>> There's about 15 lines of code in common between the 2 files.
>
> Cool. I recently did the same thing for BSD.
> http://www.bsdnewsletter.com/2012/05/Features181.html
> Some examples of code that is mostly the same since the first Berkeley
> distribution are: colcrt, expand, mkstr, and soelim. But a few others
> still have some of the original ~1976-1977 code.
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
next prev parent reply other threads:[~2012-05-21 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 5:18 Warren Toomey
2012-05-21 15:00 ` Jeremy C. Reed
2012-05-21 15:43 ` Armando Stettner [this message]
2012-05-21 16:15 ` Michael Davidson
2012-05-22 7:35 ` Dave Horsfall
2012-05-21 7:45 arnold
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=9F28D643-765D-4A49-B6B5-61A293DA936F@ieee.org \
--to=aps@ieee.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).