On Tue, Dec 14, 2010 at 1:42 PM, Matt Mackall [off-list ref] wrote:

On Tue, 2010-12-14 at 13:30 -0800, Mike Waychison wrote:

quoted

Add support for letting userland define a 32bit boot id.  This is useful
for users to be able to correlate netoops reports to specific boot
instances offline.

This sounds a lot like the pre-existing /proc/sys/kernel/random/boot_id
that's used by kerneloops.org.

Could be.  I'm looking at it now... There is no documentation for this
boot_id field?

Reusing this guy would work, except that it doesn't appear to allow
arbitrary values to be set.  We need to inject our boot sequence
number (which is figured out in userland) in the packet somehow as we
need to correlate it to our other monitoring systems.

I agree that having the uuid included in the netoops messages would be
very useful.

netoops is probably the wrong place to have a system-wide boot
sequence ID set in retrospect.  For our purposes, I can have it
encoded into the 'user_blob' portion of the packet if folks don't
think the kernel should have any notion of boot sequence number
programmable by userland.