From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] OT: critical Intel design flaw
Date: Thu, 4 Jan 2018 12:56:53 -0800 [thread overview]
Message-ID: <699C77DA-7685-413F-BAFD-D7C40E06090E@bitblocks.com> (raw)
In-Reply-To: <CANCZdfqMtaTQRvgEUP7d5HTk3iCibbPYnK5ytT1VxcHDqYq31Q@mail.gmail.com>
> On Jan 4, 2018, at 12:52 PM, Warner Losh <imp at bsdimp.com> wrote:
>
>
>
> On Jan 4, 2018 11:50 AM, "Larry McVoy" <lm at mcvoy.com <mailto:lm at mcvoy.com>> wrote:
> On Thu, Jan 04, 2018 at 10:29:59AM -0800, Bakul Shah wrote:
> > On Thu, 04 Jan 2018 09:17:40 -0800 Larry McVoy <lm at mcvoy.com <mailto:lm at mcvoy.com>> wrote:
> > Larry McVoy writes:
> > >
> > > I dunno what "used in anger" means but it worked. I used it. I know
> > > Joltiz pretty well, he worked for me around this time period. I hired
> > > him just to give him some money, he had gotten sort of screwed by the
> > > in crowd in the BSD/Usenix world, I didn't see that as reasonable.
> >
> > Not part of any in crowd but I am curious. How was Jolitz
> > "screwed by the in crowd in the BSD/Usenix world"?
>
> I'll answer off list, not interested in ruffling feathers.
>
> Probably best... as someone on the other side during that time, I have a different perspective on who got screwed when... and what beds were made and who had to sleep in them...
>
> But I agree rehashing all that now is not beneficial to anybody...
My fault. I had meant to reply to just Larry but forgot to remove cc: to the list.
Apologies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180104/61d65490/attachment.html>
next prev parent reply other threads:[~2018-01-04 20:56 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-03 13:43 Noel Chiappa
2018-01-03 14:26 ` Clem Cole
2018-01-03 17:28 ` Bakul Shah
2018-01-03 17:46 ` ron minnich
2018-01-03 18:28 ` Bakul Shah
2018-01-03 18:27 ` Clem Cole
2018-01-03 18:39 ` Forrest, Jon
2018-01-03 18:50 ` ron minnich
2018-01-03 19:56 ` Paul Winalski
2018-01-03 20:24 ` Bakul Shah
2018-01-03 23:40 ` Theodore Ts'o
2018-01-04 0:51 ` Larry McVoy
2018-01-04 2:13 ` Bakul Shah
2018-01-04 2:26 ` Larry McVoy
2018-01-04 3:31 ` Bakul Shah
2018-01-04 2:09 ` Arthur Krewat
2018-01-04 3:21 ` Dan Cross
2018-01-04 17:42 ` Arthur Krewat
2018-01-04 11:53 ` Harald Arnesen
2018-01-04 14:03 ` Clem Cole
2018-01-04 15:54 ` Larry McVoy
2018-01-04 16:45 ` Theodore Ts'o
2018-01-04 17:10 ` Andy Kosela
2018-01-04 17:17 ` Larry McVoy
2018-01-04 18:29 ` Bakul Shah
2018-01-04 18:50 ` Larry McVoy
2018-01-04 20:52 ` Warner Losh
2018-01-04 20:56 ` Bakul Shah [this message]
2018-01-04 20:56 ` Theodore Ts'o
2018-01-04 21:16 ` Warner Losh
2018-01-04 22:55 ` Andy Kosela
2018-01-05 14:27 ` Clem Cole
2018-01-04 21:17 ` Bakul Shah
2018-01-04 17:20 ` Tom Ivar Helbekkmo
2018-01-04 17:28 ` Warner Losh
2018-01-03 17:07 ` Bakul Shah
-- strict thread matches above, loose matches on Subject: below --
2018-01-03 17:06 Norman Wilson
2018-01-03 7:53 Andy Kosela
2018-01-03 11:57 ` Ron Natalie
2018-01-03 14:22 ` Random832
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=699C77DA-7685-413F-BAFD-D7C40E06090E@bitblocks.com \
--to=bakul@bitblocks.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).