Article about upgrading to current

rworkman · 05-19-2009, 10:31 PM

I'll paraphrase a statement I made on IRC a moment ago:

You can break a system with slackroll, with swaret, with slapt-get, with slackpkg, and yes, even doing it "by hand" or "manually" or whatever you want to call it. In all but a small minority of cases, the tool is not to blame - it's user error, even if that error was failing to read and/or understand the documentation on how to use the tool properly.

Ultimately, shit will happen. It also happens to fly farther when using tools.

niels.horn · 05-20-2009, 01:30 PM

Quote:

Originally Posted by rworkman

Ultimately, shit will happen. It also happens to fly farther when using tools.

Can I quote you at work?

rworkman · 05-20-2009, 01:49 PM

Quote:

Originally Posted by niels.horn

Can I quote you at work?

Certainly :-)

rg3 · 05-20-2009, 03:59 PM

slackroll was updated today to support Slackware64 too. I just thought this was a good thread to say it.

shadowsnipes · 05-21-2009, 12:16 AM

Robby, you should submit an online upgrade article where you just cat the CHANGES_AND_HINTS.TXT along with UPGRADE.TXT. Just be sure to describe the method of reading as some sort of new fangled-auto-information-download-and-upgrade system (and give the "tool" a catchy name like "upslack"), so that you can be sure you have people's attention. We don't want it to seem too simple.

Thanks again, btw, for providing those original docs.

onebuck · 05-21-2009, 08:04 AM

Hi,

Quote:

Originally Posted by rworkman

<snip>
Ultimately, shit will happen. It also happens to fly farther when using tools.

WOW!

Now that's a utility. Probably will get or gets a lot of use by the authors at Distrowatch.