mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: Andrea Barisani <lcars@gentoo.org>
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>,
	linux-hotplug-devel@lists.sourceforge.net,
	Greg KH <greg@kroah.com>
Subject: Re: does udev really require hotplug?
Date: Sat, 03 Jan 2004 23:21:59 +0200	[thread overview]
Message-ID: <1073164919.6075.41.camel@nosferatu.lan> (raw)
In-Reply-To: <20040102101051.GA12073@sole.infis.univ.trieste.it>

[-- Attachment #1: Type: text/plain, Size: 863 bytes --]

On Fri, 2004-01-02 at 12:10, 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?

Yes, you just miss all other events that hotplug usually handles, and
not udev ...

>  It's not clear if some features are lost by not having 
> hotplug script installed. Also is this policy subject to changes in the near
> future?
> 

I do not think so, but Greg will have to comment ...


-- 

Martin Schlemmer




[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-01-03 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 10:10 Andrea Barisani
2004-01-02 20:19 ` Greg KH
2004-01-02 22:56   ` Andrea Barisani
2004-01-02 23:25     ` Jon Smirl
2004-01-03 22:17     ` Martin Schlemmer
2004-01-03 21:21 ` Martin Schlemmer [this message]

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=1073164919.6075.41.camel@nosferatu.lan \
    --to=azarah@gentoo.org \
    --cc=greg@kroah.com \
    --cc=lcars@gentoo.org \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®