SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
If pkgtool does not locate the directory or any packages available in the directory specified then it terminates after entering the directory name. It is probably better and easier to change to the directory desired and run pkgtool from that location. You also have the opportunity to view what packages are actually available before installing.
Slack packages use the the ".tgz" extension. "tar.gz" are just gzipped tar files. Use the "tar" command to extract them.
tar -xzvf the_file_name.tar.gz
These are usually source distributions and will require building prior to installation. But read the README and INSTALL files first to determine what is required. For instance, I know Opera is not source distributed, but binary only. After it is extracted you would just run ./install.sh to install it. For source distributions, then usually it starts with something like the following:
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
<slightly off topic>
Ahem. There is no requirement that any files use any extension.
While it's true that pkgtool looks for files that are named with a .tgz
extension, that's a mistake that should be easy to fix (I'm working on a
patch right now).
It's starting to sound like I'm a nutcase when it comes to filenames, but
UNIX does not limit your file names, thus you cannot rely on the file
name to tell you what is contained within, but you CAN rely on the
magic number within the file to tell you what it contains.
If these files are in fact tarballs, you can do:
file -z filename.tar.gz
and it will return something like:
GNU tar archive (gzip compressed data). . .
</slightly off topic>
Regardless of whether the tarballs are slackpacks, you can do as
Excalibur says, which is decompress and unarchive them by using
tar xzvf filename.tar.gz. If this is a slackpack, there will be a directory
called "install" when you unwrap it. Until my patch is done, you can just
rename the .tar.gz to .tgz and pkgtool will be able to handle it.
Otherwise, it's jut a bunch of files that someone thought were important
enough to put together in a tarball.