We used RHEL5 + perceus successfully. I had to modify the perceus boot image for x86_64, but it may have been a kexec/hardware specific issue I ran into. If you run into an issue with it I can help you along.
I don't think the 9P module was built in, but I don't think you would use it. On Thu, Aug 28, 2008 at 11:31 AM, Daniel Gruner <[EMAIL PROTECTED]> wrote: > > Thanks, Abhishek. > > I will try it and report on my success/lack thereof. > > Just for info, I am using a RHEL5 distribution, but with the 2.6.26 > kernel so that it supports 9p. Has anybody been successful with this > distribution? Otherwise, is there a preferred one? > > Daniel > > On 8/28/08, Abhishek Kulkarni <[EMAIL PROTECTED]> wrote: > > > > Daniel, > > > > It is _not_ necessary to install cAos Linux to use Perceus. Perceus > > supports most, if not all, distributions. > > > > XCPU is bundled up as a module within Perceus. The documentation at > > http://www.perceus.org/docs/perceus-userguide-1.4.0.pdf is quite > > extensive at that and has details on importing and activating modules. > > It's quite simple even if you find yourself wanting to tinker with the > > XCPU Perceus module (it's just a shell script that runs at a specified > > provisioning state/level) > > > > > > -- Abhishek > > > > > > On Thu, 2008-08-28 at 14:17 -0400, Daniel Gruner wrote: > > > Yes, that is a possibility. Instructions on that, please? > > > I tried installing caos linux, but it doesn't quite finish doing the > install. > > > > > > Daniel > > > > > > On 8/28/08, ron minnich <[EMAIL PROTECTED]> wrote: > > > > > > > > Use perceus. > > > > > > > > Ron > > > > > > > > > > > > On 8/28/08, Daniel Gruner <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Hi All, > > > > > > > > > > The list has been very quiet lately... :-) > > > > > > > > > > I've been trying, yet again, to install the latest xcpu2 in a > test > > > > > cluster. Ron's instructions on the xcpu.org site seem to be > outdated, > > > > > and partly buggy too. For instance, here are a couple of points: > > > > > > > > > > - After doing: > > > > > > > > > > make xcpu-tarball > > > > > > > > > > make ramfs-tarball > > > > > > > > > > make install > > > > > > > > > > I don't know whether xcpu2 has actually been built (I suspect > not), > > > > > and it certainly has not been installed (e.g. no xrx, or xcpufs, > or > > > > > any of that stuff has been installed). > > > > > > > > > > - The command > > > > > > > > > > export u=`uname -r` > > > > > ./mk-initramfs-oneSIS -f initrd-$u.img $u -nn -rr \ > > > > > -o ../overlays/xcpu-64 \ > > > > > -w e1000 \ > > > > > -w forcedeth \ > > > > > -w ext3 > > > > > > > > > > should really be > > > > > > > > > > ./mk-xcpu-oneSIS .... > > > > > > > > > > in order that the 9p and 9pnet modules get loaded into the > initrd. > > > > > > > > > > Can someone please take a look and revise the instructions (and > let us > > > > > mere mortals know what to do)? > > > > > > > > > > > > > > > Furthermore, is xcpu2 actualy useable for production work? What > about > > > > > its integration with a scheduler/resource manager? What about > MPI? > > > > > > > > > > Regards, > > > > > Daniel > > > > > > > > > > > > > > > > > -- > > > > Sent from Gmail for mobile | mobile.google.com > > > > > > > > >
