From: Pierfrancesco Caci <ik5pvx@penny.ik5pvx.ampr.org>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.1 segfault when doing "ls /dev/"
Date: 04 Feb 2001 17:28:03 +0100 [thread overview]
Message-ID: <87g0huv2ek.fsf@penny.ik5pvx.ampr.org> (raw)
In-Reply-To: <87u26avkfp.fsf@penny.ik5pvx.ampr.org> <3A7D5CFB.1C21ECD2@wanadoo.fr> <87lmrmv984.fsf@penny.ik5pvx.ampr.org> <3A7D7BCE.37F3DDF@wanadoo.fr>
In-Reply-To: <3A7D7BCE.37F3DDF@wanadoo.fr>
:-> "Pierre" == Pierre Rousselet <pierre.rousselet@wanadoo.fr> writes:
> /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 ...
Yes I know this. Actually, booting with "devfs=nomount s" is the only
way to update the boot record with lilo and my existing lilo.conf.
If I boot with devfs=nomount, I *can* ls /dev, without segfaulting.
I don't want to access or use any device in /dev, I just want to stat
/dev and see what's inside. There's something wrong with (I suspect)
devfsd and the way it populates /dev with symlinks, whick make /dev
un-listable but still usable, somewhat.
> i was thinking the trouble may come from some programme launched by
> your boot scripts before devfsd is running.
I have no idea. Any other debian users reporting this ?
> is your version of fileutils > 4.0.28 (ls --version) ?
root@penny:/usr/src/linux # ls --version
ls (fileutils) 4.0.37
Pf
--
-------------------------------------------------------------------------------
Pierfrancesco Caci | ik5pvx | mailto:p.caci@tin.it - http://gusp.dyndns.org
Firenze - Italia | Office for the Complication of Otherwise Simple Affairs
Linux penny 2.4.1 #1 Sat Feb 3 20:43:54 CET 2001 i686 unknown
-
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/
next prev parent reply other threads:[~2001-02-04 16:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-04 9:58 Pierfrancesco Caci
2001-02-04 13:45 ` Pierre Rousselet
2001-02-04 14:00 ` Pierfrancesco Caci
2001-02-04 15:57 ` Pierre Rousselet
2001-02-04 16:28 ` Pierfrancesco Caci [this message]
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=87g0huv2ek.fsf@penny.ik5pvx.ampr.org \
--to=ik5pvx@penny.ik5pvx.ampr.org \
--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
all inboxes | Powered by JetHome®