linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: yaboot 0.2
Date: Thu, 25 Nov 1999 16:35:27 +0100	[thread overview]
Message-ID: <19991125163527.021520@mailhost.mipsys.com> (raw)


I've posted version 0.2 of yaboot, it adds network booting (the config
file, the kernel and the ramdisk can be retreived via TFTP, and with the
appropriate bootp server settings, the machine will completely network
boot when booting with the "N" key).

still to do:

 - fix and merge the head.S MMU patch in the kernel (yaboot will require
this patch)
 - include Stephen Edie ISO filesystem and test with CD-ROMs
 - graphical UI
 - merge with quik (hum... can this simply replace quik ? I would have to
add code to handle broken OF claim)
 - add a README file and example config file, write man pages, etc...


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

                 reply	other threads:[~1999-11-25 15:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=19991125163527.021520@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).