Hrm, that's odd. Is there actually a /dev/root symlink present?
If so, what's the target, and is it really the / filesystem?

No symlink. But something else looks strange.... at Kinfocenter/Storage Devices I see:

Device: /dev/hda1 Type: reiserfs Size: N/A Mount Point: / Free: 0 B Full%: N/A
Device: /dev/root Type: ? Size: 8.0GB Mount Point: / Free: 5.9 GB Full%: 26.5%

So somehow both /dev/hda1 and /dev/root are claiming mount point /.

In fstab I have /dev/hda1 but not /dev/root.

Very strange.

Yes, this new /dev/root has been discussed here on LQ recently:

http://www.linuxquestions.org/questi...evroot-688189/

I've just upgraded to 12.2 from 12.1. As always, I followed the instructions in UPGRADE.TXT and CHANGES_AND_HINTS.TXT, and it was a piece of cake.

It's not mentioned in the release highlights, but 12.2 upgrades to Tcl/Tk 8.5 from 8.4, that was a nice surprise (Yeah ok, who uses Tcl these days, right? At least there are the aMSN users ).

Hi.
Another stupid question:
I run -current for couple of months.
If i simply change today mirrors slackpkg from -current to 12.2 i stay with 12.2 now?
-current now is 12.2 -> so simply to change my mirrors config file to 12.2 will
keep me on 12.2?

Is it wright ?

There are no stupid questions!
Correct.
If you want to continue the adventure of following -current, leave your mirror as is. If you want to stay with the -stable version and just update security fixes, change your mirror to 12.2

I also run -Current on all of my machines (two desktops, one laptop) and nothing to worry about (well, once, only at the beginning of -Current development where new things are introduced for the first time. After that, most of the updates are completely fine on my system).

In fact, my laptop is based on Slackware 10.1 and up to now i have been following -Current on that laptop and works just fine.

There are just lots of inquisitive idiots. ;-)

* No, that wasn't at all directed at anyone who asked a question in this thread -- it just reminded me of a "demotivational poster" at ThinkGeek.com

Finally took the plunge (on my laptop). Water's fine. No signs of piranhas or sharks yet.

Yeah, finished my second install of 12.2 last night. Absolute perfection, no bugs evident.

does anyone have a breakdown of what is on which disk?

The Slackware torrents page has a breakdown of which package series is on each CD.

http://slackware.com/getslack/torrents.php

Thank you.

the strange thing i had noticed that a lot of problems had appeared when slackware 12.2 had released
i don't know why ??????????!!!!!!!!!!!!
isn't it tested perfectly ???

(1) You seem to indicate that the errors come from Slackware 12.2 release. It may be just a coincidence, for example everyone looks closer if something strange happens when booting. Or some errors are discussed that are present in the vanilla code. Or the kernel developers changed something and these changes don't fit Slackware users habits. Fill in some other reasons for this ...... Maybe reread the posts and look what errors happened because of bad package integration, I guess you will not find many of them if any.

(2) Is your last question meant to be serious? What do you consider perfect? I think nearly *nothing* can be done perfectly. "Thorougly tested" would be what I hope for No offense intended, but the word "perfect" triggers my gyrus humoris