* 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 -
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| David Brown | Re: Linux 2.6.21-rc2 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
git: | |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | Re: [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [BUG] New Kernel Bugs |
