Am 14.10.2007 00:11 schrieb Tilman Schmidt:
quoted text
> CONFIG_LOCALVERSION=3D"-testing"
[...]
quoted text
> has worked fine for all of 2.6.23{-rc?{,-mm?},}. For 2.6.23-mm1
> [there is] "make modules_install" installing the
> modules into /lib/modules/2.6.23-mm1 instead of
> /lib/modules/2.6.23-mm1-testing, and "make install" passing
> "2.6.23-mm1" without the "-testing" suffix to the install.sh
> script, but mkinitrd [...] looks for modules in
> /lib/modules/2.6.23-mm1-testing, so initrd creation fails.

I have investigated a bit more, and stumbled on this:

ts@xenon:~/kernel/linux-2.6.23-mm1-work> make include/config/kernel.relea=
se
ts@xenon:~/kernel/linux-2.6.23-mm1-work> cat include/config/kernel.releas=
e
2.6.23-mm1-testing
ts@xenon:~/kernel/linux-2.6.23-mm1-work> make
  Using ARCH=3Di386 CROSS_COMPILE=3D
  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
[...]
Kernel: arch/i386/boot/bzImage is ready  (#1)
  Building modules, stage 2.
  MODPOST 1085 modules
ts@xenon:~/kernel/linux-2.6.23-mm1-work> cat include/config/kernel.releas=
e
2.6.23-mm1
ts@xenon:~/kernel/linux-2.6.23-mm1-work>

Hmmm. "Curiouser and curiouser", said Alice.

So the content of the file include/config/kernel.release generated
by "make" varies depending on whether I ask "make" to create just
that file, or an entire kernel!? That runs against everything I
ever learned about "make"!

My ability to comprehend the inner workings of Kbuild ends here.
I'll just skip this -mm release and wait for 2.6.24-rc1, hoping
it won't have the same problem.

--=20
Tilman Schmidt                          E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Unge=F6ffnet mindestens haltbar bis: (siehe R=FCckseite)