From: Ethan Benson <erbenson@alaska.net>
To: Steven Hanley <sjh@wibble.net>
Cc: Linux PPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: how to pass kernel command line arguments?
Date: Wed, 8 Nov 2000 03:24:27 -0900 [thread overview]
Message-ID: <20001108032427.Z2367@plato.local.lan> (raw)
In-Reply-To: <20001108214245.A31388@wibble.net>; from sjh@svana.org on Wed, Nov 08, 2000 at 09:42:45PM +1100
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On Wed, Nov 08, 2000 at 09:42:45PM +1100, Steven Hanley wrote:
>
> All
>
> Okay I shall be more specific, how do I pass kernel command line arguments
> (say for example a video=whatever) to the kernel when booting the kernel on
> the hfs floppy disk image that comes with debian potato. Does anyone know?
hexeditor /mnt/floppy/.resource/System
there is a resource in there somewhere that has the kernel arguments,
ive heard its not too hard to find and edit in a hex editor.
unfortunatly miboot really badly needs a text based configuration file...
> I suspect the .rootinfo may have something to do with the bootup for linux,
> though not sure and I dont know where to find docs on this stuff either.
no .rootinfo is a hfs thing, don't mess with it, all you would likely
end up doing is trashing the filesystem.
if you have access to macos and resedit/resourcerer you might find
those simpler to edit the System file. (beware that MacOS may make
the floppy unbootable if you mount it read-write on macos. (ive heard
its more forgiving of floppies then disk partitions though, ymmv as
usual))
--
Ethan Benson
http://www.alaska.net/~erbenson/
[-- Attachment #2: Type: application/pgp-signature, Size: 0 bytes --]
prev parent reply other threads:[~2000-11-08 12:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 10:42 how to pass kernel command line arguments? Steven Hanley
2000-11-08 12:24 ` Ethan Benson [this message]
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=20001108032427.Z2367@plato.local.lan \
--to=erbenson@alaska.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=sjh@wibble.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.