Re: Where is lapack-dev ?
On Fri, Jul 03, 1998 at 10:21:26AM +, Ionut Borcoman at debian wrote:
> From: Ionut Borcoman at debian <[EMAIL PROTECTED]>
> Hi,
>
> I've downloaded some time ago the hamm. Now I need the lapack-dev, but
> it is nowhere between my downloaded files. I do not have for the moment
> a full connection so I do not know if it is still missing or no. Can
> somebody be so kind and tell me if it is back and at what ftp address
> does it have (for ftp-by-email) ?
I believe it was only recently recompiled for libc6 (just before code
freeze). Try
ftp://ftp.debian.org/pub/debian/hamm/hamm/binary-i386/devel/
lapack-dev_2.0.1-2.1.deb
>
> Is anybody packing c++/lapack++ ? How to link lapack to my c/c++
> programs ?
lapack-dev is a fortran library. The consequence of this is that on
Linux, Irix, and perhaps other systems you need to call function_() instead
of function(), and pass all values by address. For example:
Matrix& Matrix::invert() {
int n=4,ipiv[4],info;
float work[4];
sgetrf_(&n,&n,m,&n,ipiv,&info); // float m[4][4]
sgetri_(&n,m,&n,ipiv,work,&n,&info);
return *this;
}
Lapack++ hasn't been packaged yet, but would be welcome. The successor,
NTL, might be a better time investment. http://math.nist.gov/tnt/
>
> I've try something but got ld errors (actually I've forced the
> instalation of lapack-dev from bo which depends on libc5-dev, but got a
> lot of ld errors). Can I use lapack-dev from bo till I get lapack-dev
> from hamm ?
I used the old lapack-dev for a while in a mixed libc5/libc6 environment,
but wouldn't suggest trusting it for production work. If you compile with
the libc5 gcc-altdev package it should be safe.
--
Dr. Drake Diedrich, Research Officer - Computing, (02)6279-8302
John Curtin School of Medical Research, Australian National University 0200
Replies to other than [EMAIL PROTECTED] will be routed off-planet
--
Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Re: updating through a proxy
On Sun, May 17, 1998 at 07:14:37PM -0500, Greg Norris wrote: > I've got a bo (installed from a 1.3.1r6 CD) machine at work, and am > looking for a good way to update it via FTP. The problem I have is > that all FTP connections at our site have to go through a proxy (connect > with the userid "proxyftp", use the command "quote site some.site.name" > to connect to the remote site, and finally login with the "user" > command), and dselect does not appear to be able to accomodate this. > dpkg-http (in hamm) can use a web proxy, if that's an option. I haven't installed it on a bo system, but can't think of any reason it wouldn't work. I've suggested it to a few people in similar circumstances and never heard back from them. (That might not be a good sign...) dpkg-ftp 1.4.9.1 and later have authenticated ftp proxy support. Neither dpkg-http nor dpkg-ftp depend on libc6, so it should be possible to install the latest versions on bo systems without updating anything else. -Drake -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ssh question
On Sun, May 10, 1998 at 09:15:07PM +0100, G. Kapetanios wrote:
>
> Thanks for all the replys. The RSA keys method can be made not to ask for
> anything if you put no passphrase, and that is my question. I can do what
> I want without a passphrase. But is this safe ??
> The man page of ssh-keygen says that if you put no passphrase YOU SHOULD
> KNOW WHAT YOU ARE DOING. This is the scary bit. The man page does not
> bother to explain what the consequences of no passphrase are. Does anyone
> know ??
The danger is that someone gaining your private key by any means is able
to log in to any other machine that accepts that key.
What I do locally is put pass phrases on my private keys, but use
ssh-agent to start the system Xsession script. Then in .xsession, I run
ssh-add. Adter ssh-add returns, I try to start remote sessions.
The following is added to /etc/X11/Xsession just after the
/etc/environment clause:
if [ -x /usr/bin/ssh-agent ] ; then
if [ -z ${SSH_AGENT_PID} ] ; then
exec /usr/bin/ssh-agent $0
fi
fi
Then in your .xsession file, you may
ssh-add
xtoolwait ssh -n remote.host.name xterm -geometry +0-0 +sb +rv -e mutt -y
The ssh-agent process will hold the unencrypted private key in RAM, which
is more difficult for an intruder to read than from disk. The ssh-agent
dies when you log out as well.
This modification to Xsession has been submitted as part of wishlist
#15085 against xbase, but hasn't been acted on yet. The above would
probably also work at the top of a .xsession file, but I haven't tested it.
An alternative is to run ssh-agent and ssh-add from your
.login/.profile files, and save the output (export SSH_*=... lines) to a
temporary file for future sourcing. Email me if you want bash versions
(they're on an offline machine at the moment).
-Drake
--
Dr. Drake Diedrich, Research Officer - Computing, (02)6279-8302
John Curtin School of Medical Research, Australian National University 0200
Replies to other than [EMAIL PROTECTED] will be routed off-planet
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Where is the Local Guide to Latex?
On Thu, 13 Nov 1997, Dale Scheetz wrote: > I have finally decided to learn Latex, so I bought Leslie Lamport's book > and started reading ... but the first suggestion has been difficult to > deal with. He suggests that there is a Local Guide to Latex that I should > read to find out how to use the local implimentation, like how to go from > a .tex document to the printer. I've never seen such a file on any system with Latex. The impression I've gotten is that the sysadmin (you) has to write it. I use three steps to print: latex, dvips, and lpr. dvips without the -f will do the lpr for you. For complex documents with references and labels you sometimes need to run bibtex, and rerun latex once or twice (for references in floating captions to page numbers of other floating figures ...). A makefile rule can simplify the process. Modify as needed. .SUFFIXES: .ps .tex .tex.ps: latex $* bibtex $* if egrep Rerun $*.log ; then latex $* ; fi if egrep Rerun $*.log ; then latex $* ; fi if egrep Rerun $*.log ; then latex $* ; fi dvips -f < $< > $@ The intermediate .dvi file can be made into a separate target as well. This is useful in the final stages of producing a large document, when you're recompiling frequently to look at small formatting changes. -- Dr. Drake Diedrich, Research Officer - Computing, (02)6279-8302 John Curtin School of Medical Research, Australian National University 0200 Replies to other than [EMAIL PROTECTED] will be routed off-planet -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
