From: "Andrea Barisani" <lcars@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: does udev really require hotplug?
Date: Mon, 29 Mar 2004 15:39:22 +0000 [thread overview]
Message-ID: <007101c415a4$01efd050$d100000a@sbs2003.local> (raw)
In-Reply-To: <20040102101051.GA12073@sole.infis.univ.trieste.it>
On Fri, Jan 02, 2004 at 12:19:05PM -0800, Greg KH wrote:
> On Fri, Jan 02, 2004 at 11:10:51AM +0100, Andrea Barisani wrote:
> >
> > Hi everybody and happy new year!
> >
> > Just one simple question about a very simple matter that right now
> > I can't figure out: does udev need hotplug package presence?
> >
> > >From your README:
> >
> > If for some reason you do not install the hotplug scripts, you must tell the
> > kernel to point the hotplug binary at wherever you install udev at. This can
> > be done by:
> > echo "/sbin/udev" > /proc/sys/kernel/hotplug
> >
> >
> > ...does this work properly?
>
> It should. Does it not for you?
>
> > It's not clear if some features are lost by not having hotplug script
> > installed.
>
> None of the other programs that hook off of the hotplug program will be
> available to you if you do this (automatic driver loading, firmware
> loading, devlabel, etc.)
>
> > Also is this policy subject to changes in the near future?
>
> What policy? If you don't have the hotplug package installed, then you
> can still use udev. If you have the hotplug package installed, I've
> detailed how you can still use udev. What's the problem? :)
>
> thanks,
>
> greg k-h
Ok, now it's all clear :). It wasn't so clear from the documentation (at
least for me) and since I'm not fully familiar with hotplug features I've
decided to ask ;).
Thanks a lot for your feedback
Bye
--
Andrea Barisani <lcars@gentoo.org> .*.
Gentoo Linux Infrastructure Developer V
( )
GPG-Key 0x864C9B9E http://dev.gentoo.org/~lcars/pubkey.asc ( )
0A76 074A 02CD E989 CE7F AC3F DA47 578E 864C 9B9E ^^_^^
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
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:[~2004-03-29 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 10:10 does udev really require hotplug? Andrea Barisani
2004-01-02 20:19 ` Greg KH
2004-01-02 22:56 ` Andrea Barisani
2004-01-02 23:25 ` Jon Smirl
2004-03-29 15:39 ` Greg KH
2004-03-29 15:39 ` Andrea Barisani [this message]
2004-03-29 15:39 ` Jon Smirl
2004-03-29 15:40 ` Martin Schlemmer
2004-03-29 15:40 ` Martin Schlemmer
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='007101c415a4$01efd050$d100000a@sbs2003.local' \
--to=lcars@gentoo.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 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).