From: bame@ldl.fc.hp.com (Paul Bame)
To: Joel Soete <soete.joel@tiscali.be>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] palo_1.5 available
Date: Tue, 18 May 2004 12:29:56 -0600 [thread overview]
Message-ID: <20040518182956.GA15743@ldl.fc.hp.com> (raw)
In-Reply-To: <40A6A4C9.5090201@tiscali.be>
On Sat, May 15, 2004 at 11:16:25PM +0000, Joel Soete wrote:
> Thanks but I would just remember that the original idea was of Bjoern A.
> Zeeb :)
palo 1.6 will have a more accurate comment in the changelot
> workaround) but still lock when with my large finger I typo and:
> Command line for kernel: 'root=/dev/md2 HOME=/ console=ttyS0 TERM=vt102
> palo_kernel=3/vmlinux-2.66-rc3'
> Selected kernel: /vmlinux-2.66-rc3-pa3 from partition 3
> ERROR: open /vmlinux-2.66-rc3-pa3 from partition 3 failed
Thanks for spotting those cases I missed. They'll be caught in 1.6
-P
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
parent reply other threads:[~2004-05-18 18:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <40A6A4C9.5090201@tiscali.be>]
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=20040518182956.GA15743@ldl.fc.hp.com \
--to=bame@ldl.fc.hp.com \
--cc=parisc-linux@parisc-linux.org \
--cc=soete.joel@tiscali.be \
/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