From: "Brian Macy" <bmacy@sunshinecomputing.com>
To: <linuxppc-dev@lists.linuxppc.org>, <linuxppc-user@lists.linuxppc.org>
Subject: Success!!! Yeah!!!
Date: Mon, 22 Mar 1999 08:35:33 -0800 [thread overview]
Message-ID: <001c01be7482$0565a2f0$020210ac@paso.atasd.com> (raw)
In-Reply-To: 19990321023338.A2592@persephone.ppc.kernel.org
Unfortunately I had to use R4 because I couldn't get preR5 to install after
many tries with all kind of variations. The only problem I had with R4 was
when I went into package selection and click on "base" (the last package) I
got a SEGV 11. I also had a bit of problem getting BootX Extension to
correctly pass the root device as an argument... it ended up as 00:00
several times until I actually booted into MacOS, changed the setting with
the BootX App, and saved the prefs. Shame I couldn't install preR5 on this
spare machine though.
Anyways, I noticed R4 is using kernel 2.1.125 which is nice. It means
modutils and a bunch of other packages are up to date for the 2.2.x series.
Are there any other packages I should update? Anyone try 2.2.3-ac4 yet (I
probably will this week)?
Brian Macy
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-03-22 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-21 9:33 New installer images available Cort Dougan
1999-03-22 16:35 ` Brian Macy [this message]
1999-03-23 10:13 ` 2.2.3-ac4 on 7600 Thomas Capricelli
1999-03-23 6:01 ` Kernel panic on 2.2.3-ac4 PPC Brian Macy
1999-03-23 10:35 ` Thomas Capricelli
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='001c01be7482$0565a2f0$020210ac@paso.atasd.com' \
--to=bmacy@sunshinecomputing.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@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).