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 upgraded my tower that way and had no issues, though I use lilo and not grub, so can't comment on that part.
Yes. That has worked for me as well. The important piece is to edit /etc/slackpkg/slackpkg.conf and set DOWNLOAD_ALL=off to on. This way you download all of the software before you start the upgrade process. The default for Slackware 14.0 is DOWNLOAD_ALL=off.
I will be curious to hear if the upgrade can be done with GRUB.
Kinda? Using slackpkg is an alternate method. UPGRADE.TXT being written by Patrick Volkerding, you can safely consider the method proposed there as recommended
OK, but the how-to referenced by Stuferus was written by Eric H., so while maybe not "official", it can be strongly trusted. It also addresses the issues raised by jtsn about installing and testing the kernel first, upgrading glibc-solibs before other things, etc. Really, you can use slackpkg blindly, or in conjunction with the instructions in UPGRADE.TXT to simply speed the process (like not having to manually uninstall all the removed packages). This seems to be the approach in the referenced how-to, which goes well beyond simply issuing 4 or 5 commands.
i think useing upgrade.txt and slackpkg both is a good way.. i dont want to look (for example) after every single new config file.. that would take a while to long.. so i think ill use slackpkg new-config to speed it up (if its really possible, i only did think about it a short while now).
as i have a serial console connection (nice 15m cable with 9600bps), as my system for example is headless, ill have no problem with singleuser mode - i think..
Lots of people use slackpkg to handle the distro upgrade, including many very experienced users and even members of the Slackware team. It apparently works very nicely for them but as long as UPGRADE.TXT doesn't list it, it is not an official upgrade method.
Just to be clear, that is not a comment on if I personally think it is good or bad.
Distribution: OpenSUSE 13.2 64bit-Gnome on ASUS U52F
Thank you all.
I am all set with SlackWare 14.1. I went with AlienBob's how to. It worked I just skipped the LILO installation and let it proceed. It took all day of running stuff on terminal once it was done I booted on Arch and updated the GRUB from there, then reboot and GRUB had created an entry for SlackWare 14.1.
So all good to go!
Thank you for all advice received, I highly appreciate it.