Upgrade, break the system with a mistake, then install

Hi :-)

Previous Slack13 I always did the new installation, then with Slack13.1 i started to upgrade ... and now I'm using Slackcurrent ...

It's worth noting that slackware is the only distro that has ever upgraded without issues for me and it's done so at least 6 times.

I followed the official instructions and the upgrade went very smoothly. It took a long time though. And the part where I had to diff a bunch of new files in /etc looked bad from a distance, but up close it was actually very educational. Being able to script in bash definitely helps.

I had nothing to loose to try the update from 13.0 to 13.1.
I did it, it didn't work, problème of booting lilo.
So I reinstalled the Slack 13.1 version.

NjB

I have always upgraded, ever since the first and only install on this system -- slackware 8.1. Upgraded all the way through to Slackware 13.1, even during times I didn't have internet access. And the hardware has changed quite a bit too

I usually Upgrade, reinstalled between 12.1 and 13.0, otherwise upgrade on the command line following UPGRADE.TXT (the unix way)

Hi

Said the way up for me I use Slackcurrent, but to do that anyway I have to download all files, which shows the changelog using another PC of a friend who uses windows.

So I download each file and then I take the files using a USB driver and update my Slack using the command:

My question is whether someone will have an idea (some script or something) so
more practice than I do?

If you know someone will let me know ...

Thank you very much :-)

ps: I have no programming knowledge

PS: RESOLVED !!! |--| Boot from cd (or dvd) of a Linux distribution any more ftp server, an HD partition on which Windows is installed (to save files) and ...

I keep a back up mirror and always upgrade.

My case I think is more complicated. I use dial-up and pretty much only use the internet on weekends (Saturday and Sunday).

I use Windows for a friend because he has quick connection and also because I can use the internet during the week ... The connection quickly allows me to download so many files, as large files (when appropriate)

The idea is to use a "species" script on the Windows OS so that allowed me to download
all files at once, and not to download one at a time ... According to changelog ....

My English is horrible, how would the portuques for y'all.

Thanks

PS: RESOLVED !!! |--| Boot from cd (or dvd) of a Linux distribution any more ftp server, an HD partition on which Windows is installed (to save files) and ...

well I have some extra partitions so I did the cowardly thing I installed to one of those extra partitions
I'm glad I did Xorg thought my screen was 800x1280(the text was still right side up) instead of 1280x800 until I copied my /etc/X11/xorg.conf file from my slackware64-13.0 installation

now it's time to let the tweaking begin

I upgraded a production server running 12.0 recently, to 13.1. The UPGRADE.TXT and CHANGES_AND_HINTS.TXT (first from 13.0, then 13.1) provided me with all the required information. Worked like a charm!

Basically, it's just upgrading packages, removing obsolete, installing new, review some config files, (optional - build a new kernel), LILO, reboot.

hehe. Not cowardly. Wise and prudent.

Keep 2 partitions of exactly the same size and you've got a quick, easy and safe way to update, plus when you're not updating you can use the second one to either follow current, or as a emergency backup.

I have taken the same approach in the past, only I use LVM and LVs rather than partitions, but it's the same principle.

Upgrade

For ages I have always preferred a clean install, although I have upgraded in the past when I had smaller HDs. I usually keep Slack on a 20GB partition (have 13.0 and 13.1 installed now and a single /home partition on another drive, with a 500 GB drive for home video, pictures misc data etc that is mirrored to another 500 GB NAS). With over 1 TB of storage its easy to set up multiple installs, tweak, configure and then switch default boot when all the updates are done. Since I try a lot of F/OSS software (curse you, SBo!), all the old unused cruft fall away.