From: Joe Alonso <jalonso@kaydara.com>
To: linux-mips@fnet.fr, linux@cthulhu.engr.sgi.com, ewt@redhat.com,
linux-mips@vger.rutgers.edu
Subject: Re: Announce: New uploads
Date: Thu, 11 Dec 1997 09:50:39 -0500 [thread overview]
Message-ID: <348FFDBF.EE8@kaydara.com> (raw)
In-Reply-To: 19971210151448.23359@thoma.uni-koblenz.de
Pardon my ignorance, but...
I have a couple of questions;
is there a how-to document that outlines how to load linux on an sgi?
is the Indigo Elan (r4000) supported?
I'm not sure how to initialize a loading of linux on the sgi.
Here's what I've assumed:
- bring over the src's to the sgi
- compile a basic system (under irix)
- copy over the original irix kernel with the new linux kernel
- re-boot
The begging questions:
The FS are not compatible, therefore a new mkfs has to be done on the
(root) partitions.
This just doesn't "sound" right to me.
What am I overlooking?
ja
Ralf Baechle wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
>
> Hi all,
>
> ok, here are the toys I promised to upload to ftp.linux.sgi.com:
>
> - tons of srpms some of which have been modified compared to RedHat's
> original versions for the ``Mustang'' release and big endian binaries.
> - tarballs of libc binaries.
> - srpms and both big and little endian binaries of an updated binutils
> package.
> - a tarball with big endian binaries of XFree 3.3.1.
> - kernel binaries for the Indy and RM200. The RM200 kernel has the support
> for a couple of other little endian machines in it but I didn't test.
>
> All in all this is around 350mb.
>
> Have fun leeching,
>
> Ralf
>
next parent reply other threads:[~1997-12-11 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19971210151448.23359@thoma.uni-koblenz.de>
1997-12-11 14:50 ` Joe Alonso [this message]
1997-12-11 18:21 ` Announce: New uploads Ariel Faigon
1997-12-11 18:21 ` Ariel Faigon
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=348FFDBF.EE8@kaydara.com \
--to=jalonso@kaydara.com \
--cc=ewt@redhat.com \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@vger.rutgers.edu \
--cc=linux@cthulhu.engr.sgi.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