take the plunge!!!

Hi,

Just like the bunny and Timex. Slackware just keeps on ticking!

I can't swim.

I don't believe you, even if you throw a baby in a pool it'll swim, a dog, a cat, a squirrel, they all quickly learn how to swim when thrown in water. I'm sure you will too.

@Carpo
I have a second partition that has KDE 4.1 from testing installed in place of KDE 3.5.10. It is a little slower to start up compared to KDE 3.5.10 ( although that is an impression as I have not actually timed it). In my limited experience KDE 4.1 is no different to KDE 3.5.10 in actual use as far as responsiveness is concerned. I am liking the the new program startup menu arrangement, which I think is good for getting to the most often used programs more easily.

I have not experienced any crashes although there have been some messages about unimplemented functionality and some weird display results when I have played with widgets, although that may be my inexperience more than KDE 4.1.

As is stated in the ChangeLog, there are still issues with some software.

Overall I like the new look, which makes 3.5.10 seem jaded.

My advice would be to clone your 12.2 install in a second partition, remove KDE 3.5.10 and install KDE 4.1 and have a play!

I was just thinking of doing that. Scrubbing Debian off my desktop, and installing 12.2.

Hi,
Not to get into a flame war with you 'H" but that myth is not always true about babies and water. Now animals instinct (human or otherwise) may result in a recovery but not always. Instinctively, yes everything should react to self preservation but panic does cause a lot of failures. Lower class animals do panic to situations differently.

This is a GNU/Linux forum so I'm referring to the GNU when comparing humans to animals. I don't like the rats with long fuzzy tails, too destructive. As for dogs and cats, if Ferrel then just place in a burlap sack before throwing in the water. Cheaper than a 22 cal. I could never get them to line up in a line to shot them with one shot. PETA people, I'm really kidding. Not really!

Eeeek, don't mention HUMAN.......the Ubuntu folks might not like that comparison.

Well, yes, instincts fail when panic takes hold. Another reason not to panic. Either way even people who say they cannot swim can still tread water to stay afloat at least as long as they don't panic.

Totally agree there, I spent a year as a Water Safety Survival Instructor (WSSI) and some people that never swam their whole life were surprised at how long they could tread water after being thrown of a 10 meter tower. Some would panic the first time but after being thrown off for the 2nd or 3rd time, piece of cake. The stories I could tell from those days...........sorry getting off-topic.

Well, maybe I'm a bit of a special case, but I feel like I have an obligation to run -current on my main "rely on" system (which is my laptop), and I think the rest of the team is pretty much the same way. The benefit (for everyone) is that when something *does* stop working, there's some *real* incentive to get it fixed :-)

I think you *are* a bit of a special case, Robby
I actually use my -current machines more than my -stable desktop. But it gives me a secure feeling I always have a stable system I can use. And when I run into problems with -current, it is a great learning experience. That is enough incentive for me to find a solution and get it fixed.

Well I just installed a fresh copy of 12.2 with no problems. I had it all up and running within 2 hours with a new kernel, nvidia drivers with dual monitors and all the software I use. SUPER easy.

I have just finished installing Slackware 12.2. This was a "clean" install from scratch. Just about everything went well, I did however have 2 problems, both of which I have been able to get around.

(1) LILO complains about not being able to find root=/dev/root. I checked to see what I had on 12.1, and it was root=/dev/hda1, so I manually changed lilo.conf to that and it worked. I'm sure there is a better (standard) way of dealing with that, I'm open to suggestions.

(2) Kaffeine would not compile...when doing the ./configure it said: ERROR: Could not find cdparanoia headers. I searched online and found that adding --with-extra-includes=/usr/include/cdda to the ./configure would enable it to find the missing headers. Again, perhaps there's a better way, but that did work.

All-in-all an easy straightforward install. Congrats on a job well done.

I had the same problem. The solution you mentioned is what the build script at Slackbuilds also uses, so I'm guessing that's the "proper" way.