On Saturday 10 February 2007 10:44, [EMAIL PROTECTED] wrote: > From: Jeff Dike <[EMAIL PROTECTED]> > > The startup code panics a lot if anything goes wrong early on. This is > wrong for several reasons, like the kernel isn't running, so you can't > really be calling into it yet, but the harm comes from useful error > messages being trapped in the printk ring where no one will ever see them. > > This patch changes these panics to perror and printf in wrappers which also > exit. Normal, informational, prints are also wrapped so that > fflush(stdout) is called after each one. This is so the output appears in > the correct sequence in the event of an error.
libc's printf has an enormous stack usage, so that my_printf is used for direct output instead of printf; if this is ok because it's bootup code, then *fatal* should be marked as "bootup code only"; otherwise we may reuse vsprintf() and write() or fputs(); this should match what happens in my_printf, to avoid any unlikely problem with libc's buffering. -- Inform me of my mistakes, so I can add them to my list! Paolo Giarrusso, aka Blaisorblade http://www.user-mode-linux.org/~blaisorblade Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
