Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: klibc and logging | Date | 13 Aug 2002 10:41:03 -0700 |
| |
Followup to: <ajaka7$qb6$1@ncc1701.cistron.net> By author: "Miquel van Smoorenburg" <miquels@cistron.nl> In newsgroup: linux.dev.kernel > > In article <3D58B14A.5080500@zytor.com>, > H. Peter Anvin <hpa@zytor.com> wrote: > >However, I'm wondering what to do about logging. Kernel log messages > >get stored away until klogd gets started, but early userspace may need > >some way to log messages -- and syslog is obviously not running. The > >easiest way to do this would probably be to be able to write to > >/proc/kmsg (which probably really should be /dev/kmsg) and push messages > >onto the kernel's message queue; but we could also have a dedicated > >location in the initramfs for writing logs, and do it all in userspace. > > /dev/shm/log/ ? >
Requires too much to work before it's can be made available.
Andrew Morton sent me a proposed patch last night which adds a klogctl (a.k.a. sys_syslog) which does a printk() from userspace. It was less than 10 lines; i.e. probably worth it. I have hooked this up to syslog(3) in klibc, although the code is not checked in yet.
-hpa -- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |