public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Thayne Harbaugh" <tharbaugh@lnxi.com>,
	"Jörn Engel" <joern@wohnheim.fh-wedel.de>,
	"Greg KH" <greg@kroah.com>, "Andrew Morton" <akpm@osdl.org>,
	"Linux Kernel Development" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Console: fall back to /dev/null when no console is availlable
Date: Thu, 7 Oct 2004 10:07:57 +0100	[thread overview]
Message-ID: <20041007100757.A10716@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.GSO.4.61.0410071017020.9319@waterleaf.sonytel.be>; from geert@linux-m68k.org on Thu, Oct 07, 2004 at 10:18:51AM +0200

On Thu, Oct 07, 2004 at 10:18:51AM +0200, Geert Uytterhoeven wrote:
> What about letting the kernel open the console without going through
> /dev/console? Since the kernel knows /dev/console is the device with major 5
> minor 1, why can't it just open (5, 1)? Then we don't need a /dev/console node,
> and things will never break.

Famous last words.  What about the case where you don't have a console
device registered (eg in the case of an embedded device) ?  Currently,
opening /dev/console fails in that circumstance.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-10-07  9:08 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 18:52 [PATCH] Console: fall back to /dev/null when no console is availlable Jörn Engel
2004-10-05 20:27 ` Russell King
2004-10-05 21:06   ` Greg KH
2004-10-05 21:13     ` Russell King
2004-10-06 15:00       ` Alan Cox
2004-10-06 17:41         ` Greg KH
2004-10-06 18:01           ` Jörn Engel
2004-10-06 18:18             ` Greg KH
2004-10-06 19:20               ` Jörn Engel
2004-10-06 18:26             ` Chris Wright
2004-10-06 18:16           ` Andries Brouwer
2004-10-06 19:18           ` Alan Cox
2004-10-06 20:54             ` Greg KH
2004-10-06 20:29               ` Alan Cox
2004-10-06 21:45                 ` Russell King
2004-10-07  5:51                 ` Valdis.Kletnieks
2004-10-08  2:15                   ` Herbert Xu
2004-10-06 20:01           ` Russell King
2004-10-05 22:36   ` Andries Brouwer
2004-10-06  6:43     ` Russell King
2004-10-07 14:41   ` Jan-Benedict Glaw
2004-10-05 21:58 ` Denis Vlasenko
2004-10-06  4:34   ` Willy Tarreau
2004-10-06  8:43     ` Geert Uytterhoeven
2004-10-06 12:15       ` Jörn Engel
2004-10-06 13:07         ` Geert Uytterhoeven
2004-10-06 13:33           ` Jörn Engel
2004-10-06 13:55             ` Geert Uytterhoeven
2004-10-06 14:12               ` Jörn Engel
2004-10-06 14:23                 ` Geert Uytterhoeven
2004-10-06 15:28                   ` Jörn Engel
2004-10-06 15:36                     ` Geert Uytterhoeven
2004-10-06 15:51                       ` Jörn Engel
2004-10-05 23:30 ` Andrew Morton
2004-10-06 12:16   ` Jörn Engel
2004-10-06 17:38 ` Greg KH
2004-10-06 18:04   ` Jörn Engel
2004-10-06 18:19     ` Greg KH
2004-10-06 19:23       ` Jörn Engel
2004-10-06 21:22         ` Thayne Harbaugh
2004-10-07  8:18           ` Geert Uytterhoeven
2004-10-07  9:07             ` Russell King [this message]
2004-10-07  9:46               ` Geert Uytterhoeven
2004-10-06 18:37 ` Gianni Tedesco
2004-10-06 19:08   ` Jörn Engel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041007100757.A10716@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=geert@linux-m68k.org \
    --cc=greg@kroah.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tharbaugh@lnxi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox