All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Surekha.PC" <surekhap@cisco.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: udev does not create scsi disk entries during bootup
Date: Wed, 19 Nov 2003 13:48:03 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-106924986702673@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106870290127081@msgid-missing>


Hi all,

 Request your attention for the problem I am facing. This issue is
urgent for our iSCSI driver inclusion to 2.6 kernel.

Appreciate your response.

Thanks,
surekha

-----Original Message-----
From: Surekha.PC [mailto:surekhap@cisco.com] 
Sent: Tuesday, November 18, 2003 1:42 PM
To: 'Martin Hicks'
Cc: 'linux-hotplug-devel@lists.sourceforge.net'
Subject: RE: udev does not create scsi disk entries during bootup



>> Hi,
>>
>>   I am not able to run udev during boot time inspite of having
>> installed udev, and the associated configuration. Appreciate help in 
>> resolving this issue soon.
>> 
>> Is this feature working for udev-005 right now or one needs to
>> manually run "udev add/remove" to configure devices ?

>I suspect that you still have to run udev-005 manually unless the 
>devices are detected after the hotplug service starts
>(i.e., if your scsi disk code is a module).  Is that right Greg?


Ok, that applies for native scsi disks. I have a iSCSI setup. My iSCSI
disks are detected long after hotplug service has started. In that case,
the device entries should have been created by udev. Does this still
require sd_mod to be loaded as a module?

Thanks,
surekha

 

-----Original Message-----
From: Martin Hicks [mailto:mort@wildopensource.com] 
Sent: Monday, November 17, 2003 6:33 PM
To: Surekha.PC
Cc: linux-hotplug-devel@lists.sourceforge.net
Subject: RE: udev does not create scsi disk entries during bootup


On Sun, 2003-11-16 at 23:52, Surekha.PC wrote:
> Hi,
> 
>   I am not able to run udev during boot time inspite of having
> installed udev, and the associated configuration. Appreciate help in 
> resolving this issue soon.
> 
> Is this feature working for udev-005 right now or one needs to
> manually run "udev add/remove" to configure devices ?

I suspect that you still have to run udev-005 manually unless the
devices are detected after the hotplug service starts (i.e., if your
scsi disk code is a module).  Is that right Greg?

mh
-- 
Martin Hicks                Wild Open Source Inc.
mort@wildopensource.com     613-266-2296





-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
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-19 13:48 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
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 [this message]
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-106924986702673@msgid-missing \
    --to=surekhap@cisco.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 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.