|
Slackware64-current (after the big one) multi-lib - some thoughts.
Clitus I'm bored. What plaything can you offer me today?
Well this pretty much sums up the experience with Slackware current these days. This is not to say it was all plain sailing. So what problems were there?
1) Nvidia drivers did not work, this was fixed by re-compiling the kernel modules and installing a patched or beta driver, but it introduced another fault. However this problem cannot be accredited to Slackware, all operating systems have driver problems after being updated. Nvidia however had a new version out in a couple of days, which completely fixed the problem.
2) The problem introduced by the hacked fix of the older Nvidia driver wouldn't allow me to switch to the generic kernel (it would not create a valid initrd.gz). I think this was because of re-compiling the kernel modules, so I re-installed them and the problem was fixed. Again not a Slackware fault but a samac fault.
3) Program A couldn't find library B. Slackware has moved some libraries from e2fsprogs to util-linux-ng. This may cause some stuff to break if you are using the multi-lib extensions. This was fixed by creating a compat32 package for util-linux-ng. Again not actually Slackwares fault, but a little closer to home. Alien Bob could you update the massconvert.sh please.
That's it so far, after an update that ran to over 500 lines in the change log, an updated kernel, updated glibc, updates X server etc. etc. and three paltry problems none of which could be attributed to Slackware directly.
Current used to be a bit more exciting than this, so as I said in the opening sentence.
Clitus I'm bored. What plaything can you offer me today?
samac the merciless
ruler of the known universe
Last edited by samac; 03-06-2010 at 11:30 AM.
|
