iraf.net

>From mpolsen@ix.netcom.com Mon Sep 16 20:37:55 1996
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: IRAF installation: Linux platform I tried the command that was suggested "cat ~/nb.* | uncompress | tar
-xpvf -" and also "cat /d0/nb.lnux.x86/nb.* | tar -xvf -". I still get
the "Broken pipe" message. My files are stored in a scratch directory
under /d0/nb.lnux.x86/nb.linux.x86.gz.00 up .gz.25. It seems that it
doesn't recognize them as being compressed. I had no problem putting the
as.gen and ib.linux files together, only the nb's are giving me the
problem.Thanks again,
Mark Polsen>From fitz Mon Sep 16 21:16:18 1996
To: mpolsen@ix.netcom.com
Subject: Re: IRAF installation: Linux platformHi Mark,
Did you verify the checksums on the files, maybe one or another got
corrupted? Does anything unpack at all? I've verified that the files are
from a compressed tar file, I'm not sure what else could be wrong. Did
ftp in binary mode? Did these files come from a CD (ours or "Linux for
Astronomy"?)?Cheers,
-Mike

>From mpolsen@ix.netcom.com Wed Sep 18 12:33:59 1996
To: Mike Fitzpatrick <fitz@noao.edu>
Subject: Re: IRAF on LinuxHi Mike,
I was able to run the install script without any problems. I was bue to
not having the csh shell. My version of slackware did not have csh, only
tcsh. I got csh from an ftp site, I have to link the two though. I still
have to set up a link from /iraf/iraf/bin.linux ->
/iraf/irafbin/bin.linux, this was kind of giving me trouble because the
later already exists. When setting up a user account, does iraf provide
it own window manager or does it utilize an existing window manager? I'm
still kind of new to linux and UNIX based systems, this is for an
undergrad project for school. I hope I'm not getting myself to deep!Thanks again for all your help,
Mark Polsen>From fitz Wed Sep 18 12:51:03 1996
To: mpolsen@ix.netcom.com
Subject: Re: IRAF on LinuxHi Mark,
When you unpacked the as.* source files there should already have
existed a bin.linux link pointing to "../irafbin/bin.linux", by unpacking
the ib.* and nb.* files as suggested these links are automatically resolved
since /iraf/iraf/bin.linux would point to /iraf/irafbin/bin.linux (similarly
for the noao$bin.linux link). You should verify that a 'cd' to
$iraf/bin.linux and $iraf/noao/bin.linux put you in a (different!) binary
directory.> My version of slackware did not have csh, only tcsh. I got csh from an ftp
> site, I have to link the two though.
Tcsh is just an extended csh, simply linking a /bin/csh to tcsh
should work. Linux distributions all differ so this may have been one detail
missing from yours.> When setting up a user account, does iraf provide it own window manager or
> does it utilize an existing window manager?
Strictly speaking IRAF doesn't know you're running under a window
manager, just whether or not the terminal you're using supports graphics.
The iraf user account ($iraf/local) contains some example startup files
but you dont necessarily need to copy these in order to run IRAF. You
linux system may create a default environment when you create the user, these
can be customized later. About all you need to do is put the XGterm and
XImtool binaries in some public place like /usr/local/bin so everyone can
get at them.> I hope I'm not getting myself to deep!
Can you say "abyss" 8-)Cheers,
-Mike