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.

1 members found this post helpful.

I had a laptop which ran well on Slackware 13.1 but when I upgraded to LEET it didn't cope very well (mind you, the 13.6.37.6 kernel had a lot to answer for).

I currently have a netbook with an intel atom processor and 1 GB memory running 32-bit Slackware 14.0 and a PC with 2 GB memory running 64-bit Slackware 14.0. Both work marvelously.

Will they work equally as well if I upgrade to 14.1 or will their resources be tested?

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.

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.

Brian

1 members found this post helpful.

Indeed. Did I say otherwise?

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..

i still would have to look at every one manualy with an edtior wouldnt i? or are you hinting slackpgk new-config will not work?

slackpkg and find command ruario gave you roughly do the same thing. Whatever the method, better have a look at every file if you want to stay in control of your system.

It is fairly easy to knock up a quick for loop to diff the new files to their current version, e.g.

Nope, not at all, slackpkg automates this stuff nicely. I'm just comment that it can fairly easily (IMHO) be done without touching slackpkg if you so desire.

Sorry if I misunderstood the implication of your post. It seemed to me that you were steering him away from slackpkg.

Brian

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.

ok, ruario, understood

slackroll does a pretty good job too. (http://rg3.github.io/slackroll/)

1 members found this post helpful.

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.

1 members found this post helpful.