Brian:
=09In my company this is a test project, so we found a bounch of
computers that nobody was using. In one of them we've made a fresh
install of RH 9.0, then patched it with the latest packages avalible
from redhat and installed the SSI suite RPMs. While running install
we've found out that the the SysVinit complained, so we installed it
with --old-package. We also added libxml2. We also commented from
/etc/rc.sysinit the initialization of USB devices (redhat should make
this optional).
=09I've noticed that node #1 while booting complains as
follows: INIT:Error create initstate, failover compromised. Yesterday
we found a new computer for our experiment to act as node#2, we
configured it and made it boot from a floppy created in rom-o-matic.
This computer boots, and somewhere it stales at the beggining of the
init process. I hope to find some spare time to look after this in a
while.
=09Do yo have any idea of the next release date? I don't find my
self with the time and knowledge to fix my problems, but I can
betatest and return feedback.
=09=09=09Andr=E9s
Post by Andres Tarallo (CHASQUE)I'm running with success OpenSSI in a fresh redhat 9.0 instalation,
from the RPMs. Very little has to be done to achieve this goal.
=20
I'm clearing my notes (this i s atest instalation) and then I will
send a full report to let you know what differs from the standard RPM
instalation.
=20
I tried that myself with OpenSSI 0.9.9. One problem I ran into is that=20
cluster_mkinitrd grabs the LTS version of libc and several other=20
libraries, which are incompatible with the 2.4.18-18.7.x_ssi_3ssi=20
kernel. It also made me nervous that I was significantly backrevving=20
several packages, which broke dependencies of some non-SSI packages.
=20
The next release will be based on Red Hat 9 packages, so it will be=20
inherently compatible with that distro.
=20
Brian