From: Ralf Baechle <ralf@Julia.DE>
To: miguel@nuclecu.unam.mx (Miguel de Icaza)
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Linux/SGI
Date: Fri, 7 Mar 1997 22:38:35 +0100 (MET) [thread overview]
Message-ID: <199703072138.WAA16621@kernel.panic.julia.de> (raw)
In-Reply-To: <199703071951.NAA10311@athena.nuclecu.unam.mx> from "Miguel de Icaza" at Mar 7, 97 01:51:32 pm
Hello,
> This is kind of a test message to see if we are (Ralf and I) are on
> the SGI Linux mailing list.
>
> Ralf and I have joined the Linux/SGI project (he will mail his very
> own presentation later). The idea basically is that we will be
> getting a machine each one to finish the Linux on SGI port.
Thanks for the introduction Miguel; I'd like to use the chance to drop
some words about what I'm doing right now on Linux and what the status
of this is.
As you know David left SGI again in the late August. At that time he
had not only completed a good part of the SGI specific stuff but also
made a lot of improofments to the generic MIPS parts of the kernel. At
that time his kernel was based on Linus' 2.0.14.
At the same time I was working mostly independend of him; luckily. My target
machines were at that time the good old Magnum 4000 and it's OEM variant
M700-10 from Olivetti, the Magnum based Acer PICA machine and SNI's RM200.
When Ariel mailed me about working on Linux/SGI my kernel for these
machines was based on Linux 2.1.21.
It's obvious that our kernels have diverged a good bit from each other
and right now I'm working on merging both kernel sources into one single
tree again.
The second most important part of the system is libc. On MIPS we use
the GNU which has the enormous advantage of being far more portable and
cleaner code than the Linux Libc on which most Linux/i386 systems are
based. Disadvantage is that GNU libc was much buggier than Linux Libc.
This has changed a lot and so libc presents itself already quite near
to a release (*) libc but there is still some work to do.
Similar for the other core parts of the system on which David worked but
right now I'm still busy merging the kernel sources; the next step will
be libc.
Ralf
*) famous last words
WARNING: multiple messages have this Message-ID (diff)
From: Ralf Baechle <ralf@Julia.DE>
To: Miguel de Icaza <miguel@nuclecu.unam.mx>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: Linux/SGI
Date: Fri, 7 Mar 1997 22:38:35 +0100 (MET) [thread overview]
Message-ID: <199703072138.WAA16621@kernel.panic.julia.de> (raw)
Message-ID: <19970307213835.4lOE8ARjuS24Uerhz_q87z5JxrWmb8olbCt1Sz6LJDI@z> (raw)
In-Reply-To: <199703071951.NAA10311@athena.nuclecu.unam.mx> from "Miguel de Icaza" at Mar 7, 97 01:51:32 pm
Hello,
> This is kind of a test message to see if we are (Ralf and I) are on
> the SGI Linux mailing list.
>
> Ralf and I have joined the Linux/SGI project (he will mail his very
> own presentation later). The idea basically is that we will be
> getting a machine each one to finish the Linux on SGI port.
Thanks for the introduction Miguel; I'd like to use the chance to drop
some words about what I'm doing right now on Linux and what the status
of this is.
As you know David left SGI again in the late August. At that time he
had not only completed a good part of the SGI specific stuff but also
made a lot of improofments to the generic MIPS parts of the kernel. At
that time his kernel was based on Linus' 2.0.14.
At the same time I was working mostly independend of him; luckily. My target
machines were at that time the good old Magnum 4000 and it's OEM variant
M700-10 from Olivetti, the Magnum based Acer PICA machine and SNI's RM200.
When Ariel mailed me about working on Linux/SGI my kernel for these
machines was based on Linux 2.1.21.
It's obvious that our kernels have diverged a good bit from each other
and right now I'm working on merging both kernel sources into one single
tree again.
The second most important part of the system is libc. On MIPS we use
the GNU which has the enormous advantage of being far more portable and
cleaner code than the Linux Libc on which most Linux/i386 systems are
based. Disadvantage is that GNU libc was much buggier than Linux Libc.
This has changed a lot and so libc presents itself already quite near
to a release (*) libc but there is still some work to do.
Similar for the other core parts of the system on which David worked but
right now I'm still busy merging the kernel sources; the next step will
be libc.
Ralf
*) famous last words
next prev parent reply other threads:[~1997-03-07 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-03-07 19:51 Linux/SGI Miguel de Icaza
1997-03-07 21:38 ` Ralf Baechle [this message]
1997-03-07 21:38 ` Linux/SGI Ralf Baechle
[not found] <340DF260.5D60941F@xtra.co.nz>
1997-09-04 2:53 ` Linux/SGI Ariel Faigon
1997-09-04 2:53 ` Linux/SGI 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=199703072138.WAA16621@kernel.panic.julia.de \
--to=ralf@julia.de \
--cc=linux@cthulhu.engr.sgi.com \
--cc=miguel@nuclecu.unam.mx \
/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