Greetings! I don't know about mpich, but lam does have support for using ssh in place of rsh. The problem is is that the default is a compile time option, which can optionally be over-ridden at run-time. So in building a Debian package, one has to choose a default, (which should be rsh instead of ssh for most users, due to speed and the internal network topology of most clusters), and if a dependency is not made on that default, then the package simply won't work unless the user sets their LAMRSH environment variable. I suppose one could duplicate lam-runtime into a lam-runtime-ssh, but this seems a bit excessive. If you want to use lam with ssh, just install rsh, disable it in inetd, set LAMRSH="ssh -x", and you're ready to go!
Take care, Jose Marin <[EMAIL PROTECTED]> writes: > Hi all, > > I wanted to install mpi and some mpi-related packages, but they seem to > depend either on rsh-client and rsh-server, or on the "Heimdal" secure > alternatives. I'm using only ssh (Openssh) and I'd like to stay that way. > > I'm using unstable (woody). Here are some of the packages in question: > > blacs-mpich-dev > blacs1-mpich > mpich > netpipe-mpich > scalapack-mpich-dev > scalapack1-mpich > > Any reason why they can't be made to offer dependencies on ssh as well? > File a bug? > > Cheers, > > Jose > -- > Jose L Marin [EMAIL PROTECTED] > Dept of Mathematics [EMAIL PROTECTED] > Heriot-Watt University > Edinburgh EH14 4AS, U.K. > Phone: +44 131 451 3893 > Fax: +44 131 451 3249 > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- Camm Maguire [EMAIL PROTECTED] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah
