I am highly amused this morning by this wallaper found onKDE-look.org. Even though it’s just an attempt at humor, I can definetly agree with his sentiments.
To show you a quick thumbnail. I think it’s brilliant, I might drop a note back to the author and ask if he can also make a nice 1280×1024 sized one.
Still, I might make this my wallpaper for a while, just for a laugh ;)
I have been “away”-ish for a couple of days mostly because I tried to be smart and it kind of backfired horribly. One of those things that you think you can do but nope, something goes wrong.
Ok the deal was this:
With slackware current most of the programs are installed in /usr (mainly the big X11 and KDE), this leaves much room in /opt which will not be used. So the plan is to actually move some things around using multitude of mv/cp/mounnt and partition-funess. The dangerous part here is hat you could technically hose the whole box. Would that happen, reinstalling verything from scratch would be the only solution in that case [1]. Anyway: My current partition scheme (for /dev/hda) looks like follows:
I am gonna shamelessly plug some content here for a change…
As I wrote in my previous blog upgrading to slackware-current using automated pkgtools, other than slackpkg is just plain silly. I don’t care how much you think it’s done wonders for you over the past and it never let you down before.
Because of the way that slackware-current is setup and with the many changes to both KDE and Xorg, the new glibc and all, upgrading is to be done in a certain way following tested and proven steps. In other words, follow the CHANGES_AND_HINTS.TXT. Yes I may sound like a bit of a broken record, but I can’t stress it enough.
Rworkman has graciously supplied those who are stubborn uhm not wise in this way an HOWTO on how to rescue your system from the mess you created in the first place.
To quote his original posting on Linuxquestions:
DISCLAIMER: This is not intended to be a *complete* guide to cover all possible ways that one can botch an upgrade - rather, it is intended to cover one of the most frequent problems that people encounter when upgrading from one release of Slackware to another (or more recently, from the latest stable release to -current).
If you've failed to read UPGRADE.TXT / CHANGES_AND_HINTS.TXT before attempting an upgrade to Slackware -current, you possibly/probably wound up with errors about GLIBC stuff not found or "kernel too old" and such. This document should help you (mostly) return your system to its previous state so you can start over and do the upgrade correctly.
anyway, please have a look at his glibc-recovery HOWTO if you have hosed your system using slapt-get/swaret.
Please note: This HOWTO is in no way shape or form my doing. I am only plugging it for peoples sake. All credit goes to rworkman.
