Have *you* read the file? It's not the usual UPGRADE.TXT - you'll notice that it details each package that has been added, each package that has been removed, and and has notes on new dependency issues and such in addition to detailed upgrade instructions. If a user is well-versed enough to have a partial installation, then there's absolutely no reason why he/she wouldn't be able to follow the relevant parts of that guide.

Don't use runlevel 3 so xwmconfig depending on which is not a concern. Still haven't installed or found a use for which in what I do. Did have to install mcs and gamin. upgrade_txt has been updated since I last captured it but I see little about interlinked dependencies. Missing elements can be found in the MANIFEST and then installed if wanted.

Just for an alternative perspective. I have two boxes, one that is reserved for goofing around on. The goofing around one upgraded nicely from a fresh 11.0 install with slapt-get to current in two stages. First, with

slapt-get --distupgrade, then a reboot,
slapt-get --install-set --remove-obsolete a ap d e f k kde l n t tcl x xap y

As I watched it go through things, it seems to have done the installpkg steps in pretty much the order suggested with the exception that I think it upgraded the glibc-so libs before doing the kernel. Not sure if that's a problem though.

After that it took a bit of hand tweaking of things like /etc/ld.so.conf and a few other things in /etc to get it to work (should have kept notes).

This pretty much mirrors what I do with a new slackware version anyway. rsync the home tree over to one computer so there's a backup, wipe the hardrive and install a clean version. I don't fill the HD with lots of movies, so what's a few hundred megs of extra fonts/drivers?

I then had compiz and all working nicely. Now, is there a nice configure program for compiz? I can't seem to find any way to configure the eye-candy.

PS: This worked on my goof around box with an nvidia card, but not on the laptop with an intel graphics card.

All things considered, if a person really understands what's happening behind the scenes in an upgrade, an automated tool can (will usually) work fine.
With respect to the kernel upgrade, yes, that step is important - glibc-2.5 *needs* a 2.6 kernel.

Most likely things like moving/merging .new files (something that has to be done regardless of how you upgrade).

I sa a posting the other day with a minimal list of X packages -something like 4-7 package I believe- Try tracking that down. Separate packages of course makes it easier to upgrade individual components. It also makes it easier to custom install and leave out what you don't need. Finding out *what* you don't need is is a nightmare though. I also do not like having to sort through nearly 300 package names which were covered by 5-7 packages before. But since upstream has gone modular we are pretty much stuck with that.
Simplicity and flexibility are usually on opposite sides of the coin.

Here's the link to that thread.
http://www.linuxquestions.org/questi...ighlight=libcm

Not so..
I absolutely cannot stand 300 X packages. Has to be the siliest thing I've ever heard of..

I was hoping Pat would think it thru a little and decide to break from "mainstream", but I guess not. No matter, if you don't like something, then change it...

OK, here's something else that's frustrating

I've been running current on a computer with an NVidia card for a couple weeks now, no problems. So I thought I'd give it a go on my laptop with an i945 card ... problems.

Using the intel driver for xorg, I get huge fonts. By huge, I mean that the icon names for Wastebin and Home fill the screen all on their own. Fonts where individual letters fill about 1/3 of the screen. This is not joke. I can't even fix it with kcontrol since where I need to get at is somewhere off the bottom of the screen in the netherworld. And there's no way to see when I scroll down to it.

If I start an xterm (not a konsole, but a good old xterm) I get a monster titlebar, but at least a useful text area, from which I can get a xdpyinfo ... which tells me the following ...

screen #0:
print screen: no
dimensions: 1280x800 pixels (289x21 millimeters)
resolution: 112x968 dots per inch
depths (7): 24, 1, 4, 8, 15, 16, 32

However, my xorg.conf file says

Section "Monitor"
DisplaySize 330 210 # mm
Identifier "Monitor0"
VendorName "LPL"
ModelName "0"
EndSection

So, somewhere the detection of the screen resolution is getting messed up ... can't tell if this is a slackware thing or an x thing or what.

As a temporary work around, I've noticed that everything works fine when using the vesa driver instead of the intel driver. So, I was able to go in using the vesa driver and get at kcontrol to pin all my fonts to "force fonts DPI" to 96. Then switch the driver back to intel. So, now the fonts at least look OK, but some things (like xine) which depend on having good info on the screen resolution still look extremely weird.

Is there some way to fix this for real? Is there some other (possibly undocumented) option I can put into xorg.conf? Is there some other way to pin this down as a slackware or xorg problem?