From: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
To: Hans-Christian Armingeon <linux.johnny@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at slab.c:815!
Date: Wed, 16 Jan 2002 20:40:07 +0100 [thread overview]
Message-ID: <3C45D717.30600@wanadoo.fr> (raw)
In-Reply-To: <16Qvbw-0AB5F2C@fmrl02.sul.t-online.com>
Hans-Christian Armingeon wrote:
> VFS: mounted root (ext3 filesystem) readonly
> devfs: devfs_do_symlink(root): could not append to parent, err: -17
> change_root: old root has d_count=5
it's not a bug, it is a faq
http://www.atnf.csiro.au/~rgooch/linux/docs/devfs.html#faq-messages
Pierre
--
------------------------------------------------
Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------
next prev parent reply other threads:[~2002-01-16 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 20:21 kernel BUG at slab.c:815! Hans-Christian Armingeon
2002-01-16 19:40 ` Pierre Rousselet [this message]
2002-01-17 14:51 ` Hans-Christian Armingeon
-- strict thread matches above, loose matches on Subject: below --
2002-01-16 20:22 Hans-Christian Armingeon
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=3C45D717.30600@wanadoo.fr \
--to=pierre.rousselet@wanadoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.johnny@gmx.net \
/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