Mahy wrote:

> ... slapt-get, ... can't execute /usr/<something>/slapt-get, so i
> tried swaret. It performed update and upgrade (to "current"), ... ...
> started dependency checking. I was shocked when it found hundreds of
> missing libraries, that were nowhere to be found. After updatedb and
> reboot, the system is quite crippled. ... Is it a way to resolve it??

As you've already seen, the easiest way to restore your system at this
point is simply to reinstall, then avoid using third-party package
manglement "tools". If you really want (or "need"?) -current, the
_best_ way to go about it with minimum headaches, is to follow
Slackware's own documentation. Be prepared to read a lot, though.
-current changes very frequently, and you'll often need to know exactly
what's changing in order to be able to set it up correctly on your
system.

Slackware -current is NOT (nor is it intended to be) a "stable"
distribution.

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems and Network analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

allisonken1 wrote:

> Since you didn't mention it, just a reminder that all package managers
> must be run as root.

Yes, but since he reports that his system is hoes after running Swaret,
it seems to me a safe bet that he was running it as root...

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems and Network analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

Mahy wrote:

> How to (easily) upgrade to "current" without any 3rd party util while
> minimizing the risk of landing with bricked system? ...

I'm curious to know why you're so set on running Slackware -current so
soon in your Slackware experience, especially given that in an earlier
post you were challenging whether this was supposed to be the "stable"
Slackware. You won't get stable with -current, though you'll get
"reasonably current" with Slackware's stable release.

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems and Network analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

Sylvain Robitaille wrote:
> I'm curious to know why you're so set on running Slackware -current so
> soon in your Slackware experience, especially given that in an earlier
> post you were challenging whether this was supposed to be the "stable"
> Slackware. You won't get stable with -current, though you'll get
> "reasonably current" with Slackware's stable release.

Well, i sorted out my priorities a bit, but i still can't stand having
firefox and thunderbird so much out-of-date. I did clean reinstall, and
this time upgraded only ffox, thunderbird, java and alsa.

A package alsa-driver-1.0.11 didn't work ("modprobe snd-hda-intel"
reported no such module), but when i downloaded it as a source and then
compiled it, it did. I guess that's the way things work in Slack, very
much unlike Ubuntu ...

I also plan to upgrade kernel, coz kernels below 2.6.14 cause my HDD
control light to be permanently on, which gets a bit annoying over
time.

Other than that, i'm not obsessed with -current after y'all told me
it's quite unstable.

Mahy wrote:

> Well, i sorted out my priorities a bit, but i still can't stand having
> firefox and thunderbird so much out-of-date. I did clean reinstall, and
> this time upgraded only ffox, thunderbird, java and alsa.

Did you notice that there's a Changelog for Slack 10.2 as well? It has
the most recent versions of Firefox and Thunderbird too, and a number of
other security updates. I must-visit, I suppose :-)

PJ

Mahy wrote:
>
> Well, i sorted out my priorities a bit, but i still can't stand having
> firefox and thunderbird so much out-of-date. I did clean reinstall, and
> this time upgraded only ffox, thunderbird, java and alsa.
> [...]

That's the way to go. I have Slack 10.0, but that didn't stop be from
installing Fx 1.5.0.2 and Tb of the same version. I bought the Fx/Tb CDs
and upgraded later.

Just because you want a few of the latest applications does not mean
that you have to upgrade your O/S. Slackware is not a Microsoft O/S.

On 2006-05-14, Mahy <jkotuc@gmail.com> espoused the following:
>
> A package alsa-driver-1.0.11 didn't work ("modprobe snd-hda-intel"
> reported no such module), but when i downloaded it as a source and then
> compiled it, it did. I guess that's the way things work in Slack, very
> much unlike Ubuntu ...

I believe that you should only update alsa if you update the kernel.
In the past, alsa would be built against a matching kernel version. From the
changelog, I believe Pat is trying to get away from that, but for me I still
had to keep them matched for them to work.

Scott Cole

--
Only trust pipesmoking penguins.
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." --Benjamin Franklin

ok, this might sound really noobish, but is there a place to find
libstdc++?? I've browsed through mirrors, unable to find one. Am i
looking for a wrong package name?

Mahy

Mahy wrote:
> ok, this might sound really noobish, but is there a place to find
> libstdc++?? I've browsed through mirrors, unable to find one. Am i
> looking for a wrong package name?
>
> Mahy

Don't bother, i found it. It was in the cxxlibs package. Who on earth
might've known it without g00gle...

Mahy wrote:

> A package alsa-driver-1.0.11 didn't work ("modprobe snd-hda-intel"
> reported no such module), but when i downloaded it as a source and then
> compiled it, it did. I guess that's the way things work in Slack, ...

This isn't Slackware-specific. The ALSA driver is very dependant on the
kernel with which it was compiled. If you upgrade one, you need to
upgrade the other as well. The best approach, if you want a newer ALSA
than the distribution provides for the kernel you're using, is to do
exactly as you have done, and compile the driver yourself.

> I also plan to upgrade kernel, coz kernels below 2.6.14 cause my HDD
> control light to be permanently on, which gets a bit annoying over
> time.

I've not tried newer kernels from -current myself. Instead, the kernel
is another component that I simply compile myself, tuned to my systems,
from source. I think you'll find it much less aggravating that way.

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems and Network analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------