* Sat, 6 Oct 2007 13:08:35 +0200Only boot time selectable? Then write so, please. This approach in GIGO-like, IMHO. Ugliness of (default) boot process messaging itself can and must be solved in the userspace. I don't know if anybody read sub-thread about size reduction by moving static printk string to userspace "message codes" (there were one more person than me, but still). The main problem, is the very narrow perspective of such "kernel" functionality: See? In the userspace one can make anything freely, try do it in the Linux kernel. With userspace {codes, messages} -> messages tool, any console printing frontend is possible. Of course, when kernel OOPes before or in early userspace, where nothing other than photo viva is possible, nobody should care about "Linux's cuteness!" Is it possible to have a macro for this, which will be `do { } while(0)' in case of "NO, thanks" configuration? -- -o--=O`C #oo'L O <___=E M -
| H. Peter Anvin | Re: [RFC 00/15] x86_64: Optimize percpu accesses |
| Linus Torvalds | Linux 2.6.27-rc5 |
| Ingo Molnar | [announce] "kill the Big Kernel Lock (BKL)" tree |
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Ben Hutchings | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH iproute2] Re: HTB accuracy for high speed |
