From: "Surekha.PC" <surekhap@cisco.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: udev does not create scsi disk entries during bootup
Date: Thu, 20 Nov 2003 15:11:05 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106934093108581@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106870290127081@msgid-missing>
Hi,
>>
>> root disk will show >up as being found by udev for right now, unless
>> you put udev into initramfs somehow.
>>
>> Ok, that being the case, the local scsi disks would not be seen by
>> udev during bootup unless it is part of initrd, right ?
>udev would need to be initrd, and sysfs needs to be mounted. Have you
done that?
Ok thanks for that, I will try making udev part of initrd and test this
feature.
>> However I am bring up my iSCSI services, after root disk is mounted,
>> so these disks have to be recognised by udev. Stopping the iSCSI
>> service, will deconfigure the iSCSI disks, this should remove the
disk
>> entries in udev. Is it possible to achive this funtionality with the
>> latest hotplug and udev?
>Yes, make sure that sysfs is mounted before you start finding the iscsi
devices.
I have automounted sysfs. The /sys/block/ shows the iSCSI device
entries.
But hotplug event is not notified by the kernel. This is the reason why
udev
is not getting triggered for configuring device nodes.
I have few queries about the way hotplug mechanism works.
The /etc/hotplug/scsi.agent script does not seem to handle the "ACTION"
add/remove of a scsi device ?
Also the "/usr/src/linux/drivers/scsi" driver code does not have any
hotplug
initialization functions, then how does it indicate "/sbin/hotplug"
program about the addition/deletion of device ?
I have referred the hotplug documentation in the follg URL FYI
http://linux-hotplug.sourceforge.net/?selected=hotplug
Thanks,
surekha
-------------------------------------------------------
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
next prev parent reply other threads:[~2003-11-20 15:11 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
2003-11-19 23:57 ` Greg KH
2003-11-20 15:11 ` Surekha.PC [this message]
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-106934093108581@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.