From: Clay Haapala <chaapala@cisco.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev does not create scsi disk entries during bootup
Date: Thu, 20 Nov 2003 19:11:33 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-106935556629336@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-106870290127081@msgid-missing>
On Thu, 20 Nov 2003, Greg KH spake thusly:
> On Thu, Nov 20, 2003 at 12:38:12PM -0600, Clay Haapala wrote:
>> On Thu, 20 Nov 2003, Greg KH uttered the following:
>> > On Wed, Nov 19, 2003 at 07:06:03PM +0530, Surekha.PC wrote:
>> >>
>> >> Hi all,
>> >>
>> >> Request your attention for the problem I am facing. This issue
>> >> is
>> >> urgent for our iSCSI driver inclusion to 2.6 kernel.
>> >
>> > Getting udev to work for your devices has nothing to do with
>> > getting your iscsi driver to be included in the main 2.6 kernel.
>> > Why do you say that?
>> >
>> > thanks,
>> >
>> In the effort to get this iSCSI driver included into the 2.6
>> kernel, we are making a number of changes in response to comments
>> from the SCSI maintainers. Many of these comments are regarding
>> work-arounds or designs currently in our [2.2/2.4-derived] driver
>> that should be removed or redesigned in favor of features now
>> available in 2.6. Udev is one of those features.
>
> Um, but what features does udev require, that any other well working
> scsi driver not require? sysfs support? I thought the scsi core
> would provide that for you.
>
> thanks,
>
> greg k-h
Being newest to iSCSI dev, I probably shouldn't have entered the
discussion, since I'm not sure that what is needed is a new udev
feature, or rather a better understanding of udev.
--
Clay Haapala (chaapala@cisco.com) Cisco Systems SRBU +1 763-398-1056
6450 Wedgwood Rd, Suite 130 Maple Grove MN 55311 PGP: C89240AD
Well, looks like hypocrisy is back on the airwaves.
C'mon, Rush! Do the crime, do the time, right?
-------------------------------------------------------
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 19: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
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 [this message]
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-106935556629336@msgid-missing \
--to=chaapala@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 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).