Dan
Great, thanks for the reply. I was not inferring any thing on the
requirement of mounting sysfs, just trying to understand if there was
another method of checking for sysfs prior to the mount.
And the one that came from the list was what I was looking for.
==================
And there's grep sysfs /proc/filesystems (|| modprobe -q sysfs, if
compile-as-module is ever added to sysfs).
===================
Thanks Dan, thanks for the patch.
On Tue, 2006-03-14 at 09:10 -0800, Daniel Stekloff wrote:
> On Mon, 2006-03-13 at 19:10 -0800, Woody Marvel wrote:
> > Dan
> >
> > Is that the only check you can used is 2.6 from uname? Is there any
> > other piece of info you can check? <not knowing sysfs that well>
>
>
> Hi Woody,
>
> Yeah... sysfs is compiled into the 2.6 domU kernel, which we are
> assuming is the kernel for the ramdisk. The HVM disk.img, which goes and
> finds its own non-xen kernel, could be an issue - if the kernel it finds
> doesn't compile in sysfs - such as an embedded kernel. I'm not sure this
> really is an issue, however. Even if it shouldn't find sysfs to mount,
> the image will still boot and still be able to run tests.
>
> Is that ok?
>
> Thanks,
> Dan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
--
Sincerely, Woody Marvel
IBM Linux Technology Center
Open Source Virtualization
email: marvel@xxxxxxxxxx
503-578-3833 Beaverton, OR 97006
**********************************
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home