From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] MIPS Support in Release 4
Date: Mon, 1 Jul 2002 08:55:24 -0400 [thread overview]
Message-ID: <efd7d1b6a3bc3b102408ab655c865ed9@plan9.bell-labs.com> (raw)
> That's too bad. Is there any way to obtain a binary-only kernel? Perhaps
> one from an older release?
The release terms would need to be negotiated, it probably wouldn't run
on your hardware, and since it would be from an ancient version of the
kernel - the only SGI machine we still have is a hulking Challenge - many
binaries wouldn't work properly. ls, for one.
I've spent too much time trying to get SGI to let us spring our kernel loose.
I'm not spending any more.
-rob
next reply other threads:[~2002-07-01 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 12:55 rob pike, esq. [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-28 13:58 rob pike, esq.
2002-07-01 9:45 ` Jim Meier
2002-07-01 9:46 ` Jim Meier
2002-06-28 10:00 Geoff Collyer
2002-06-28 8:52 Jim Meier
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=efd7d1b6a3bc3b102408ab655c865ed9@plan9.bell-labs.com \
--to=rob@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).