From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Bainbridge <chris.bainbridge@gmail.com>
Subject: Re: Cannot create domU
Date: Sat, 24 Sep 2005 20:00:12 +0000
Message-ID: <623652d505092413006f3950b@mail.gmail.com>
References: <5d7aca9505092307156e0c7f00@mail.gmail.com>
	<20050923173759.GA25613@vrable.net>
	<623652d5050923153973b9804c@mail.gmail.com>
	<7d249e777fd88c08faab74751b15fca6@cl.cam.ac.uk>
	<623652d50509240354750991d3@mail.gmail.com>
	<9f173d1d7dea2ed7b9d458acd070f552@cl.cam.ac.uk>
Reply-To: Chris Bainbridge <chris.bainbridge@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <9f173d1d7dea2ed7b9d458acd070f552@cl.cam.ac.uk>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>, gregkh@gentoo.org
List-Id: xen-devel@lists.xenproject.org

On 24/09/05, Keir Fraser <Keir.Fraser@cl.cam.ac.uk> wrote:
>
> I guess it's possible it is looking in /etc/hotplug.d. If so it really
> ought to be updated. Alternatively, some distros have /sbin/hotplug
> search in /etc/hotplug.d, but they add a script to
> /etc/hotplug.d/defaults/ which also searches in /etc/hotplug/. That
> gives you the benefit of searching in both locations.
>
> Anyway, I think it's gentoo's udevsend that is at fault here. Every
> other distro we know of searches /etc/hotplug/ these days.

Gentoo has a udev rule that runs /sbin/udev_run_hotplugd (from
/etc/udev/rules.d/50-udev.rules):

# be backward compatible for a while with the /etc/dev.d and
/etc/hotplug.d/ systems
# run /etc/hotplug.d/ stuff only if we came from a hotplug event, not
for udevstart
ENV{UDEVD_EVENT}=3D=3D"1", RUN+=3D"/sbin/udev_run_hotplugd"

The path /etc/hotplug.d is hardcoded into udev_run_hotplugd - it
doesn't search anywhere else. I don't understand why it doesn't run
the agent scripts in /etc/hotplug.