interesting lockup with Slackware current

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ah well. Slackware 9.1 is up-to-date so far as its own packages are concerned, and things are working beautifully. I'll definitely not be upgrading to Slackware current again unless it's really necessary.
Thanks,
Steve


*********** REPLY SEPARATOR  ***********

On 5/31/2004 at 9:38 PM Doug Sutherland wrote:

>Steve,
>
>I've gone down the road of playing with slackware-current, and that
>basically
>equates to unstable, untested, incompatible, etc. Also, mixing and matching
>the latest stable rev (9.1) with some of the current stuff is dangerous,
>they
>often use different revs of the very basic core stuff like gcc, glibc, and
>binutils (from which everything is built). With slackware, its usually best
>to stick with the latest stable rev, and if you need to upgrade stuff, best
>to build from source.
>
>Regarding your sendmail "lockup", I'm willing to bet that the machine was
>not
>frozen, rather sendmail was confused about some configuration detail
>related
>to networking. Like I said before this is common. That used to happen to me
>in the redhat 5 days. Usually the problem relates to DNS name resolution.
>
>   -- Doug
>
>
>_______________________________________________
>Speakup mailing list
>Speakup at braille.uwo.ca
>http://speech.braille.uwo.ca/mailman/listinfo/speakup


Stephen Clower, that guy from the south.
You can reach me by any of the following:
E-Mail: steve at steve-audio.net
MSN: steve at steve-audio.net
AIM: AudioRabbit03

You can also check out my little home on the web by visiting http://www.steve-audio.net
    





[Index of Archives]     [Linux for the Blind]     [Fedora Discussioin]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]
  Powered by Linux