linux 2.6.16.38 w/ vs2.0.3-rc1

[linux-2.6.git] / arch / um / drivers / stderr_console.c

diff --git a/arch/um/drivers/stderr_console.c b/arch/um/drivers/stderr_console.c
index 6d2cf32..429ae8e 100644 (file)
--- a/arch/um/drivers/stderr_console.c
+++ b/arch/um/drivers/stderr_console.c
@@ -8,7 +8,10 @@
 
 /*
  * Don't register by default -- as this registeres very early in the
- * boot process it becomes the default console.
+ * boot process it becomes the default console.  And as this isn't a
+ * real tty driver init isn't able to open /dev/console then.
+ *
+ * In most cases this isn't what you want ...
  */
 static int use_stderr_console = 0;
 
@@ -40,20 +43,3 @@ static int stderr_setup(char *str)
        return 1;
 }
 __setup("stderr=", stderr_setup);
-
-/* The previous behavior of not unregistering led to /dev/console being
- * impossible to open.  My FC5 filesystem started having init die, and the
- * system panicing because of this.  Unregistering causes the real
- * console to become the default console, and /dev/console can then be
- * opened.  Making this an initcall makes this happen late enough that
- * there is no added value in dumping everything to stderr, and the
- * normal console is good enough to show you all available output.
- */
-static int __init unregister_stderr(void)
-{
-       unregister_console(&stderr_console);
-
-       return 0;
-}
-
-__initcall(unregister_stderr);