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 10:15:46 -0500 [thread overview]
Message-ID: <1081782948.2234.26.camel@mulgrave> (raw)
In-Reply-To: <20040412150556.GT20209@linuxcare.com>
On Mon, 2004-04-12 at 10:05, Richard Hirst wrote:
> Unbootable, or unbootable on 64 bit h/w?
It seems to be unbootable entirely, but for 32 bit kernels that's random
(sometimes it will, sometimes it won't).
> > Unfortunately, palo is rather poor about checking this limit when
> > installing the image or modifying the command line...
>
> and last time I tried building palo on a sid system to investigate
> these hangs on boot, the result didn't work at all :(
I think just reducing the command line would be the best option. Why's
it so long?
James
next prev parent reply other threads:[~2004-04-12 15:15 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
2004-04-12 14:19 ` James Bottomley
2004-04-12 15:05 ` Richard Hirst
2004-04-12 15:05 ` Richard Hirst
2004-04-12 15:15 ` James Bottomley
2004-04-12 15:15 ` James Bottomley [this message]
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 11:12 ` [parisc-linux] Re: if something is not done, hppa will not have an " 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=1081782948.2234.26.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.