From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] PDP-10 UNIX?
Date: Mon, 18 Sep 2017 10:40:11 -0700 [thread overview]
Message-ID: <20170918174011.GM3272@mcvoy.com> (raw)
In-Reply-To: <CAC20D2O3KDoNSHsarY6HDZfrzdTx1UuMz9QCpJ+4XNmERE-idQ@mail.gmail.com>
On Mon, Sep 18, 2017 at 01:25:41PM -0400, Clem Cole wrote:
> On Mon, Sep 18, 2017 at 12:46 PM, Steve Johnson <scj at yaccman.com> wrote:
>
> >
> >
> > ???...
> > After the first time, there is little to learn, and the tedium of
> > debugging a compiler and OS on a bare machine, when the documentation of
> > the machine was hastily written and often incomplete, was frustrating
> > almost beyond describing.
> >
>
> ???+1??? And the HW does quite work the way it claimed too....
> It's fun ... once :-)
Wussies, I did it twice :) Not really true, I worked a port to the ETA-10
and managed a group that was doing a bringup on a MIPS chip (Cobalt Qube).
I had more of a clue the second time around, actually quit over it.
The details, if you care, were that I was brought in as the director
of software, there was no VP, I reported to the CEO. I was assured
that I would be treated like a founder, yada yada.
OK, some time goes by and the CEO wants a schedule. Be aware that
things were a mess, no backups, no nightly builds, no source control,
engineers were hoarding "their" code on their machines. It was little
disfunctional, but I was straightening all that out, had it pretty
much under control by the time they asked for a schedule.
We were using GCC which hadn't had a ton of MIPS time under its belt,
and Linux, which was in the same state. We could boot a kernel but
it crashed (I think, this was a long time ago).
Anyway, they wanted a fast schedule (don't they always?) and I looked
around and said "6 months". Which was aggressive but I felt it was
doable, the kernel was booting, once you get that stable, userland tends
to fall into place. We were also developing a web interface to the box,
that was the whole point, it was a "web server in a box" with a web UI,
no login for you (well there was but we weren't supposed to use it).
They freaked at the schedule. "The board will never go for that!"
So I called Bill Earl, who has done more bringups on MIPS chips than
anyone, period. At least so far as I knew at the time, still don't
know of anyone who has done more. He asked a bunch thoughtful questions
and said "weeeeell, maybe you could do it in 3 months. If you don't hit
any bugs." I asked "Would you bet your kids college education on it?"
He said "Oh, hell no, I wouldn't bet $20 that you'll make it in 3 months.
You hit one compiler bug, that could blow the whole schedule easy."
So I go back to the CEO and said "6 months". He's all pissed and says
he'll take it to the board. I say I want to be there to make my case.
He says "Nope, you aren't an executive." I handed in my resignation.
Founder my ass.
--lm
next prev parent reply other threads:[~2017-09-18 17:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1031.1505666037.3779.tuhs@minnie.tuhs.org>
2017-09-18 2:34 ` Johnny Billquist
2017-09-18 15:30 ` Arthur Krewat
2017-09-18 16:46 ` Steve Johnson
2017-09-18 17:25 ` Clem Cole
2017-09-18 17:40 ` Larry McVoy [this message]
2017-09-18 20:08 ` Chris Torek
2017-09-20 18:40 Nelson H. F. Beebe
2017-09-24 18:29 ` arnold
-- strict thread matches above, loose matches on Subject: below --
2017-09-18 21:14 Noel Chiappa
2017-09-19 6:46 ` Lars Brinkhoff
2017-09-18 17:24 Nelson H. F. Beebe
2017-09-18 18:10 ` Lars Brinkhoff
2017-09-20 4:55 ` Warner Losh
2017-09-17 14:28 Arthur Krewat
2017-09-17 14:31 ` Warner Losh
2017-09-17 15:01 ` Lars Brinkhoff
2017-09-17 15:22 ` Arthur Krewat
2017-09-18 13:50 ` Clem Cole
2017-09-18 16:42 ` Arthur Krewat
2017-09-18 19:58 ` Lars Brinkhoff
2017-09-18 20:10 ` Clem Cole
2017-09-18 20:22 ` Lars Brinkhoff
2017-09-18 20:43 ` Clem cole
2017-09-19 9:06 ` Mutiny
2017-09-19 9:56 ` Lars Brinkhoff
2017-09-17 16:33 ` Warner Losh
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=20170918174011.GM3272@mcvoy.com \
--to=lm@mcvoy.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).