- Subject: Re: [PATCH v3 21/22] netoops: Add user-programmable boot_id
- From: Matt Mackall <mpm@xxxxxxxxxxx>
- Date: Tue, 14 Dec 2010 15:42:37 -0600
- Cc: simon.kagstrom@xxxxxxxxxxxxxx, davem@xxxxxxxxxxxxx, nhorman@xxxxxxxxxxxxx, adurbin@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, chavey@xxxxxxxxxx, Greg KH <greg@xxxxxxxxx>, netdev@xxxxxxxxxxxxxxx, Américo Wang <xiyou.wangcong@xxxxxxxxx>, akpm@xxxxxxxxxxxxxxxxxxxx, linux-api@xxxxxxxxxxxxxxx
- In-reply-to: <20101214213048.17022.58746.stgit@xxxxxxxxxxxxxxxxxxxxxxxx>
- References: <20101214212846.17022.64836.stgit@xxxxxxxxxxxxxxxxxxxxxxxx> <20101214213048.17022.58746.stgit@xxxxxxxxxxxxxxxxxxxxxxxx>
On Tue, 2010-12-14 at 13:30 -0800, Mike Waychison wrote:
> 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.
--
Mathematics is the supreme nostalgia of our time.
--
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Home]
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Free Online Dating]
[Linux Kernel]
[Linux SCSI]
[XFree86]