linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev does not create scsi disk entries during bootup
Date: Fri, 14 Nov 2003 01:07:59 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106877429811400@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106870290127081@msgid-missing>

On Thu, Nov 13, 2003 at 01:31:33PM +0530, Surekha.PC wrote:
> 
> Hi Greg,
> 
> >Anything in your debug logs to show that udev is really running? Is
> >/etc/hotplug.d/default/udev.hotplug pointing to your udev binary?
> 
> The debug log is empty, it seems udev is not being invoked by hotplug
> program.
> The symlink exists from udev.hotplug to the binary.

And does your /sbin/hotplug binary say that it will read from the
/etc/hotplug.d directories?

> CONFIG_HOTPLUG is enabled in the kernel.
> The sd_mod driver is not a module, it is made part of the kernel.
> Is that ok?

That's fine, but remember, only devices found after init mounts your
root disk will show up as being found by udev for right now, unless you
put udev into initramfs somehow.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.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:[~2003-11-14  1:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-13  5:28 udev does not create scsi disk entries during bootup Surekha.PC
2003-11-13  6:25 ` Greg KH
2003-11-13  8:13 ` Surekha.PC
2003-11-14  1:07 ` Greg KH [this message]
2003-11-14  3:55 ` Surekha.PC
2003-11-17  4:54 ` Surekha.PC
2003-11-17 13:02 ` Martin Hicks
2003-11-18  8:23 ` Surekha.PC
2003-11-19 13:48 ` Surekha.PC
2003-11-19 23:57 ` Greg KH
2003-11-20 15:11 ` Surekha.PC
2003-11-20 16:46 ` Greg KH
2003-11-20 16:53 ` Greg KH
2003-11-20 18:38 ` Clay Haapala
2003-11-20 18:41 ` Greg KH
2003-11-20 19:11 ` Clay Haapala
2003-11-21  5:49 ` Surekha.PC
2003-11-21  6:12 ` Greg KH
2003-11-21  6:52 ` Surekha.PC
2003-11-22 18:12 ` Greg KH
2003-11-24 12:50 ` Surekha.PC
2003-11-24 22:14 ` Greg KH
2003-11-25 12:56 ` Surekha.PC
2003-11-25 13:12 ` Martin Hicks
2003-11-25 13:40 ` Surekha.PC
2003-11-25 16:36 ` Greg KH
2003-11-27 11:36 ` Surekha.PC
2003-12-01 23:59 ` 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=marc-linux-hotplug-106877429811400@msgid-missing \
    --to=greg@kroah.com \
    --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;
as well as URLs for NNTP newsgroup(s).