From: Warner Losh <imp@bsdimp.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Deleted lib1 and lib2 in v6, recoverable?
Date: Sat, 29 Dec 2018 09:49:29 -0700 [thread overview]
Message-ID: <CANCZdfpMpOzLD_iiuoG6gyNKAPM7wGVm7_yxoW0KVQKvQjbLYQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2MiHqMJb_wC4ccng_sy7q+A94OiGj5G0cwLRH6oftaO6Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On Sat, Dec 29, 2018, 11:27 AM Clem Cole <clemc@ccc.com wrote:
>
>
> On Fri, Dec 28, 2018 at 11:59 PM Warren Toomey <wkt@tuhs.org> wrote:
>
>> Yes, order will be important, I forgot. There's no ranlib in v6 :-)
>>
>
> Good point. I've forgotten as to where and when did ranlib appear in
> the dev stream? Was it research, UCB or somewhere else like on the
> Harvard Tape?
>
> Just now, I took a quick peak at the 1BSD archive on TUHS.org but the
> subdirtectories are all packed up as v6 ar archives (cont.a files) -
> *i.e.* when somebody converted the BSD stp tape to a tar image they just
> wrote the archive and then rewrote it as a compressed tar ball. So I will
> take a little more work to unpack them, ensure the dates are 1978 based.
> (which I'll do at some point and offer them back to Warren).
>
> But I do remember when ranlib showing up it was such a win for fixing C
> compiler (well linkage) errors. I could have sworn, we had it was before
> V7, so maybe it came with the Typesetter C or UNIX/TS stuff.
>
But wasn't it tsort that did the heavy lifting to get things in order?
ar c foo.a `tsort *.o`
Ranlib just made it fast by adding an index..
Warner
> ᐧ
>
[-- Attachment #2: Type: text/html, Size: 2869 bytes --]
next prev parent reply other threads:[~2018-12-29 16:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-29 1:09 Noel Chiappa
2018-12-29 1:26 ` Will Senn
2018-12-29 1:35 ` Warren Toomey
[not found] ` <82e23dba-38a4-3ee4-e35a-6293b8eef749@gmail.com>
2018-12-29 4:59 ` Warren Toomey
2018-12-29 16:26 ` Clem Cole
2018-12-29 16:49 ` Warner Losh [this message]
2018-12-29 17:48 ` Clem cole
2018-12-30 18:34 ` Paul Winalski
2018-12-30 18:48 ` ron
2018-12-30 18:56 ` Warner Losh
2018-12-30 19:02 ` Paul Winalski
2018-12-31 0:00 ` Donald ODona
2018-12-31 17:51 ` Paul Winalski
-- strict thread matches above, loose matches on Subject: below --
2018-12-31 3:22 Rudi Blom
2018-12-31 2:28 Doug McIlroy
2018-12-31 3:34 ` Will Senn
2018-12-31 6:52 ` ron
2018-12-30 19:07 Norman Wilson
2018-12-30 19:24 ` Paul Winalski
2018-12-31 6:57 ` arnold
2019-01-02 13:54 ` Tony Finch
2018-12-29 14:13 Noel Chiappa
2018-12-29 0:25 Will Senn
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=CANCZdfpMpOzLD_iiuoG6gyNKAPM7wGVm7_yxoW0KVQKvQjbLYQ@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=clemc@ccc.com \
--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).