public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: <linux-kernel@vger.kernel.org>
Cc: sam@ravnborg.org
Subject: KBUILD tries to make initramfs contents :-)
Date: Tue, 27 Jun 2006 15:06:20 +0200	[thread overview]
Message-ID: <m3wtb27noz.fsf@defiant.localdomain> (raw)

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?
-- 
Krzysztof Halasa

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27 13:06 Krzysztof Halasa [this message]
2006-06-27 17:50 ` KBUILD tries to make initramfs contents :-) Sam Ravnborg
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=m3wtb27noz.fsf@defiant.localdomain \
    --to=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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