From: Wiktor Wodecki <wodecki@gmx.de>
To: rgooch@atnf.csiro.au
Cc: linux-kernel@vger.kernel.org
Subject: 2.6.0-test1 devfs question
Date: Fri, 25 Jul 2003 13:08:31 +0200 [thread overview]
Message-ID: <20030725110830.GA666@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
Hello,
I'm currently running at 2.6.0-test1-mm2-O8 and I wanted to give devfs a
shot. I recompiled the kernel with the following settings:
CONFIG_DEVFS_FS=y
CONFIG_DEVFS_MOUNT=y
# CONFIG_DEVFS_DEBUG is not set
As I read through the documentation (btw, devfs=nomount is mentioned in
configure help but not in Documentation/filesystems/devfs/boot-options)
I got the understanding that this shouldn't make any difference to the
system right? After booting with this kernel there were lots of proper
devfs devices in my dmesg (host0/ide0... scsi0/...) however, the system
didn't came up (couldn't mount rootfs). It didn't even work when I
enabled CONFIG_DEVFS_MOUNT.
I'm not sure whether this is a bug in mount/nomount of devfs or if it's
somewhere my fault/setup (root on raid1, various lvm2 devices on raid1/0
devices)
Any help would be greatly appreciated.
--
Regards,
Wiktor Wodecki
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-07-25 10:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 11:08 Wiktor Wodecki [this message]
2003-07-25 11:18 ` 2.6.0-test1 devfs question Wiktor Wodecki
2003-07-26 11:12 ` Daniele Venzano
2003-07-26 18:25 ` Andrew Morton
2003-07-27 11:17 ` Alan Cox
2003-07-25 18:53 Balram Adlakha
2003-07-26 10:45 ` Wiktor Wodecki
[not found] ` <20030726175214.GA2535@localhost.localdomain>
[not found] ` <20030726183750.GB789@gmx.de>
[not found] ` <20030726201919.GA5166@localhost.localdomain>
2003-07-26 20:35 ` Wiktor Wodecki
2003-07-26 19:51 Andrey Borzenkov
2003-07-26 20:50 ` Andrew Morton
2003-07-26 22:30 ` Andrey Borzenkov
2003-07-27 8:58 ` Daniele Venzano
2003-07-28 7:13 "Andrey Borzenkov"
2003-07-28 7:22 ` Andrew Morton
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=20030725110830.GA666@gmx.de \
--to=wodecki@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rgooch@atnf.csiro.au \
/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;
as well as URLs for NNTP newsgroup(s).