From: Daniel Jacobowitz <drow@false.org>
To: Andreas Bogk <andreas@andreas.org>
Cc: Benjamin Herrenschmidt <bh40@calva.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: New booter
Date: Mon, 13 Sep 1999 14:12:30 -0400 [thread overview]
Message-ID: <19990913141229.A30982@them.org> (raw)
In-Reply-To: <m3aeqqoai5.fsf@soma.andreas.org>; from Andreas Bogk on Mon, Sep 13, 1999 at 07:51:46PM +0000
On Mon, Sep 13, 1999 at 07:51:46PM +0000, Andreas Bogk wrote:
>
> Benjamin Herrenschmidt <bh40@calva.net> writes:
>
> > I forgot to mention that the kernel args can be changed by editing the
> > CMDL resource in the System file with resedit. Don't forget the trailing
> > 0, it's a C string !
>
> What's the point of a boot application that works without MacOS when
> yu need MacOS to modify the kernel args?
You don't. You can hack them with a hex editor if you prefer. Are
there decent tools for dealing with hfs resource forks from linux? Not
that I know of but there is nothing stopping someone from writing one.
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-13 18:12 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19990913192231.002595>
1999-09-13 17:24 ` New booter Benjamin Herrenschmidt
1999-09-13 19:51 ` Andreas Bogk
1999-09-13 18:12 ` Daniel Jacobowitz [this message]
1999-09-14 5:22 ` resource forks (Re: New booter) Ryan Nielsen
[not found] <199909170500.AAA08016@lists.linuxppc.org>
1999-09-17 16:07 ` New booter Derek Homeier
1999-09-18 12:58 ` Benjamin Herrenschmidt
[not found] <v04011701b404e6cd4493@[199.174.193.101]>
[not found] ` <v04210105b404ed46f043@[192.168.0.1]>
1999-09-15 9:39 ` Benjamin Herrenschmidt
1999-09-15 9:58 ` Ethan Benson
1999-09-15 17:53 ` Kevyn Shortell
1999-09-15 18:03 ` David A. Gatwood
1999-09-15 22:40 ` Ethan Benson
1999-09-15 22:56 ` Tom Rini
1999-09-15 23:03 ` Dan Burcaw
1999-09-15 22:37 ` Ethan Benson
1999-09-15 23:02 ` Peter Bierman
1999-09-16 3:18 ` Ethan Benson
1999-09-16 3:37 ` David D. Kilzer
1999-09-15 23:10 ` Wolfgang Denk
1999-09-16 8:16 ` Geert Uytterhoeven
1999-09-16 8:38 ` Ethan Benson
1999-09-16 10:47 ` Benjamin Herrenschmidt
1999-09-16 17:01 ` David A. Gatwood
1999-09-16 18:48 ` Michel Lanners
1999-09-15 23:15 ` erik cameron
1999-09-16 3:50 ` Ethan Benson
1999-09-16 4:21 ` Dan Burcaw
1999-09-15 17:22 ` David A. Gatwood
1999-09-15 22:41 ` Ethan Benson
1999-09-15 17:39 ` Peter Bierman
1999-09-15 22:27 ` Ethan Benson
1999-09-15 22:47 ` David N. Welton
1999-09-15 23:01 ` Dan Burcaw
1999-09-15 22:48 ` Peter Bierman
1999-09-15 23:19 ` Ethan Benson
1999-09-15 23:48 ` Tom Rini
1999-09-16 0:23 ` David A. Gatwood
1999-09-16 4:02 ` Sean
1999-09-16 5:42 ` David A. Gatwood
1999-09-16 3:59 ` Ethan Benson
1999-09-14 9:37 Ethan Benson
-- strict thread matches above, loose matches on Subject: below --
1999-09-14 9:18 Benjamin Herrenschmidt
1999-09-14 9:28 ` Ethan Benson
1999-09-14 9:10 Benjamin Herrenschmidt
1999-09-13 20:37 Kevin Puetz
1999-09-13 22:08 ` Ethan Benson
1999-09-13 17:22 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=19990913141229.A30982@them.org \
--to=drow@false.org \
--cc=andreas@andreas.org \
--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).