archive mirror
 help / color / mirror / Atom feed
From: Wiktor Wodecki <>
To: Balram Adlakha <>
Subject: Re: 2.6.0-test1 devfs question
Date: Sat, 26 Jul 2003 12:45:06 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20030725185325.GA3944@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2247 bytes --]

On Sat, Jul 26, 2003 at 12:23:25AM +0530, Balram Adlakha wrote:
> >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_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
> >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.
> You need to change your /etc/fstab to reflect the new devfs device names,
> ex: "/dev/discs/disc0/part1" instead of "/dev/hda1". You can also use devfsd (or some alternative) to make synlinks to the older devices and retain permissions etc... Also, without devfsd you cannot expect module autoloading as modules can't be automatically loaded when theres no device requesting them (in this case the device simply doesn't exist until module is loaded)

wait a second, this is a dumb thing to do. I do not want to migrate over
to devfs yet. I wanted to give it a shot and look around a bit. What I
haad in mind was mounting it on /dev2 or similar. Enabling this option
and converting my whole system is not a migration path. That's just
plain luck (might be easy for plain ide/scsi disks, but whatabout
metadevices like lvm and raid?). It is written in the documentation that
devfs comes with most backwards compatibility. I expected there to be
things like /dev/md0 and such for compatibility.
OTOH what's CONFIG_DEVFS_MOUNT for then? If devices get named the other
way round I *have* to mount it anyway, haven't I? I think improvements
must happen here in order to make devfs usable.


Wiktor Wodecki

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-07-26 10:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 18:53 2.6.0-test1 devfs question Balram Adlakha
2003-07-26 10:45 ` Wiktor Wodecki [this message]
     [not found]   ` <20030726175214.GA2535@localhost.localdomain>
     [not found]     ` <>
     [not found]       ` <20030726201919.GA5166@localhost.localdomain>
2003-07-26 20:35         ` Wiktor Wodecki
  -- strict thread matches above, loose matches on Subject: below --
2003-07-28  7:13 "Andrey Borzenkov" 
2003-07-28  7:22 ` Andrew Morton
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-25 11:08 Wiktor Wodecki
2003-07-25 11:18 ` Wiktor Wodecki
2003-07-26 11:12 ` Daniele Venzano
2003-07-26 18:25   ` Andrew Morton
2003-07-27 11:17     ` Alan Cox

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).