[Lilux-help] Slackware upgrade from 10.0 to 10.1

[Patrick Useldinger]

Patrick Kaell wrote:

> I do not know your girlfriend. But isn't keeping config files in the 
> home directory enough? If you have a separate /home directory everything 
> is kept during a fresh install. Or did she manipulate /etc files?

I hope not ;-)
You're right, the /home backup should be sufficient.

> 1. OS updates costs (Panther: 150 Euro) and happen very often (almost 
> yearly)

Convenience comes at a cost, as usual. An Apple computer is always the 
most expensive solution, IMO more expensive than a Windows system.

> 2. If you do not update (ie save 150 Euro/year), Apples let you in the 
> rain. I still get security updates for Jaguar, but many new things only 
> run on Panther.

That's normal procedure, also with other systems, SuSE for example.

> 3. Apple omitted MacOS classic when releasing Panther. This means that 
> you are no more compatible with the pre-2001 Mac world. Many people 
> protested and Apple had to reconsider MacOS classic for Panther.

Which is not a problem for me... DID Apple bring support for MacOS 
Classic in 10.3?

> This is still gpart... Just kidding. But backing up /etc on the same 
> disk is no better ;-) The backup must be on a separate disk if you want 
> to go for sure.

As I said, there's basically no risk with Slackware. I'd do a backup on 
DVD or another system if I had to face some automatic update system that 
I cannot control.

>> like tripwire in order to monitor exactly what changed. Next time.
> Modification dates on files should normally be enough. Only hackers make 
> sure that modification dates stay unchanged after changing a file.

There's always cp -p. Tripwire is an 100% certain solution, I like 
those. It might also spot more subtle issues like chmods, chowns or 
whatever.

> We all know that Patrick Volkerding needed the money to pay his bills 
> (and medical treatment) ;-) I was surprised to hear that Slackware is 
> his only income.

And it's OK if we can help now that he needs it. It just means that we 
*might* expect issues.

> Thanks. Hope that the lock up doesn't happen again!

I knew Linux was boring...

Regards,
-pu