Sorry for my English.
Le jeu 24/06/2004 à 20:40, Alexandre Oliva a écrit :
On Jun 24, 2004, Jeremy Katz <katzj(a)redhat.com> wrote:
> Alexandre was suggesting in the version or release, not the name or even
> just in the uname output and not as part of the name.
Right. Not part of the kernel package name, just part of the version
string.
I am not sure if i understand all the problem.
Here, i have three kernel base on the same kernel source :
2.6.6-1.435 : RH
2.6.6-1.435mat : RH without REGPARAM (bewan driver (binary) don't like this).
2.6.6-1.435matcustom : Custom configuration.
Simple, for each kernel configuration i have a different EXTRAVERSION
(/usr/src/linux/Makefile).
The problem is that kernel.i586 and i686 use the same EXTRAVERSION and
share file names.
Just add a "magic string" (the arch for example) in EXTRAVERSION for
each configuration.
That give :
/boot/config-2.6.6-1.435-i586
/boot/System.map-2.6.6-1.435-i586
/boot/vmlinuz-2.6.6-1.435-i586
/boot/initrd-2.6.6-1.435-i586
/lib/modules/2.6.6-1.435-i586/*
No conflict.
With this rule, at least kernel developers (freshrpms, etc) can add a
kernel with "rpm -i --nodeps".
/lib/modules/`uname -r`/build should be in a -devel package. This save
disk space.
If Fedora continue to ship kernel-source, add EXTRAVERSION in the
directory name. Example :
rename /usr/src/linux-2.6.6-1.435 to /usr/src/linux-2.6.6-1.435custom .
/lib/modules/2.6.6-1.435custom/build should point to
/usr/src/linux-2.6.6-1.435custom and not to /usr/src/linux-2.6.6-1.435 .
This is less confusing.
> I still think that encoding the arch somehow that's visible
to uname
> is kind of ugly
But it actually solves another problem. How do you tell otherwise
which kernel arch you've booted into?
--
Alexandre Oliva
http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva(a){redhat.com, gcc.gnu.org}
Free Software Evangelist oliva(a){lsd.ic.unicamp.br, gnu.org}