Re: [SSI-users] Generic manual install instructions for CVS version?

[Scott W. <sc...@sl...>]

Hi John,

"Fiendishly difficult" does change my strategy for the moment, but I'm still
curious what goes into converting a system to run OpenSSI.  Obviously, one
man's curiosity doesn't justify the work involved in someone actually typing
that up.  A rough overview might be fun in the unlikely case that you're
bored.

bash-3.1$ ps ax | grep -e udev -e hal
bash-3.1$ 

No problem there.

My strategy for the moment is to snapshot FC3 before and after the package
install and dig through the diffs and use that to gauge to the scope of work
involved in a one-off Slackware conversion.  Hardware is dedicated to the 
task, and I'm not afraid of broken eggs >=)

I might just settle on the FC3 rpms, but I thought taking a stab at this
would be fun.

Thank you very much for your comments, and please pardon my unsolicited
elaboration.

Regards,
-scott


On  0, John Hughes <john@Calva.COM> wrote:
> Scott Walters wrote:
> > Is there a document somewhere that lists steps to manually install 
> > the CVS working copy of OpenSSI on a joe random Linux machine?
> >   
> It could be done, but it would be fiendishly difficult.  Many
> distribution packages need to be modified to deal with their different
> clusterview/localview requirements.  (In general we want an OpenSSI
> system to be SSI, I.E. processes don't have to know which node they're
> on, or even that the machine has multiple nodes.  This breaks down for
> some system tasks, like udev and hal which obviously care about the
> exact hardware on the node.  Subsystems that should be run in parallel
> across nodes may also need modification).
> 
> Unless you have many man-months to expend in making an OpenSSI port for
> slackware I'd recommend using one of the existing ports - FC or Debian.
> 
> If you don't want to trash your existing systems you could investigate
> running OpenSSI under KVM or QEMU - I find that's often the best way of
> debugging and developing things.