botched upgrade: is this a good fix?
 

heya, i attempted to have swaret update my slack 9.0 to get all the 9.1 packages, but some dependency issues or glitchy packages that i cannot pin down have caused massive problems. i had just recently gotten the 2.6.0test6-mm1 kernel to work, but then when i upgraded the packages it broke my xterm, rxvt and konsole. broke means the following: xterm and rxvt won't run under fluxbox and konsole spawns (in some cases thousands of them) zombie processes out the ass when i have a root shell issuing commands.

my idea for fixing this would be to uninstall all the packages on this box and then get the source for the various things i need and recompile it all from scratch, with only what i need. i'll make a point of using checkinstall to allow for removal of installed sources. does this seem like a really bad idea? if i do this, i'll make certain to backup all my stuff on CD-RW. also, is there a suggested order of operations if i do this? should i get the newer gcc first?

i know this is a LFS sort of question, but i'd just like to find a way around having to get the new slackware iso and then reinstall to fix my botched packages. so recompiling things from source seems like a good thing to do, although it may be complicating.

thx for reading,
y-p

if you had the files local this is how it would work

0. Put your machine in single-user mode:
telinit 1


1. Upgrade your glibc shared libraries. This is important, or things
will go haywire during the first part of the upgrade:

upgradepkg /path to packages/slackware/a/glibc-solibs-*.tgz


2. Upgrade your package utilities:

upgradepkg /path to packages/slackware/a/pkgtools-*.tgz


3. Install sed. This is used by the package utilities.

installpkg /path to packages/slackware/a/sed-*.tgz


4. Upgrade everything else (and install new packages):

upgradepkg --install-new /path to packages/slackware/*/*.tgz

So maybe you could try that same upgrade order with swaret.

See HERE. This worked well for me. :)