ADL: Unpacking (autodock).tar.tar
jackygrahamez at gmail.com
Sun Nov 4 08:39:36 PST 2007
You could do whatever you like, but I like to put my source in my /usr/src
I don't like cluttering my home directory. I never broke my server
while doing that. I found other ways to break it.
tar xvf works for me without problems but you can do xzf or xvzf makes
no diffrence in my experience or maybe do gunzip before tar whatever.
On 11/4/07, Daniel Jana <dfjana at gmail.com> wrote:
> Hello Jack, Martin!
> Jack Shultz wrote:
> > For 32 bit linux make sure you are downloading Linux: RedHat
> > (32-bit)<http://autodock.scripps.edu/downloads/autodock-registration/tars/dist401/autodocksuite-4.0.1-i86Linux2.tar.gz>
> > http://autodock.scripps.edu/downloads/autodock-registration/tars/dist401/autodocksuite-4.0.1-i86Linux2.tar.gz
> > 1) Try downloading it to the /usr/src directory
> I am sorry but I have to disagree. As a regular user you have your own
> home directory (usually located under /home). This is where you should
> download the file to. It's up to you the place where you put it but I
> usually create a folder called software under my home directory and I
> put all the files I download there. That way, if you need to find some
> info about the software you downloaded you know where it is.
> I don't really see the point of downloading to /usr/src, the place where
> are the sources of the kernel among other things, so you should avoid
> (even the remote) possibility of tampering with them. Besides, to save a
> file in the /usr/src you need to either download it as root, the folder
> has permissions only for root at least in the majority of distributions,
> or change the permissions of that folder so that anyone can use it. The
> /usr folder in Linux is partially the same as the C:\Windows folder. You
> do not want to put things there by yourself, let the computer do that
> job for you.
> > 3) unpacking with tar xvf autodocksuite-4.0.1-i86Linux2.tar.gz, if you are
> > unable to unpack try running it with sudo xvf
> > autodocksuite-4.0.1-i86Linux2.tar.gz
> It seems to me that Martin was using a graphical program to do that job
> for him. If the idea is to do it in the command line the command is:
> tar xzf autodocksuite-4.0.1-i86Linux2.tar.gz
> and not xvf. tar is the name of the program followed by some options.
> The ones that matter in this case are:
> x - for extract
> z - for a gzipped file
> f - for a file in a computer (instead of a tape, which was the first use
> of the tar [Tape ARchive] program.
> v - (which is optional) for verbose, to tell you the names and locations
> of the extracted files.
> If that does not work then a 'sudo tar xzf
> autodocksuite-4.0.1-i86Linux2.tar.gz' is not the right way to go. Tar is
> available as a program for all users (root and everyone else with less
> privileges). If you cannot extract due to a permission denied then you
> are doing it in the wrong folder. You should do it, I repeat, under your
> home directory.
> > If that does not work run as root, or add sudo permissions or chmod the
> > ownership on the directories and files to give you execute.
> If the extraction procedure cannot be done under a regular user, either
> the folder isn't a good option (protected from writing by the current
> user) or the file is damaged. If it is damaged, then re-download.
> > If all else fails try compiling it. Autodock source is fairly easy to
> > compile unless you want to do something special.
> > 1) cd to the autodock source directory,
> > 2) ./configure
> > 3) make
> > 4) make install
> Yes, in a regular Linux system, you should have no problems with this
> but, in order to compile you just have to go through all the previous
> steps as the source comes in a tar.gz file too.
> Best luck with that,
> --- ADL: AutoDock List --- http://autodock.scripps.edu/mailing_list ---
More information about the autodock