WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Cannot create domU

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Cannot create domU
From: Chris Bainbridge <chris.bainbridge@xxxxxxxxx>
Date: Sat, 24 Sep 2005 20:00:12 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, gregkh@xxxxxxxxxx
Delivery-date: Sat, 24 Sep 2005 19:57:55 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FiOOuQ+z5IZoSuoA1zE79pSb+FWS3J55VK6PEZ89HdGVSORfu85TjPQyxp3d1jOj5jUqTdNdwk6Oea/0XEOl20+7qtWW6sgsseDqwGFk2WCpytvgl45a45NQATpxqTUnXravrA5oSxZOku4RgqnbwGgwFpwUHeMzVyU40k4Y9r8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <9f173d1d7dea2ed7b9d458acd070f552@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <5d7aca9505092307156e0c7f00@xxxxxxxxxxxxxx> <20050923173759.GA25613@xxxxxxxxxx> <623652d5050923153973b9804c@xxxxxxxxxxxxxx> <7d249e777fd88c08faab74751b15fca6@xxxxxxxxxxxx> <623652d50509240354750991d3@xxxxxxxxxxxxxx> <9f173d1d7dea2ed7b9d458acd070f552@xxxxxxxxxxxx>
Reply-to: Chris Bainbridge <chris.bainbridge@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 24/09/05, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> 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}=="1", RUN+="/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.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel