public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Greg KH <greg@kroah.com>
Cc: J?rn Engel <joern@wohnheim.fh-wedel.de>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Console: fall back to /dev/null when no console is availlable
Date: Tue, 5 Oct 2004 22:13:33 +0100	[thread overview]
Message-ID: <20041005221333.L6910@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20041005210659.GA5276@kroah.com>; from greg@kroah.com on Tue, Oct 05, 2004 at 02:06:59PM -0700

On Tue, Oct 05, 2004 at 02:06:59PM -0700, Greg KH wrote:
> On Tue, Oct 05, 2004 at 09:27:12PM +0100, Russell King wrote:
> > On Tue, Oct 05, 2004 at 08:52:14PM +0200, J?rn Engel wrote:
> > > Looks pretty trivial, but opinions on this subject may vary.
> > > Comments?
> > 
> > There's a related problem.  /sbin/hotplug.  I keep seeing odd failures
> > from /sbin/hotplug scripts which go away when I ensure that fd0,1,2 are
> > directed at something real.
> 
> Which scripts cause this problem?

I have no idea.  Somewhere in the depths of the Red Hat networking
scripts.  There's multiple of them calling multiple other programs
and it's impossible to debug what's going on.  All I know is that
IPv6 doesn't get configured if fd0,1,2 are closed, but does if they're
open.

It could be a script, or some other program.  There's no way to tell.

> > It's rather annoying because it currently means that, when my PCMCIA net
> > interface on the firewall comes up, the IPv4 configuration works fine
> > but IPv6 configuration falls dead on its nose without any explaination
> > why.
> > 
> > And, like I say, redirecting fd0,1,2 fixes it.
> 
> Redirecting it in the script itself?  Or in the kernel like this patch?

I'm redirecting them in the /sbin/hotplug script to something sane,
but I think the kernel itself should be directing these three fd's
to somewhere whenever it invokes any user program, even if it is
/dev/null.

I think Alan disagrees with me, but I think the history that these
types of problems _keep_ cropping up over and over is proof enough
that it's necessary for sane userspace.

(Another example which is happening _now_: having /sbin/init die over
 a suspend/resume cycle because you have no system console on your
 embedded device isn't nice.)

-- 
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-05 21:15 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 [this message]
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
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=20041005221333.L6910@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@vger.kernel.org \
    /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