On Thu, Dec 22, 2011 at 02:47, Greg KH <gregkh@xxxxxxx> wrote: > On Wed, Dec 21, 2011 at 05:32:36PM -0800, Tim Bird wrote: >> On 12/21/2011 04:51 PM, Greg KH wrote: >> > On Wed, Dec 21, 2011 at 04:36:21PM -0800, Tim Bird wrote: >> >> On 12/21/2011 03:19 PM, Greg KH wrote: >> >> > Huh, I'm not talking about syslogd, I'm talking about the syslog(2) >> > syscall we have. >> >> OK - switching gears. Since the kernel log buffer isn't normally >> used to store use-space messages, I thought you were referring >> to syslog(3) and the associated (logger(1) and syslogd(8)). > > The kernel log buffer has been storing userspace messages for a while > now, look at your boot log on the latest Fedora and openSUSE releases > (or any other distro using systemd for booting). Right, and the kernel's printk buffer support numbered facilities, like the syslog protocol defines, just fine. Stuff injected into the kernel from userspace can easily distinguished from kernel generated messages when pulled out by userspace. We use that currently to do early boot logging, when no syslog is running: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=9d90c8d9cde929cbc575098e825d7c29d9f45054 Kay -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
