From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Theurer Subject: Re: [RFC] Cleaning up /proc/xen Date: Thu, 08 Sep 2005 07:54:17 -0500 Message-ID: <43203479.9000004@us.ibm.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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