From: Brent Cook <bcook@bpointsys.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: make install on ppc
Date: Sun, 26 Mar 2006 19:56:40 -0600 [thread overview]
Message-ID: <200603261956.40700.bcook@bpointsys.com> (raw)
In-Reply-To: <OF06763F9B.91995CDB-ON4825713E.000850DE-4825713E.000949FE@cn.ibm.com>
On Sunday 26 March 2006 19:42, Jin Qi Huang wrote:
> I also think the 'make install' is very useful, now on ia32, the 'make
> install' provided by the latest kernel linux-2.6.16 not only create
> initrd, copy vmlinuz and System.map to /boot directory, but also update
> grub, ppc32 does not provide this useful feature, maybe it is a pity!
>
Maybe narrow it to define 'make install' for new world/old world Macintoshes,
or IBM machines? I can't see a generic make install being useful for the
wider range of platforms that fall under ppc.
'make install' appears to me to be very platform dependent. Sure, on x86, you
can reasonably assume that the majority of systems have the kernel on a disk
under /boot and the bootloader is grub or lilo. I have 5 ppc machines
currently, and no two use the same bootloader or kernel image. I've seen
u-boot, yaboot, quik, powerboot (Motorola/Force), xmon (XES) and more, and
they all required different post-processing to the kernel image to boot. For
most of these, there is no way to programmatically guess where a particular
kernel image should go to work with the boot loader.
- Brent
next prev parent reply other threads:[~2006-03-27 2:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 14:08 [Fwd: Re: make install on ppc] Hans Fugal
2006-03-26 19:26 ` make install on ppc Hollis Blanchard
2006-03-26 20:43 ` Arnd Bergmann
2006-03-26 21:44 ` Hans Fugal
2006-03-27 1:42 ` Jin Qi Huang
2006-03-27 1:56 ` Brent Cook [this message]
2006-03-28 3:43 ` Hollis Blanchard
2006-03-28 3:59 ` Jin Qi Huang
2006-03-28 19:06 ` Geoff Levand
2006-03-28 20:02 ` Hollis Blanchard
2006-03-28 20:30 ` Geoff Levand
2006-03-28 21:13 ` Paul Mackerras
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=200603261956.40700.bcook@bpointsys.com \
--to=bcook@bpointsys.com \
--cc=linuxppc-dev@ozlabs.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).