I always want to know WHAT I'm running (or people I'm working with
are running) rather than "guessing" ("do you have the most current
patch" "I think so")
I've been a proponent of capturing .config information SOMEPLACE where
you can look at it at runtime...(it took a while but its there now).
In /proc/patches there would be a series of comments (perhaps including
file, date and time) of various patches you want to monitor.
It would be enabled by something like
in file foo.c:
PATCH_COMMENT("this enables the foo feature");
In membar.c:
PATCH_COMMENT("go to the bar on saturday");
...
PATCH_COMMENT("watch how much you drink");
and in /proc/patches:
foo.c: compiled <date> <time>:this enables the foo feature
membar.c: compiled <date> <time>:go to the bar on saturday
member.c: compiled <date> <time>:watch how much you drink
There would be a Kconfig flag whether or not to enable this (i.e.
production kernels would not need it,
hacked kernels would, it could always be there if you're willing to
increase the footprint).
Instead of looking for aberrant behavior to identify patches, you could easily
see things with cat.
Seems very easy and has high ROI if you need to track patched kernels locally.
marty
-
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]
