Difference between revisions of "Upgrading destiny"

From CUC3
Jump to navigation Jump to search
import>Cen1001
import>Cen1001
 
Line 8: Line 8:
   
 
--[[User:cen1001|Catherine]] 14:50, 28 March 2006 (BST)
 
--[[User:cen1001|Catherine]] 14:50, 28 March 2006 (BST)
  +
  +
Upgrading destiny was amazingly painless and only took two days.
  +
  +
The only problem so far has been that I had forgotten that the old destiny had an MPI library installed (a Debian package of LAM) and it seems that at least one person relied on this. This happened because I used a sword package list to produce the package list for the SuSE install, thinking they were the same.

Latest revision as of 15:42, 27 April 2006

Destiny is to be upgraded to SuSE and at the same time have a new disk installed to give a bigger /scratch and /usr/local.

I will be withdrawing CRYSTAL98 and Portland versions less than 5.2. I will be adding gnuplot, svn, icc, and recent iforts.

I'd like to lose MPI from destiny. Athens is the place to run MPI.

I also intend to implement modules.

--Catherine 14:50, 28 March 2006 (BST)

Upgrading destiny was amazingly painless and only took two days.

The only problem so far has been that I had forgotten that the old destiny had an MPI library installed (a Debian package of LAM) and it seems that at least one person relied on this. This happened because I used a sword package list to produce the package list for the SuSE install, thinking they were the same.