From: "Timothy A. Seufert" <tas@mindspring.com>
To: Benjamin Herrenschmidt <bh40@calva.net>,
<linuxppc-dev@lists.linuxppc.org>
Subject: Re: MacOS X and yaboot wars.
Date: Sat, 23 Sep 2000 13:23:08 -0700 [thread overview]
Message-ID: <v04220800b5f2c0d86aa2@[10.0.0.42]> (raw)
In-Reply-To: <19340818034744.27131@192.168.1.10>
At 12:16 PM +0200 9/23/00, Benjamin Herrenschmidt wrote:
>>
>>Interestingly enough, I noticed this tidbit in their BootX script:
>>
>>-------------------------------------------
>>if 0 0 then
>>
>>
>>-------------------------------------------
>>
>>Implying that they may be doing something with ext2 support.
>
>You "tidbit" was empty ;)
It sure didn't look that way when I wrote it in Eudora! And in fact
it made it through to Ethan Benson, who was CC'ed. Maybe the mailing
list software mangled it.
Bizarre.
>They have indeed ext2 support in their "BootX". They have ELF support.
>They have almost everything needed to boot the Linux kernel as well. I
>need to implement the necessary support in the kernel itself to get it
>working.
Cool! Do you know if their "BootX" is under their open source license?
Tim Seufert
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-09-23 20:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <v04220800b5f21601b44d@[10.0.0.42]>
2000-09-23 10:16 ` MacOS X and yaboot wars Benjamin Herrenschmidt
2000-09-23 20:23 ` Timothy A. Seufert [this message]
2000-09-23 20:41 Benjamin Herrenschmidt
[not found] <20000921214002.N30638@plato.local.lan>
2000-09-22 16:04 ` Benjamin Herrenschmidt
2000-09-23 1:54 ` Ethan Benson
[not found] ` <39CFE49F.DB1E05EE@noos.fr>
2000-09-25 22:54 ` Ethan Benson
2000-09-26 8:10 ` Michael Schmitz
2000-09-26 8:48 ` Ethan Benson
2000-09-26 12:12 ` Benjamin Herrenschmidt
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='v04220800b5f2c0d86aa2@[10.0.0.42]' \
--to=tas@mindspring.com \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
/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).