From: James Bottomley <James.Bottomley@steeleye.com>
To: Richard Hirst <rhirst@linuxcare.com>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
debian-boot@lists.debian.org, parisc-linux@parisc-linux.org,
debian-hppa@lists.debian.org
Subject: Re: [parisc-linux] Re: if something is not done, hppa will not have an installer for sarge
Date: 12 Apr 2004 09:19:27 -0500 [thread overview]
Message-ID: <1081779569.1804.11.camel@mulgrave> (raw)
In-Reply-To: <20040412111257.GS20209@linuxcare.com>
On Mon, 2004-04-12 at 06:12, Richard Hirst wrote:
> It may be relevant that the ISO had a rather long kernel commandline,
> relative to the 127 char limit that palo claims. I'm never sure
> whether that 127 char limit is before or after palo adds all the
> console and sti related parameters though.
That limit is absolute and may not be overrun. The co-ordinates of the
64 bit kernel lie immediately after the 128 char buffer. Usually the
system is unbootable if you overrun this limit.
Unfortunately, palo is rather poor about checking this limit when
installing the image or modifying the command line...
James
next prev parent reply other threads:[~2004-04-12 14:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040411165459.GB11699@kitenet.net>
[not found] ` <20040411171831.GA15032@mcmartin.ca>
[not found] ` <20040411174629.GA12562@kitenet.net>
2004-04-12 11:12 ` [parisc-linux] Re: if something is not done, hppa will not have an installer for sarge Richard Hirst
2004-04-12 14:19 ` James Bottomley [this message]
2004-04-12 15:05 ` Richard Hirst
2004-04-12 15:05 ` Richard Hirst
2004-04-12 15:15 ` James Bottomley
2004-04-12 17:15 ` Richard Hirst
2004-04-12 18:13 ` Thiemo Seufer
2004-04-12 18:13 ` Thiemo Seufer
2004-04-12 17:15 ` Richard Hirst
2004-04-12 17:18 ` [parisc-linux] Re: if something is not done, hppa will not havean " Andy Walker
2004-04-12 17:18 ` Andy Walker
2004-04-12 15:15 ` [parisc-linux] Re: if something is not done, hppa will not have an " James Bottomley
2004-04-12 14:19 ` James Bottomley
2004-04-12 11:12 ` Richard Hirst
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=1081779569.1804.11.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=debian-boot@lists.debian.org \
--cc=debian-hppa@lists.debian.org \
--cc=kyle@mcmartin.ca \
--cc=parisc-linux@parisc-linux.org \
--cc=rhirst@linuxcare.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 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.