mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: KBUILD tries to make initramfs contents :-)
Date: Tue, 27 Jun 2006 19:50:32 +0200	[thread overview]
Message-ID: <20060627175032.GB26435@mars.ravnborg.org> (raw)
In-Reply-To: <m3wtb27noz.fsf@defiant.localdomain>

On Tue, Jun 27, 2006 at 03:06:20PM +0200, Krzysztof Halasa wrote:
> Hi,
> 
> I'm a bit surprised :-)
> 
> I'm using a file list for initramfs generation. It's something like:
> 
> file /sbin/udev /usr/local/i386/build/udev/udev 0555 0 0
> file /sbin/udevd /usr/local/i386/build/udev/udevd 0555 0 0
> ...
> 
> /usr/local/i386/build/udev directory contains full udev sources, not
> just the executables.
> 
> Now "make linux" wants to rebuild udev executables, using kernel
> build rules :-)
> 
> All details are of course available on request if needed.
> 
> This is 2.6.17, I haven't checked it but I think the change to
> usr/Makefile which causes this is:
> 
> commit d39a206bc35d46a3b2eb98cd4f34e340d5e56a50
> Author: Sam Ravnborg <sam@mars.ravnborg.org>
> Date:   Tue Apr 11 13:24:32 2006 +0200
> 
>     kbuild: rebuild initramfs if content of initramfs changes
>     
>     initramfs.cpio.gz being build in usr/ and included in the
>     kernel was not rebuild when the included files changed.
>     
>     To fix this the following was done:
>     - let gen_initramfs.sh generate a list of files and directories included
>       in the initramfs
>     - gen_initramfs generate the gzipped cpio archive so we could simplify
>       the kbuild file (Makefile)
>     - utilising the kbuild infrastructure so when uid/gid root mapping changes
>       the initramfs will be rebuild
>     
>     With this change we have a much more robust initramfs generation.
> 
> 
> Should it stay this way or is it a bug?
Oh Crap. It's a bug. The intent it to rebuild initramfs when content of
the initramfs changes.
But not to rebuild content of initramfs of course.

No solution right now - will take a look during the weekend.

	Sam

  reply	other threads:[~2006-06-27 17:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 13:06 Krzysztof Halasa
2006-06-27 17:50 ` Sam Ravnborg [this message]
2006-06-27 17:58   ` H. Peter Anvin

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=20060627175032.GB26435@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®