-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 [EMAIL PROTECTED] wrote: | Is this a problem, or simply a name change? The filename says i686 | and I have 'CHOST="i686-pc-linux-gnu"' in /etc/make.conf, but the kernel | ends up as /usr/src/linux/arch/x86/boot/bzImage | | I noticed this when I tried running a couple of scripts that I use to | organize my production and experimental kernels, so that lilo finds | them. No problem changing the scripts to copy from a different | directory, but inquiring minds want to know.
Hi, This happens with x86-based architectures, I believe. I use an x86_64 profile, but the bzImage ends up in (from the linux directory) 'arch/x86/boot'. The 'arch/x86_64/boot/bzImage' is just a symlink to that. It is probably because most of the base kernel source for any x86 based processor is the same. I wouldn't worry about it, unless your system identifies the kernel as an i386 kernel. Regards, Chris -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJIZEwuAAoJEIAhA8M9p9DAaBEQAMWoUbKqIMAGlMHoCZ6j+qg6 iz8yHD15Uvkym2+IQUMqNSH9Fb5USwQJkhMtO7OxLhHEUlTNvHofRqmL3LG8YWVj tKYDqZ4D9Qv4w9kwxUcqvNq8l4+mWcVE4yVAM9GczX6kgIBVcLuA0YsVaEuolQhr dmoGYY5J2JwtWWUh0kVx7I/ITKea15JR7BQ77GLf6F8SOPGwt39wzBifrEM/LFmW KJHiVYxWvlaFNqybxEC5B9pJFAwXcOZ2DrAEr7IEo33SolrojYifh1Y2QV/0cbet XRdFflo3dWZQIn4iH5x30CTBspbBxz9nloEhQC3dunjFM4rd4sFqxdqsXDdhHa/m yo6AZ9LpLoTfEsMyS4GcHWI+5WFUjilxnnqJ5cdMwH2V3ox63xc/qNDRkGzgWeXt 8rNcRLkcDUiPs1yncwtCc2EI38ernDjUj1jqFines/BLm8Pi5g6An7ZRZoZno+kz d4L1U759KxQovuQbOx5H0BuJGnnC04c1V3DZAqwZg6aRxO74HoAAxkxrwnZh+16T RDilHbI6P5IhcoAzapSAjugC43WJKNimcue6Kx1z0Z1WN5Aq6FB2xT4MOFLOKuvD Pjq0AFT62gDUhFwGv0F8sfYIBZ6mHT5+tuarOnNUCgfUF2VGCnVkax2pL6AKvHxx kQ0sGCaRCXccDlXU4qls =6tLC -----END PGP SIGNATURE----- -- gentoo-user@lists.gentoo.org mailing list
