public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] kernel make install - why don't we make it easy like on ia32?
Date: Tue, 26 Mar 2002 16:06:00 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905339@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905306@msgid-missing>

On Tue, Mar 19, 2002 at 10:38:02PM -0800, Piet/Pete Delaney wrote:
> I was wondering why the ia32 style of installing boot stuff like 
> /boot/vmlinuz that done in:
> 
> 	arch/i386/boot/Makefile
> and
> 	arch/i386/boot/install.sh
> 
> isn't being done for ia64. 
> 
> I'm thinking of makeing a few tweaks to the ia32 version to copy 
> kernel stuff to /boot and /boot/efi. I've been using a hack on the 
> top level kernel Makefile but it's a hack to do it there. The ia32 
> paradigm seems fine; so why isn't it done for ia64. Even after 
> applying the ia64 patch to linux-2.4.18, a 'make install' in the 
> top level kernel Makefile still breaks.
> 
> What gives?

Note that on Debian ia64 the efi partition is not normally mounted.  The
approach we took was that kernels+initrds are dropped in /boot, and then
we have a script /usr/sbin/elilo, which makes sure the efi partition
contents are up to date.

Richard



      reply	other threads:[~2002-03-26 16:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-20  6:38 [Linux-ia64] kernel make install - why don't we make it easy like on ia32? Piet/Pete Delaney
2002-03-26 16:06 ` Richard Hirst [this message]

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=marc-linux-ia64-105590701905339@msgid-missing \
    --to=rhirst@linuxcare.com \
    --cc=linux-ia64@vger.kernel.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