All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 048 release
Date: Thu, 09 Dec 2004 22:07:49 +0000	[thread overview]
Message-ID: <200412092207.49139.andrew@walrond.org> (raw)
In-Reply-To: <20041208194618.GA28810@kroah.com>

On Thursday 09 Dec 2004 21:56, Kay Sievers wrote:
> On Thu, 2004-12-09 at 21:47 +0000, Andrew Walrond wrote:
> > On Wednesday 08 Dec 2004 19:46, Greg KH wrote:
> > > Ok, version 048 has been released to fix the build errors for the
> > > extras/ directory.  It's available at
> > >  kernel.org/pub/linux/utils/kernel/hotplug/udev-048.tar.gz
> >
> > I've built a boot cd with linux-2.6.10-rc3, udev 048 and latest hotplug.
> >
> > When I boot a machine with my CD, udev doesn't create /dev/hda
> > I can't fathom why. Any reasons why it wouldn't create it?
> > It _has_ created /dev/hdc, (the cdrom drive) and all the other usual
> > devices.
> >
> > /proc/ide shows hda->ide0/hda
> > /proc/ide/ide0/hda/model = MAXTOR 6L040J2
> >
> > This is a simple Asus P4PE m/b with intel ICH4 IDE.
> >
> > ( I know I can mknod, but since this is supposed to be a general purpose
> > boot/toolkit CD, I'd like to make sure udev is working properly)
> >
> > Any clues? hda currently contains windows server and I'm rather eager to
> > wipe it ;)
>
> Do you run udevstart at one of the first things after boot?
> udev only creates a node if it gets a hotplug event, but that may not be
> the case for your boot drive...

I run start_udev right after mounting proc and sys. Note that the boot drive 
node gets created just fine (hdc, the cdrom) but hda, the harddrive, doesn't.

Andrew


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
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-12-09 22:07 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 18:58 [ANNOUNCE] udev 047 release Greg KH
2004-12-08 18:58 ` Greg KH
2004-12-08 19:28 ` Greg KH
2004-12-08 19:28   ` Greg KH
2004-12-08 19:46   ` [ANNOUNCE] udev 048 release Greg KH
2004-12-08 19:46     ` Greg KH
2004-12-08 21:56     ` Tomasz Kłoczko
2004-12-08 21:56       ` Tomasz Kłoczko
2004-12-08 22:05       ` Greg KH
2004-12-08 22:05         ` Greg KH
2004-12-08 22:15         ` Kay Sievers
2004-12-08 22:15           ` Kay Sievers
2004-12-08 23:25         ` Tomasz Kłoczko
2004-12-08 23:25           ` Tomasz Kłoczko
2004-12-08 22:22     ` Marco d'Itri
2004-12-08 23:56     ` Marco d'Itri
2004-12-09  0:08     ` Mike Frysinger
2004-12-09 21:47     ` Andrew Walrond
2004-12-09 21:47       ` Andrew Walrond
2004-12-09 23:25       ` Greg KH
2004-12-09 23:25         ` Greg KH
2004-12-10  8:46         ` Andrew Walrond
2004-12-10  8:46           ` Andrew Walrond
2004-12-09 21:56     ` Kay Sievers
2004-12-09 22:07     ` Andrew Walrond [this message]
2004-12-09 22:18     ` Kay Sievers
2004-12-09 22:24     ` Andrew Walrond
2004-12-09 22:27     ` Kay Sievers
2004-12-09 22:33     ` Andrew Walrond
2004-12-11 16:44 ` [ANNOUNCE] udev 047 release [u] Martin Schlemmer [c]
2004-12-11 16:44   ` Martin Schlemmer [c]
2004-12-11 17:46   ` Kay Sievers
2004-12-11 17:59   ` Martin Schlemmer [c]
2004-12-13 16:44   ` Martin Schlemmer [c]
2004-12-13 17:08   ` Kay Sievers
2004-12-13 19:18   ` Martin Schlemmer [c]
2004-12-14  0:46   ` Kay Sievers
2004-12-17  0:08   ` Greg KH
2004-12-17 17:11   ` Martin Schlemmer [c]
2004-12-17 23:32   ` Greg KH

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=200412092207.49139.andrew@walrond.org \
    --to=andrew@walrond.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.