From: <ron@ronnatalie.com>
To: "'Will Senn'" <will.senn@gmail.com>,
"'Doug McIlroy'" <doug@cs.dartmouth.edu>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Deleted lib1 and lib2 in v6, recoverable?
Date: Mon, 31 Dec 2018 01:52:55 -0500 [thread overview]
Message-ID: <08c301d4a0d5$770791d0$6516b570$@ronnatalie.com> (raw)
In-Reply-To: <E0AD2E17-E86D-4B21-AD89-698900DAE541@gmail.com>
Not in v6. Showed up in V7.
> -----Original Message-----
> From: TUHS <tuhs-bounces@minnie.tuhs.org> On Behalf Of Will Senn
> Sent: Sunday, December 30, 2018 10:35 PM
> To: Doug McIlroy <doug@cs.dartmouth.edu>
> Cc: tuhs@tuhs.org
> Subject: Re: [TUHS] Deleted lib1 and lib2 in v6, recoverable?
>
>
>
> On Dec 30, 2018, at 8:28 PM, Doug McIlroy <doug@cs.dartmouth.edu>
> wrote:
>
> >> But wasn't it tsort that did the heavy lifting to get things in order?
> >
> > An amusing notion. Having written tsort, I can assure you it couldn't
> > lift anything heavy--it used the most naive quadratic algorithm. But
> > it was good enough for libc.
> >
> > Doug
>
> I don’t see tsort anywhere on the system, is it v7 or an addon to v6?
>
> Thanks,
>
> Will
next prev parent reply other threads:[~2018-12-31 6:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 2:28 Doug McIlroy
2018-12-31 3:34 ` Will Senn
2018-12-31 6:52 ` ron [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-31 3:22 Rudi Blom
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 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
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
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='08c301d4a0d5$770791d0$6516b570$@ronnatalie.com' \
--to=ron@ronnatalie.com \
--cc=doug@cs.dartmouth.edu \
--cc=tuhs@tuhs.org \
--cc=will.senn@gmail.com \
/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).