Today I’ve read the post on sidux forum in which the poster asks for helping him with the confusion around upgrading procedure while maintaining distro up-to-date.

 

I think it can be most common problem – especially for people new to sidux and/ or to Linux. “To ease their pain” 😉 I would like to share my way of doing things – with the hope it could help.

 

So – here are some hints/ tips for let’s say – “sidux newcomers”:

 

1. At least in my case I am doing dist-upgrade everyday. To be on the safe side I type in terminal (as root, of course):

 

~ apt-get update && apt-get dist-upgrade -d

 

Notice especially this -d at the end – it means that apt-get will check for upgrades and download all of them.

 

But then it will stop until you will not repeat command dist-upgrade without -d.

 

This is very useful because you have the time to take a look if apt-get “would not like to” remove something important from your computer.

 

If this is the case move to point 2a.

 

If not you can safely move to point 2b.

 

2a. If apt-get “wants” to remove some packages I turn to sidux web page in particular:

 

sidux news

 

AND!

 

sidux forum – here I check All the news about sidux and Upgrade Warnings (EN & DE). And either somebody else has noticed before you that apt-get is “in the vicious humor” or you can open your thread asking how to behave.

 

All in all it’s the time to wait for the help from our fantastic devs.

 

Now – as you probably know – you should ALWAYS do dist-upgrade in console and in init 3!

 

 

The easiest way to remember all of the important steps is to simply use magical script by our “saviour” 😉 h2.

 

Just in case you did not find this amazing tool, here’s the link:

 

du-fixes-h2.sh

 

and here’s the link to the thread about h2’s script on sidux forum:

 

du-fixes script: information and updates

 

and thus we are coming to the easiest part – using script of h2:

 

 

 

2b. Once again – you should always make dist-upgrade in console and in init 3 mode. To make it correctly while being in GUI (Graphical User Interface) press Ctrl+Alt+F1, than while in the console (black screen 😉 ) log in as the root and just to be on the safe side type:

 

~ init 3

 

(the script will do this for you…but – the best thing is to take care yourself, isn’t it? 😉 )

 

than – after installing “scripten” ;), of course – type:

 

~ du-fixes-h2.sh

 

…and the magic begins – script usually takes care of most “rocks” on the sid path…

 

Check yourself!

 

 

Disclaimer I: this howto is aimed to real newcomers – so, please do not be annoyed by very detailed instructions I tried to give here.

 

Disclaimer II: If you are new to all of this – do not be afraid and do not give up –

 

I were as you are now just ca. 1 year ago…

 

I hope it will be of a use and help.

 

tami:)

EDIT: du-fixes-h2.sh has changed name lately to sm! Despite this – script works as well as before 😉

EDIT2: sm has changed the name to smxi – still working as the charm! 

 

Advertisements