From: Greg KH <greg@kroah.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Chris Bainbridge <chris.bainbridge@gmail.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: Cannot create domU
Date: Mon, 26 Sep 2005 08:01:35 -0700 [thread overview]
Message-ID: <20050926150135.GA15781@kroah.com> (raw)
In-Reply-To: <22f2b04bae14c3efa4833ce013cc4542@cl.cam.ac.uk>
On Mon, Sep 26, 2005 at 03:41:38PM +0100, Keir Fraser wrote:
>
> On 26 Sep 2005, at 15:14, Greg KH wrote:
>
> >That's been "depreciated" for quite some time now. I would recommend
> >you switch to moving your script to /etc/hotplug.d/xen/ or
> >/etc/hotplug.d/default/ (depending on how your hotplug event is being
> >created. Which reminds me, how is it? Pointers to code anywhere?)
>
> We originally placed the script in /etc/hotplug.d/xen, but found that
> didn't work on some distros. Can't remember which ones, nor how old
> they were. We should perhaps detect such systems and treat them
> specially in our install script, and move the script back to
> /etc/hotplug.d by default.
Yes, some very old distros did not have the multiplexed /sbin/hotplug
program which would run stuff in /etc/hotplug.d/, but they should be all
gone now :)
> Our main hotplug event function is in
> drivers/xen/xenbus/xenbus_probe.c
Have an online source browser anywhere?
>, I think (it's used by our network driver at least). Actually xenbus
>registers all our virtual devices with sysfs, and I guess that
>generates some hotplug events automatically?
Yes, it will. You should _never_ call /sbin/hotplug on your own. The
one last holdout in the kernel is the input subsystem, and that will be
fixed very soon.
thanks,
greg k-h
next prev parent reply other threads:[~2005-09-26 15:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-23 14:15 Cannot create domU NAHieu
2005-09-23 17:37 ` Michael Vrable
2005-09-23 17:43 ` Michael Vrable
2005-09-23 18:00 ` Michael Vrable
2005-09-23 22:39 ` Chris Bainbridge
2005-09-24 7:38 ` Keir Fraser
2005-09-24 10:54 ` Chris Bainbridge
2005-09-24 13:21 ` Keir Fraser
2005-09-24 17:32 ` NAHieu
2005-09-24 20:00 ` Chris Bainbridge
2005-09-25 10:19 ` Keir Fraser
[not found] ` <20050926124707.GA13414@kroah.com>
2005-09-26 13:23 ` Keir Fraser
[not found] ` <20050926141407.GA15384@kroah.com>
2005-09-26 14:41 ` Keir Fraser
2005-09-26 15:01 ` Greg KH [this message]
2005-09-26 15:41 ` Keir Fraser
2005-09-26 21:22 ` Greg KH
2005-09-27 15:33 ` Chris Bainbridge
2005-09-30 14:48 ` Chris Bainbridge
2005-09-26 14:59 ` Gerd Knorr
2005-09-26 15:54 ` Chris Bainbridge
2005-10-06 15:54 ` network & block device setup via udev Gerd Knorr
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=20050926150135.GA15781@kroah.com \
--to=greg@kroah.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=chris.bainbridge@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.