Dne 02.05.2010 (ned) ob 11:58 +0200 je Marco Stornelli zapisal(a): > 01/05/2010 20:48, Samo Pogacnik wrote: > > Dne 01.05.2010 (sob) ob 12:04 +0100 je Alan Cox zapisal(a): > >>> while i was searching for effective logging of complete console output > >>> produced by the kernel and user phase of the boot process, it turned out > >>> that only kernel messages imho get systematically cached and stored into > >>> log files (if needed). All userspace processes are on their own to use > >>> syslog, which is fine, but there are also many console messages > >>> reporting the boot status via init scripts, .... I came across the > >>> bootlogd daemo, which handles the job of redirecting console output into > >>> a log file, but i find it problematic to use especialy, when using > >>> initial ram disk image. > >> > >> So you want to patch the kernel because you can't work out how to do this > >> in userspace ? The distributions seem to have no problem doing this in > >> user space that I can see. It doesn't seem to be a hard user space > >> problem, and there are a ton of things you want to do with this sort of > >> stuff (like network logging) that you can't do in kernel space. > > > > The distros have no problem logging complete console output into log > > files or over the network, because they simply do not do it at least for > > the initrd part of the boot process (i'd be glad, if i'm wrong). > > Mmm...It's an interesting problem. I see in my distro (openSuse) a > script called boot.klog that it seems to perform that (even initrd > part). In the file boot.msg I can see the initial prints of the kernel > and user space scripts. > Thanks for the info. Is this boot.klog script from the initrd image or from the real rootfs? As you can see, i am still suspicious about the initrd part user console messages:) Samo -- 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
