> > In some ways this is a bit risky, because the .config which is used for
> > compiling kernel/configs.c isn't necessarily the same as the .config which was
> > used to build vmlinux.
>
> and that's why a module wasn't allowed.
> It's not worth the risk IMO.
Hi,
I agree with Randy here; this does not make sense. Either you're ok with
a small risk that the config doesn't match the kernel (and you
use /boot/config-<version> as put there by make install and by all
distributions) or you want a 100.00% guarantee and use /proc/config.gz.
Making the later unreliable (even if that is a CHOICE a user of it
cannot find this out, in the config.gz he sees the CONFIG option for
this may say =y even if the actual config has it as module!. So users of
this are now in the cold).
One hack we could do is make an md5sum or similar of the config and
stick that somewhere which is built in and always available (proc or
sysfs or something like that); that can be used to validate any config
basically to be "correct matching". In fact we could even make it
(optionally) part of the VERMAGIC to avoid any kind of mismatch at all.
Greetings,
Arjan van de Ven
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
