From: Ethan Benson <erbenson@alaska.net>
To: Debian-powerpc <debian-powerpc@lists.debian.org>,
Linux/PPC-devel <linuxppc-dev@lists.linuxppc.org>
Subject: Last call for testing: yaboot-1.3.4pre3
Date: Fri, 12 Oct 2001 05:51:50 -0800 [thread overview]
Message-ID: <20011012055150.B10713@plato.local.lan> (raw)
I am going to take the resounding silence as an indication that there
are no problems with yaboot 1.3.4pre.
I plan to release 1.3.4 this weekend unless someone speaks up and
points out some problem.
pre3 is up now, one test i would like to see is netbooting by holding
down the `n' key on bootup of a PCI G4 (not G3), these machines appear
to netboot with dhcp rather then bootp and i want to know if yaboot
will parse the bootpath properly.
On Blue G3s when booting via the `n' key the bootpath ends up being
enet:bootp yaboot has to throw away the bootp part to work, what i
want to know is if dhcp versions of OF use something like enet:dhcp or
equivilent.
Simply booting yaboot via `n key' netboot will answer this question,
if its using something like enet:dhcp yaboot will fail to locate its
config file and print out the device path it tried, just send me that
error message.
http://master.penguinppc.org/projects/yaboot/1.3.4pre/
--
Ethan Benson
http://www.alaska.net/~erbenson/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-10-12 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-12 13:51 Ethan Benson [this message]
2001-10-13 1:23 ` Last call for testing: yaboot-1.3.4pre3 Christoph Ewering
2001-10-13 8:16 ` Ethan Benson
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=20011012055150.B10713@plato.local.lan \
--to=erbenson@alaska.net \
--cc=debian-powerpc@lists.debian.org \
--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 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.