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.
I just installed slackpkg on my system and was wondering how to upgrade my system with it. I tried "slackpkg update" then "slackpkg upgrade" but nothing happened. So I am assuming that I can only do a "slackpkg upgrade package" but I was expecting it to be able to do something like "slackpkg upgrade" to upgrade the whole system much like swaret has. Can anyone that use's slackpkg give me some tips on how they upgrade their system with it. And also if I am doing something wrong. Thanks
I'd just advice you to use swaret or slapt-get. Slackpkg seems not to have that functionallity to upgrade your whole system.
Though I'd like to warn you as well, upgrading you system with this kind of package tools isn't without risk. It can happen that you'll have to install or repare things afterwards.
There is a tread about it from about a month ago on this forum, try looking there before performing an upgrade.
Namaseit I did read all the docs and found them kind of lacking in information but put it down to myself maybe not understanding them or over estimating slackpkg. I also did a search on slackpkg in these forums and did not come up with anything. I guess what I really want to know is how did people upgrade their systems before swaret, slapt-get and slackpkg as I dont particularly want to use swaret, slapt-get? So is there another way. Thank you both for your replies.
. I guess what I really want to know is how did people upgrade their systems before swaret
We got the tarball ourselves and from the CLI we did a.......upgradepkg <file>
Actually I don't understand why some people use linux at all.
swaret, apt-get, wget, portage -------these progs are the M$ equivilent to
windows update!! Most of us use LINUX because we like to do things for ourselves and not to have our hands held like with M$...........with progs like the above mentioned, people revert back to the same old windows behavior..........
Originally posted by 320mb Most of us use LINUX because we like to do things for ourselves and not to have our hands held like with M$...........with progs like the above mentioned, people revert back to the same old windows behavior
Wrong, most of us don't use LINUX because we like to do things for ourselves, most of us want to be able to choose between automated things or doing it ourselves. Also people like the fact that most software for Linux is free, that they can check out its source. People like the fact that not everything is covered up and secret, that they don't constantly have to choose between empty pockets or stolen software...
That's what drives people, and why did you say
Let the flames begin.......LOL
since you think most Linux users support your message.
One of the great things about Linux (in all its forms) is the variety it brings, if you want a tool to upgrade your system, well there is one and if you don't want one, well then don't use it. Nobody says you have to use swaret or do they?
(let's ignore the "why people use linux flamewar and get back to the question...)
Originally posted by _mu_ Hi again,
...<snip> I guess what I really want to know is how did people upgrade their systems before swaret, slapt-get and slackpkg as I dont particularly want to use swaret, slapt-get? So is there another way. Thank you both
for your replies.
There are two ways to handle this. And it all depends on the package you are adding/updating. First stop is the Packages link off of Slackware (http://www.slackware.com/pb). You can search the packages to see the current version. It will not likely be the lastest, but its often very close. if the package is there, download it. Run installpkg or upgradepkg (see the book for details ( http://www.slackware.com/book/index....rce=x4000.html> ) These tools work well if a package was made available.
The other way is to download the source from the author and compile it. The package will come with detailed instructions for doing so. I'd never done this before last month, but I was faced with needing a custom compiled sendmail for my needs. I walked through the process and was quite successful.
One thing I found is searching for someones notes is a good idea. i found a log from a guy who had walked throug the sendmail compile process and they gave me confidence (and additional guidance) to do so.
And my one rule - Read everything before doing anything. This ain't windows...
Originally posted by gmartin ... And my one rule - Read everything before doing anything. This ain't windows...
I can agree with this, though when it is just compiling something, it is often enough just to read the quick install instructions (something like ./configure, make,... These are almost everytime in the INSTALL file).
Another thing you'd might use is checkinstall, this can be run instead of 'make install' to make a slack package, so you can remove it more easily using your 'removepkg'.
(And about those flames, it was to hard to resist )