Linux Hotplug development
 help / color / mirror / Atom feed
From: Francis Barton <fbarton@fish.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: little udev problem - loop devices instead of hda devices!
Date: Sun, 15 Feb 2004 03:28:00 +0000	[thread overview]
Message-ID: <1076815679.6858.16.camel@localhost.localdomain> (raw)
In-Reply-To: <1076601040.402ba0d05eb01@webmail.fish.co.uk>

On Fri, 2004-02-13 at 01:32, Greg KH wrote:
> > Overall, it seemed to handle most of my devices just fine, and I got a really 
> > slimline /udev directory with all my devices just sitting there and no crud.
> > 
> > Except... no hard drive. The computer didn't actually boot because it couldn't 
> > find a console. Using my rescue disk I went in and mknodded a /dev/console 
> > file. The next time it booted a bit further until it said "Error: canot 
> > find /dev/hda1 - no such file or device" (I paraphrase).
> 
> Are you trying to use udev to manage your /dev?

Trying to, yes! I want to persevere with it to get it to work, and
follow the development of udev. I am not a programmer myself but I find
the way programs like this one function really interesting.

I have set udev root to /dev - this worked ok but have decided to set it
back to /udev again and keep devfs hanging on.

> I'd really recommend trying to get a 2.6 kernel to boot properly on your
> box before worrying about udev.

Well it's booting ok now - using /dev rather than /udev I think - I had
to mknod /dev/console /dev/null and /dev/hda1-7 by hand to get it to
boot though. So I'm kind of back where I started but ready to try again.
I don't really have any unusual hardware so I feel it ought to work ok
for me.

> After you do that, then try putting udev into your initrd.  The latest
> version of udev from Fedora does this I think.

I will try the RPM but I would really like to know how to do this by
hand in order to understand better - with mkinitrd I presume? I Googled
for "udev initrd" and didn't find much of use to me.

> Good luck,

Thanks, I'll be back for help again I guess. I think I've got myself a
little confused about exactly how to implement udev but I'll keep trying
till it works. My instinct says it should be simple ;-)

Francis



-------------------------------------------------------
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\x1356&alloc_id438&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

  parent reply	other threads:[~2004-02-15  3:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 15:50 little udev problem - loop devices instead of hda devices! fbarton
2004-02-12 21:03 ` John L. Fjellstad
2004-02-13  1:32 ` Greg KH
2004-02-15  3:28 ` Francis Barton [this message]
2004-02-21 17:43 ` Francis Barton
2004-02-21 17:51 ` Jon Smirl

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=1076815679.6858.16.camel@localhost.localdomain \
    --to=fbarton@fish.co.uk \
    --cc=linux-hotplug@vger.kernel.org \
    /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