public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
To: Pierfrancesco Caci <p.caci@tin.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.1 segfault when doing "ls /dev/"
Date: Sun, 04 Feb 2001 16:57:02 +0100	[thread overview]
Message-ID: <3A7D7BCE.37F3DDF@wanadoo.fr> (raw)
In-Reply-To: <87u26avkfp.fsf@penny.ik5pvx.ampr.org> <3A7D5CFB.1C21ECD2@wanadoo.fr> <87lmrmv984.fsf@penny.ik5pvx.ampr.org>

Pierfrancesco Caci wrote:

> I can't see how this can affect performance/funtionality of
> devfsd. Can you try to stop the daemon and restart it to see if
> continues to work as before ?

/dev is mounted at boot time by the kernel (CONFIG_DEVFS_MOUNT=y).
The system boots and runs without devfsd. You just can't start any 
process calling for non-existing device under /dev and not created
by devfsd. For instance pppd or mc won't start by lack of pseudo-tty 
esd needs /dev/dsp ...

i was thinking the trouble may come from some programme launched by
your boot scripts before devfsd is running.

is your version of fileutils > 4.0.28 (ls --version) ?

-- 
------------------------------------------------
 Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-04 15:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-04  9:58 2.4.1 segfault when doing "ls /dev/" Pierfrancesco Caci
2001-02-04 13:45 ` Pierre Rousselet
2001-02-04 14:00   ` Pierfrancesco Caci
2001-02-04 15:57     ` Pierre Rousselet [this message]
2001-02-04 16:28       ` Pierfrancesco Caci
2001-02-04 17:35         ` Pierre Rousselet

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=3A7D7BCE.37F3DDF@wanadoo.fr \
    --to=pierre.rousselet@wanadoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.caci@tin.it \
    /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