> How about a crc-32 of either the kernel or the System.map file stamped
> into both? Actually, a 32 bit random is probably good enough....
>
> You could even put most of the work in user space - read a /proc/kernelid or
> /proc/mapid that just reports the number, then user space (rc files?)
> looks thru the (locally defined) list of possible locations, and writes
> it to /proc/locations/System.map
>
> Yah, it'll miss once in a *very* great while, but not often! Besides,
> this way they stay separate files that won't bloat loaded image or
> disk/diskette size. Of course, if you can't find those files, you're
> in the same shape we are today....
>
> I think the kernelid is a better choice, because you can stamp .config
> files & other stuff the same way, w/ the same number.
Here the good idea. A set of paths where kernel image is likely to be
found and a cdc32 to match the right image. Not foolproof, but near to be!
Ciao,
Riccardo.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu