From: Andrew Theurer <habanero@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: [RFC] Cleaning up /proc/xen
Date: Thu, 08 Sep 2005 07:54:17 -0500 [thread overview]
Message-ID: <43203479.9000004@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282F1A@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>
>
>
>>>Is this going to make having udev a requirement? (or would we also
>>>mknod some entries in de as part of an install?)
>>>
>>>I guess most distros have had udev for a while.
>>>
>>>
>>Yes - though it'd be good to fix udev start (which takes
>>ages, at least on redhat root filesystems).
>>
>>
>
>Yep, I'd buy a beer for whoever fixed that...
>
>
Is this a Xen problem or just a Redhat problem? I personally noticed
this when moving to 2.6.11 way back when, and I backgrounded the
"$HOTPLUG scsi_device" and "$HOTPLUG scsi" lines in start_udev. For
some reason hotplugging these serially would take about 30 seconds per
disk, even if the disk didn't even exist. Not sure if this is the same
problem. Some (any!) debug info in start_udev would have been nice...
-Andrew
next prev parent reply other threads:[~2005-09-08 12:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 9:28 [RFC] Cleaning up /proc/xen Ian Pratt
2005-09-08 12:54 ` Andrew Theurer [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-08 2:26 Ian Pratt
2005-09-08 2:50 ` Adam Heath
2005-09-08 2:51 ` Steven Hand
2005-09-08 3:24 ` Anthony Liguori
2005-09-08 16:39 ` Chris Wright
2005-09-08 12:54 ` Vincent Hanquez
2005-09-08 1:45 Anthony Liguori
2005-09-08 8:09 ` NAHieu
2005-09-08 18:59 ` Anthony Liguori
2005-09-09 2:18 ` Jed Davis
2005-09-08 22:29 ` Daniel Stekloff
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=43203479.9000004@us.ibm.com \
--to=habanero@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.