Hi Richard
I have just been through this myself. In my case I installed an older
version of RHEL3 (update 1? - how do you tell?) from CDs that came with a
computer a couple of years ago. I then installed OSCAR 4.1 (and had to
solve a whole bunch of missing .rpm problems by downloading them from the
web and putting them in /tftpboot/rpm). I then built my cluster and THEN
brought the head node up2date (to the latest status provided by RH support).
So far I have updated the kernel in the image and on the comp nodes, but I
have not yet updated any of the (several hundred?!) other .rpms that need?
updating in the image and on the nodes because everything seems to be
running OK, and if it ain't broke why fix it? (I need to keep the headnode
up2date for security reasons, but inside the cluster security isn't an issue).
I recently asked this forum how to go about updating the comp. nodes and
Bernhard Li provided a reply you should find in the last month of emails in
this forum. This more-or-less worked for updating the kernel, although
there is one "gotcha" in that the latest kernel version from Redhat
(2.4.21-32.0.1.ELsmp) makes a label that is too long for LILO and the
systemconfigurator step of updating the nodes will fail. To solve this,
manually edit the
\var\lib\systemimager\images\oscarimage\etc\systemconfig\systemconfig.conf
file to shorten the labels IN 3 PLACES (DEFAULTBOOT=, KERNEL0 LABEL= and
KERNEL1 LABEL=).
There may be a more direct way to do this and avoid the work of updating.
If so, I'd be glad to hear it.
Regards
Giles
At 10:32 AM 8/10/2005, Richard Fairfield wrote:
Hello:
We are in the process of setting up our first cluster, using OSCAR 4.1
and Red Hat Enterprise Linux 3.
The OSCAR installation manual says that only Updates 2 and 3 of RHEL 3 are
supported, not Update 4. But, using the "up2date" service, we are
currently getting Update 5 on our other RHEL 3 systems.
As we understand the process, we need to have updated the "head" node
to the Update level we want to run, and populated the /tftpboot/rpm/
directory with the RPM files from that Update level, before proceeding
with the installation of client nodes. But, so far, we've been unable
to find a way to obtain a specific Update version, such as Update 3,
or even a definition of exactly what RPM packages comprise a particular
Update version.
Can anyone help us with this problem?
[ Please cc any respones to my email address ([EMAIL PROTECTED]).
Because, until tomorrow, I think that I'll only be getting the daily
mailing list archive ]
Thank you,
Richard Fairfield
Math Sciences Computing Center
University of Washington
My Office Telephone Number: 206-685-2303
MSCC Departmental Telephone Number: 206-616-3636
Fax: 206-685-7419
[EMAIL PROTECTED]
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Oscar-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-users
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Oscar-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-users
