From mboxrd@z Thu Jan 1 00:00:00 1970 From: "John L. Fjellstad" Date: Thu, 12 Feb 2004 21:03:32 +0000 Subject: Re: little udev problem - loop devices instead of hda devices! Message-Id: <20040212210332.GA4129@fjellstad.org> MIME-Version: 1 Content-Type: multipart/mixed; boundary="MGYHOYXEY6WxJCY8" List-Id: References: <1076601040.402ba0d05eb01@webmail.fish.co.uk> In-Reply-To: <1076601040.402ba0d05eb01@webmail.fish.co.uk> To: linux-hotplug@vger.kernel.org --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Feb 12, 2004 at 03:50:40PM +0000, fbarton@fish.co.uk wrote: > What should I do to make sure my hda partitions are found at boot time? W= hy are=20 > the loop devices being created instead? Is it safe yet to empty /dev and = just=20 > rely on /udev when things are properly configured (and presumably udev th= en=20 > somehow symlinks from /dev or intercepts calls to /dev/* and uses /udev/*= =20 > instead)? Should I just go in and mknod my hda* devices again or would th= at not=20 > be a good idea? Anyone have an idea what I might have set up wrong; or do= es=20 > this look as if a piece of software is missing??? Well, I'm not an expert on udev yet, and other people on the list can probably correct me if I make a mistake somewhere (hopefully, they'll be gentle). udev is a completely userspace program, unlike devfs that lived=20 partly in the kernel. udev will probably be started as part of init.d, meaning it won't start up until after / has been mounted. This is a catch-22, of course, since the system needs udev to run to find the root partition and console, and udev won't start up until the system is up. So, the fix this, you have to create a initrd(?) image to load up the initial system with the bare minimum devices statically created (your /, console etc), and then switch over to udev once / has been mounted. Right now, udev only lives on one directory. Check your /etc/udev/udev.conf entry for udev_root for where that is. If it is /udev, /dev is not used at all. As to your /dev/loop0-/dev/loop7, I suspect you have loop either statically linked, or loaded as a module. I try to load the loop module, and those devices got created. Finally, even though devfs has been set to obsolete in 2.6.x, it won't=20 be removed yet, so you can safely use it if it works for you for now. =20 I personally run devfs to manage my /dev, while I'm testing udev on=20 /udev. --=20 John L. Fjellstad web: http://www.fjellstad.org/ Quis custodiet ipsos custodes --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iEYEARECAAYFAkAr6iQACgkQkz0vhQtHHRiv0ACfQtIxFkU3CzDuZqcshgNKXV/o O9wAoMAbw0lwQurC7HvtI2QA0MoIO4+0 =zi2J -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8-- ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel