LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-21-2012, 05:43 AM   #1
Cayitano
LQ Newbie
 
Registered: Aug 2006
Location: Seattle, North America
Distribution: Slackware
Posts: 10

Rep: Reputation: 0
Pkg Download, Installment


p, li { white-space: pre-wrap; } I believe Linux folks can do better than this in explaining how to make Linux useful. From page 218 Chapter 18 Slackware Essentials followed by my attempts. (Most of the last 12 hours has been spent looking for an answer)



"# installpkg option package_name"



bash-4.1# installpkg -r opera
Cannot install -r: file not found
Cannot install opera: file not found
bash-4.1# installpkg -r /home/opera
Cannot install -r: file not found
Cannot install /home/opera: file not found
bash-4.1# installpkg -r /root/home/opera
Cannot install -r: file not found
Cannot install /root/home/opera: file not found
bash-4.1# installpkg -r opera-11.64-1403.i386.linux
Cannot install -r: file not found
Cannot install opera-11.64-1403.i386.linux: file not found
bash-4.1# installpkg -m opera-11.64-1403.i386.linux
Cannot install -m: file not found
Cannot install opera-11.64-1403.i386.linux: file not found
bash-4.1# installpkg -r /home/opera-11.64-1403.i386.linux
Cannot install -r: file not found
Cannot install /home/opera-11.64-1403.i386.linux: file not found
bash-4.1# installpkg -r file:///root/opera-11.64-1403.i386.linux.tar.xz
Cannot install -r: file not found
Cannot install file:///root/opera-11.64-1403.i386.linux.tar.xz: file not found
bash-4.1# installpkg /home/opera*
Cannot install /home/opera*: file not found
bash-4.1# installpkg /home/opera-11.64-11403.i386.linux.tar.xz
Cannot install /home/opera-11.64-11403.i386.linux.tar.xz: file not found
bash-4.1# installpkg /root/home/opera-11.64*
Cannot install /root/home/opera-11.64*: file not found
bash-4.1# installpkg /media/S13.37d6
Cannot install /media/S13.37d6: file not found
bash-4.1# installpkg /dev/sr0/media/S13.37d6
Cannot install /dev/sr0/media/S13.37d6: file not found
bash-4.1# installpkg /tempus/fugit



I do not know what happened to Chrome after I downloaded it, but I did find these three files in Home and I would like to know how to install them. Then I would like to install Slack's 13.37's Disks 5 & 6 which I purchased from Slackware along with the two Linux books. I could not find any answers in Linux: The Complete Reference either.




opera-11.64-1403.i386.linux.tar.xz
install_flash_player_11_linux.i386.tar.gz
firefox-12.0.tar.bz2


Patronizing advice will be ignored.
 
Old 05-21-2012, 06:31 AM   #2
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,048

Rep: Reputation: Disabled
Well,
1) there are no -r or -m options for installpkg at present
2) the package name should be the full name of a Slackware package (usually ending in .tgz or .txz) and *not* a source tarball or an abbreviated name and should refer to a mounted directory (not to something in the /dev tree)
3) if the package in question is not in the working directory, the package name should include its full path.
To know more, type "man installpkg" in a terminal.
HTH

EDIT None of the 3 files you mentionned at the end of your post is a "Slackware package", they seem to be what is called a "source tarball" which can't be installed directly : first step should be to make (or build) a package of it. You will find instructions for that here.

The files provided in disks 5 & 6 are "source packages" (or tarballs) that you can't install as such. They are provided only to allow you to (edit the souce files in it if needed then) rebuild a package using the Slackbuilds provided as well.

Last edited by unSpawn; 05-30-2012 at 05:24 PM. Reason: //Edited for Didier Spaier after 5 day edit limit
 
Old 05-21-2012, 10:18 AM   #3
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; Slackware64-current (VM); Debian 12 (VM)
Posts: 8,290
Blog Entries: 61

Rep: Reputation: Disabled
Read the SlackBuild HOWTO. (Hope that's not too patronising for you.)
http://slackbuilds.org/repository/13.37/network/opera/
 
Old 05-21-2012, 10:31 AM   #4
ttk
Senior Member
 
Registered: May 2012
Location: Sebastopol, CA
Distribution: Slackware64
Posts: 1,038
Blog Entries: 27

Rep: Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484Reputation: 1484
Quote:
Originally Posted by Cayitano View Post
opera-11.64-1403.i386.linux.tar.xz
install_flash_player_11_linux.i386.tar.gz
firefox-12.0.tar.bz2
[/FONT][/COLOR]
Elaborating a bit on Didier's reply, regarding these three package files:

You need to determine, first, the full pathnames of the files. If you see them when you run "ls", then you can make their full pathnames by taking the output of "pwd" (for instance, "/root") and the files' names. If they are in "/root", then your installpkg commands would look like this:

installpkg /root/opera-11.64-1403.i386.linux.tar.xz
installpkg /root/install_flash_player_11_linux.i386.tar.gz
installpkg /root/firefox-12.0.tar.bz2

an easy way to make sure you have the correct pathnames of the files is to invoke "ls" on the pathnames, like so:

ls /root/opera-11.64-1403.i386.linux.tar.xz

If it says "No such file or directory", then the file is not in "/root" and you need to hunt around for it. If, instead, it shows you the pathname you typed in, then that's the right pathname to pass to installpkg.

To see the full pathnames of all of the files in your current directory, you can use the backtick ` around pwd to pass its output as a parameter to ls, like so (be mindful of the whitespace; there must be none between `pwd` and "/*"):

ls -ld `pwd`/*

Good luck :-) let us know how it goes!
-- TTK
 
Old 05-21-2012, 05:36 PM   #5
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,557

Rep: Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761
The packages you appear to be trying to install are not a native Slackware packages and hence cannot be installed in that way. To avoid further confusion it might be easier just to use native packages. It looks like you run 32-Bit Slackware.

For Opera download: opera-11.64-i686-1ro.txz, then install with:

Code:
installpkg opera-11.64-i686-1ro.txz
For Firefox download: mozilla-firefox-12.0-i486-1_slack13.37.txz, then install with:

Code:
upgradepkg --install-new mozilla-firefox-12.0-i486-1_slack13.37.txz
(Note: I use "upgradepkg --install-new" here because if you did a full install it is likely you already have an older version of Firefox installed already)

For Flash download: flashplayer-plugin-11.2.202.235-i386-1alien.txz, then install with:

Code:
installpkg flashplayer-plugin-11.2.202.235-i386-1alien.txz

Last edited by ruario; 05-21-2012 at 05:41 PM. Reason: changed the Firefox command to use upgradepkg
 
Old 05-21-2012, 08:06 PM   #6
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 19,272
Blog Entries: 28

Rep: Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124Reputation: 6124
The Slackbook will give you an overview of Slackware Package Management. http://www.slackbook.org/html/book.h...AGE-MANAGEMENT

Slackware does not handle software installation like any other distro. It does not resolve dependencies and it does not attempt to have a wide variety of "optional" packages in the official repos. Slackware's included software also tends to be a little behind the bleeding edge, because stability is a core Slackware feature.

For many of us, Slackbuilds.org is the go-to source for "unofficial" packages, but we still have to resolve dependencies.

As regards Opera, I have had good results downloading the *.tar.gz file from the Opera site, decompressing it, and running the install script which is included in the tarball. Indeed, in seven years of Slacking, that method has never failed me. But ruario is the Opera expert around here and I defer to him in all things Opera.

Last edited by frankbell; 05-21-2012 at 08:09 PM.
 
Old 05-22-2012, 12:37 AM   #7
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,557

Rep: Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761
Quote:
Originally Posted by frankbell View Post
As regards Opera, I have had good results downloading the *.tar.gz file from the Opera site, decompressing it, and running the install script which is included in the tarball. Indeed, in seven years of Slacking, that method has never failed me. But ruario is the Opera expert around here and I defer to him in all things Opera.
Indeed that works just fine (on pretty much any distro). However since the OP appears to be relatively new to Slackware I thought it might be better for him to focus on understanding installation of native packages first and worry about non-native packages later. Hence why I provided the links.
 
Old 05-29-2012, 03:00 AM   #8
Cayitano
LQ Newbie
 
Registered: Aug 2006
Location: Seattle, North America
Distribution: Slackware
Posts: 10

Original Poster
Rep: Reputation: 0
I went to Slackbuild's FAQ.

How do I extract a package like it says to do in Step 1 HOW TO? And when I download a package which is the better deal: Save file or Open browse? (I googled the string, ""how to extract" Slackbuild pkg," and a little over 200,000 hits came up in under 0.4 seconds telling me something about .rar.)

Intuitively, the decision would be based for me on how much I have muddled the original Slack installment so I would trust it and go to "Save File." Based on what I have read here, I could assume that if I were in "root" then the working directory (root) is where I would find the file location after it downloaded.

By the way, Linux Commands by CheapBytes helped me understand pwd & ls a little better, so I got to thinking, "Does the explanation process for learning Linux via texts' Table of Contents and the command line follow the tree protocol or format of device, directory, folder, file, sub-file etc also to provide a dependable pattern for understanding?" (e.g. /root in the Table of Contents would be a chapter to explain what "kernel" means.)

Anyway, I stumbled onto http://commondatastorage.googleapis....25.142.tar.bz2 and copied it in the URL bar like the HOW TO instructed. It downloaded and I replaced the identical one already in /root/Home, but it has 0 bytes and the new one reads ...gz.part and is increasing in Megabytes as I type. Chromium.tar.gz did not seem to work. OK, something popped up and had "Activate" on it so I clicked it just now. It reads 166MB and the file which read 0 bytes disappeared.

Let's see. This is what I have to show for trying to download and install Chrome.

bash-4.1# ls ./root
Desktop chromium.tar.gz flashplayer-plugin-11.2.202.235-i386-1alien.txz opera-11.64-1403.i386.linux opera.tar.gz
Opera-Background-Clouds2.jpg firefox install_flash_player_11_linux.i386.tar.gz opera-11.64-1403.i386.linux.tar.xz
chromium-18.0.1025.142.tar.bz2 firefox-12.0.tar.bz2 mozilla-firefox-12.0-i486-1_slack13.37.txz opera-11.64-i686-1ro.txz
bash-4.1# installpkg /root/chromium-18.0.1025.142.tar.bz2
Cannot install /root/chromium-18.0.1025.142.tar.bz2: file does not end in .tgz, .tbz, .tlz, or .txz
bash-4.1# installpkg chmod +x chromium-18.0.1025.142.tar.bz2
Cannot install chmod: file not found
Cannot install +x: file not found
Cannot install chromium-18.0.1025.142.tar.bz2: file not found
bash-4.1# installpkg ./root/Home/chromium-18.0.1025.142.tar.bz
Cannot install ./root/Home/chromium-18.0.1025.142.tar.bz: file not found
bash-4.1# installpkg chromium-18.0.1025.142.tar.bz2
Cannot install chromium-18.0.1025.142.tar.bz2: file not found
bash-4.1# installpkg /root/please.dont.laugh.because.my.brain.hurts&will.try.to.go.over.this.again.
 
Old 05-29-2012, 03:07 AM   #9
Cayitano
LQ Newbie
 
Registered: Aug 2006
Location: Seattle, North America
Distribution: Slackware
Posts: 10

Original Poster
Rep: Reputation: 0
Thanks for the heads up. This is the site which makes more sense than the other one which had only builds for 64bit systems I found. My learning skills are more kinesthetic than abstract so I would climb the tree to find my relatives or creep out into the intersection at the red light of hope which never changes and gamble the blondes at the other three lights facing me would not copy my movements.
 
Old 05-29-2012, 03:16 AM   #10
Cayitano
LQ Newbie
 
Registered: Aug 2006
Location: Seattle, North America
Distribution: Slackware
Posts: 10

Original Poster
Rep: Reputation: 0
It is pretty slick how you got to the packages, Ruario, and I will be working some more on reverse "engineering" how you got to them to make it so easy to install Opera, the Firefox update (could not find FireFox in the Slackbuild site above BrianL focused me on), and the FireFox plugin. I will be going over what everyone here has shared to see how it works. Thanks Didier, brianL, ttk, ruario, and Mr. Bell. I found a local meetup last week and those who appeared made me feel comfortable I could learn Linux from scratch. There is another meetup.com group I hope to find and attend named SLUG. The bar is closing, the menudo was good, and with an Argentina cowboy yell, goodnight.
 
Old 05-29-2012, 03:27 AM   #11
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,557

Rep: Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761
Quote:
Originally Posted by Cayitano View Post
bash-4.1# installpkg /root/chromium-18.0.1025.142.tar.bz2
Cannot install /root/chromium-18.0.1025.142.tar.bz2: file does not end in .tgz, .tbz, .tlz, or .txz
bash-4.1# installpkg chmod +x chromium-18.0.1025.142.tar.bz2
Cannot install chmod: file not found
Cannot install +x: file not found
Cannot install chromium-18.0.1025.142.tar.bz2: file not found
bash-4.1# installpkg ./root/Home/chromium-18.0.1025.142.tar.bz
Cannot install ./root/Home/chromium-18.0.1025.142.tar.bz: file not found
bash-4.1# installpkg chromium-18.0.1025.142.tar.bz2
Cannot install chromium-18.0.1025.142.tar.bz2: file not found
bash-4.1# installpkg /root/please.dont.laugh.because.my.brain.hurts&will.try.to.go.over.this.again.

You are making the exact same mistake as you made last time. Not every file you download is a Slackware package. In the same way not every file you download is a Windows program or a Word document. Why did you think that chromium-18.0.1025.142.tar.bz2 is something you could install with installpkg? It isn't a Slackware package and you cannot install it this way.

If I were you, I would therefore start with the assumption that most random files you find are not Slackware packages. As a general rule Slackware packages tend to end with .tgz or .txz. It is also possible but relatively unlikely that they may end with the extensions .tbz and .tlz. The error message your received should have given you this clue, it stated "file does not end in .tgz, .tbz, .tlz, or .txz". Thus implying that it should have one of these extensions to be a Slackware package.

However even then, I think it is worth pointing out that not every single .tgz, .txz, .tbz or .tlz is a Slackware package. Unless you got them from a site that specifically mentions Slackware or another Slackware user pointed you to them, you should still assume they are not Slackware packages. I can also say with certainty that files that end with .tar, .tar.gz, .tar.xz, .tar.bz2 or .tar.lzma are never native Slackware packages and hence will never install with installpkg.

The best way to get Chromium would be to compile it from source using a SlackBuild script. However, at this stage (with no intended disrespect) I would personally advise you not to bother as I am fairly certain it is beyond your current level (though probably not your future level! ), given you have not yet even understood what a Slackware package is and using SlackBuilds is more complex than using binary packages. Given that you (apparently) have Firefox and Opera installed stick with one of them for now, whilst you better familiarise yourself with your new Operating System. Later when everything starts to make more sense you can consider installing Chromium.

Last edited by ruario; 05-29-2012 at 04:43 AM. Reason: added quote, trie dto be less condescending ;)
 
Old 05-29-2012, 04:03 AM   #12
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,557

Rep: Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761
Ah what the hell, I'll give you a quick run down on how to get (actually how to create) a Chromium Slackware package that you can install. Though personally I would still advise you to wait a bit before you went down this route. If the steps don't make sense to you then it probably means you are not ready yet. It would be better to come back to this when you understand the underlying concepts. If I am wrong and it seems to make sense to you, proceed right ahead.

The Chromium package you downloaded early is the "source" package for Chromium, which is different than a "Slackware" package. It would have to be built into a Slackware package before it could be installed with installpkg. However, as it states on the Chromium SlackBuilds page, Chromium requires (depends on) a package called libevent. For this reason libevent itself is also needs to be built first and installed before you can install Chromium.

To install libevent grab the relevant SlackBuild package and the source package:

Code:
cd /tmp
wget http://slackbuilds.org/slackbuilds/13.37/libraries/libevent.tar.gz
tar xf libevent.tar.gz
cd libevent
wget http://www.monkey.org/~provos/libevent-2.0.10-stable.tar.gz
Now switch to root via the su command:

Code:
su -
Now build the Slackware package:

Code:
cd /tmp/libevent
./libevent.SlackBuild
If this completed correctly then the line "Slackware package /tmp/libevent-2.0.10-i486-1_SBo.tgz created." would be printed and you could install the libevent Slackware package with the command:

Code:
installpkg /tmp/libevent-2.0.10-i486-1_SBo.tgz
Only once libevent is successfully installed you could then build the Chromium package and install it as follows:

Code:
cd /tmp
wget http://slackbuilds.org/slackbuilds/13.37/network/chromium.tar.gz
tar xf chromium.tar.gz
cd chromium
wget http://commondatastorage.googleapis.com/chromium-browser-official/chromium-18.0.1025.142.tar.bz2
If you are not already/still root, switch to root via the su command:

Code:
su -
Now build the Slackware package:

Code:
cd /tmp/chromium
./chromium.SlackBuild
If this completed correctly then the line "Slackware package /tmp/chromium-18.0.1025.142-i486-1_SBo.tgz created." would be printed and you could install the libevent Slackware package with the command:

Code:
installpkg /tmp/chromium-18.0.1025.142-i486-1_SBo.tgz
Now (hopefully) you have Chromium installed. There are plenty of things that could have gone wrong however (like not having development tools installed, thus preventing package building)! If you get any error along the way, stop and post back here. Some kind soul might help you.

Last edited by ruario; 05-29-2012 at 03:26 PM. Reason: switched examples to use: su -
 
Old 05-29-2012, 04:23 AM   #13
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,557

Rep: Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761
Quote:
Originally Posted by Cayitano View Post
It is pretty slick how you got to the packages, Ruario, and I will be working some more on reverse "engineering" how you got to them
I can tell you right now how I got to them.

The Firefox package was easy to find because Slackware includes Firefox, so any updates will be found in the "patches" directory on any of the Slackware mirrors. This is true for any other Slackware software that has security updates (they would be found in the same directory).

The Flash Plugin is not included in Slackware. These days the next port of call when looking for packages that aren't found in Slackware's own repository is http://www.slackbuilds.org/ (a.k.a SBo). However SBo does not host Slackware packages directly, rather it hosts SlackBuild scripts that create Slackware packages from "source" packages. Since using these scripts are more complex than using Slackware packages directly I decided not to give you to the link to the SlackBuild Flash Plugin page at that stage as it involved a little more work and explanation. Instead I looked in Eric Hameleers's package repository. Eric is a Slackware contributor and also maintains that nice repository of binary packages and SlackBuild scripts. His (binary) Slackware packages are trusted by the community and often more convenient (since no building is required). Hence I linked to his package.

For Opera, again SBo has a SlackBuild script. However, like with the Flash Plugin it would have been more complex to get you to use this to make your own package. Instead I linked to an Opera package I made myself. I work for Opera and host unofficial Opera Slackware packages as a convenience to Slackware users. Thus it wasn't that hard to find that one.
 
Old 05-29-2012, 05:00 AM   #14
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,557

Rep: Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761Reputation: 1761
Quote:
Originally Posted by Didier Spaier View Post
2) the package name should be the full name of a Slackware package (usually ending in tar.gz or tar .xz) and *not* a source tarball or an abbreviated name and should refer to a mounted directory (not to something in the /dev tree)
Pretty sure you meant usually ending in tgz or txz. I have never known a native Slackware package to end .tar.gz or .tar.xz. Unless the package ends with .tgz, .txz, .tbz or .tlz installpkg will return an error message stating, "Cannot install $package: file does not end in .tgz, .tbz, .tlz, or .txz".

Quote:
Originally Posted by ttk View Post
your installpkg commands would look like this:

installpkg /root/opera-11.64-1403.i386.linux.tar.xz
installpkg /root/install_flash_player_11_linux.i386.tar.gz
installpkg /root/firefox-12.0.tar.bz2
These will all fail as they are not Slackware packages. Look at the endings. No Slackware packages end with .tar.xz, .tar.gz or .tar.bz2.

P.S. Whilst it doesn't have to be the case, "source" packages almost never use .tgz, .tbz, .tlz, or .txz but rather the long endings (.tar.gz, .tar.bz2, .tar.lzma, .tar.xz, etc.). So if a file is listed as being a Linux package and it has a long ending there is a fairly good chance it is a "source" package (an exception being ArchLinux and Crux packages, which end with either .pkg.tar.gz or .pkg.tar.xz).

Last edited by ruario; 05-29-2012 at 05:19 AM. Reason: added more comments about extentions
 
Old 05-29-2012, 05:53 AM   #15
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,048

Rep: Reputation: Disabled
Quote:
Originally Posted by ruario View Post
Pretty sure you meant usually ending in tgz or txz. I have never known a native Slackware package to end .tar.gz or .tar.xz. Unless the package ends with .tgz, .txz, .tbz or .tlz installpkg will return an error message stating, "Cannot install $package: file does not end in .tgz, .tbz, .tlz, or .txz"..
Of course you are right, shame on me. I'll edit my previous post.

EDIT For some reason I don't see the "Edit" button on that post thus I can't correct it.

EDIT2 It seems that my previous post was too old to be edited by myself; hopefully a moderator nicely did it for me - thanks unSpawn

Last edited by Didier Spaier; 05-31-2012 at 02:49 AM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
how to download multiple pkg using yum in parallel centos123 Linux - Server 5 02-01-2012 12:39 AM
where to download the pkg and to install veeraalin Solaris / OpenSolaris 1 06-17-2005 03:13 AM
buffalo WLI-USB-L11G-WR installment Darkrazor Slackware 3 04-30-2005 09:08 AM
Q-mail Installment help ®åD\° Linux - Software 1 09-10-2004 07:23 AM
can't download pkg-config?...newer version needed... breezewax Linux - Software 1 09-06-2004 10:07 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:00 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration