On Sun, 14 May 2006 07:29:04 -0700, Mahy wrote:

> Mahy wrote:
>> ok, this might sound really noobish, but is there a place to find
>> libstdc++??
>>
> Don't bother, i found it. It was in the cxxlibs package. Who on earth
> might've known it without g00gle...

http://slackware.it/en/pb/

--
"Don't worry about people stealing your ideas. If your ideas are any
good, you'll have to ram them down people's throats."
-- Howard Aiken

Sylvain Robitaille wrote:
> 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.
>

Yes, you're right.

> 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.
>

Huh, i did compile a kernel today (2.6.16.16), included som features
such as sata, it booted ok, even X started fine, but few seconds into
X, the system froze so badly, that even ctrl+atl+bckspc was no help...
Enough of compiling for today, i might try it again in a few days'
time.

To Guybrush: Thanks.

Mahy

In article <1147594246.095758.107270@j33g2000cwa.googlegroups .com>,
"Mahy" <jkotuc@gmail.com> 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.

It so happens that the Firefox, Thunderbird and Java packages are made
from the official binary distributions published by the authors, and
those binaries are very conservative with regards to library
dependencies and the like. So you should be able to just install these
from -current.

Alsa is a different matter since it is dependent on the particular
kernel version under which it was compiled. But as long as your sound is
working, I don't really see the point of upgrading it. If you insist,
try downloading the source directory from the -current tree and running
the SlackBuild script as root.

- Martijn

Now this is cool, i downloaded Opera 9 Beta for Slackware, only to
realize it's not a Slackware package, only a tgz archive. I even tried
running Opera from that archive, but it complained about missing files
and so on, so i deleted it, downloaded an Opera rpm for SUSE, ran
rpm2tgz, installed the newly created package and now Opera works! How
cool is that?

Mahy

On Mon, 15 May 2006 12:55:25 +0200, Martijn Dekker wrote:

> Alsa is a different matter since it is dependent on the particular
> kernel version under which it was compiled. But as long as your sound is
> working, I don't really see the point of upgrading it. If you insist,
> try downloading the source directory from the -current tree and running
> the SlackBuild script as root.

You don't see the point? Not see the point?? The point is to always have
the LATEST stuff, absolutely regardless of whether it works or not.

Think about the posts you see in all the newsgroups, about how to get the
latest even though there isn't a distro package for the software yet.
Think about how no-one wants to run a 2.4 kernel that works now that one
can get a 2.6 kernel (that probably doesn't).

Think of all those people who loved Firefox and were using 1.06 or
whatever, and suddenly couldn't be happy because someone else was running
1.5. Even though 1.5 didn't add anything special, it HAD A HIGHER VERSION!

Since Slackware is one of the last refuges left for people who like stuff
to be mature before it goes into the distro, maybe one should beware of
feeding the tendency to need the latest....

--
mark south; echo znexfbhgu2000@lnubb.pb.hx|tr a-z n-za-m
"I can trace my ancestry back to a protoplasmal primordial atomic
globule. Consequently, my family pride is something inconceivable."
-- Gilbert & Sullivan, The Mikado

Sylvain Robitaille wrote:
> 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.
>

My $.02 has been that Slackware-current is slackware-pretty-darn-stable
because other than Koffice I can count the number of major crashes on
one hand with most of my fingers shot off. And, IMHO, Koffice sucks.
Either go full bloat with oO or just use
kword/pico/emacs/vi/text_editor_of_choice.
(Koffice may not really suck, I just think it's too big to be "just a
text editor" but it's not "feature overload" like oO or MS Office...)

I've started syncing slackware-current monthly so I have an old copy
(and with hardlinks it hardly takes up any more space than one copy) and
use that to build new boxes. Other than the odd gotcha, I've found it
works fine. If I was building 50 servers for a cluster, I would
probably pick one version and make it THE load, but I'm not.

Ray

Mark South wrote:
> On Mon, 15 May 2006 12:55:25 +0200, Martijn Dekker wrote:
>
> > Alsa is a different matter since it is dependent on the particular
> > kernel version under which it was compiled. But as long as your sound is
> > working, I don't really see the point of upgrading it. If you insist,
> > try downloading the source directory from the -current tree and running
> > the SlackBuild script as root.
>
> You don't see the point? Not see the point?? The point is to always have
> the LATEST stuff, absolutely regardless of whether it works or not.
>
> Think about the posts you see in all the newsgroups, about how to get the
> latest even though there isn't a distro package for the software yet.
> Think about how no-one wants to run a 2.4 kernel that works now that one
> can get a 2.6 kernel (that probably doesn't).
>
> Think of all those people who loved Firefox and were using 1.06 or
> whatever, and suddenly couldn't be happy because someone else was running
> 1.5. Even though 1.5 didn't add anything special, it HAD A HIGHER VERSION!
>

I do agree, to some extent. Alsa prior to 1.0.11 doesn't work on my
system (Intel HDA soundcard) without a special patch. Thus, coz there's
a 1.0.11 package available (in -current), i want it. If it doesn't
work, then so what? I'll still have to compile it from source, coz
1.0.10 package is definitely useless.

As for 2.4 kernel, AFAIK, it doesn't support ipw2200. Period.

Firefox? Versions below 1.0.8 can't force links to new window to open
in a new tab, and that' a major drawback. Yes, that doesn't advocate a
change to 1.5, but if i'm about to download a higher version, then why
not 1.5? It's a painless install, all the same.

Apart from that, IDGRA about version numbers.

Mahy wrote:
> Wow, you've all been quite helpful. Thanks for the Pat's howto on
> upgrading. Yes I ran everything as root. I didn't try chmod on
> slapt-get executable, i was too perplexed when I found out it doesn't
> work. Ok, i'll try to function without these tools.

I wouldn't go that far. For me, swaret is an awesome tool for
downloading and installing *what I tell it to*. Think of it as a
network-aware version of packagetools that has some basic error checking
(such as missing libraries), not as a magic upgrade wizard.

- Daniel

D Herring wrote:
> I wouldn't go that far. For me, swaret is an awesome tool for
> downloading and installing *what I tell it to*. Think of it as a
> network-aware version of packagetools that has some basic error checking
> (such as missing libraries), not as a magic upgrade wizard.
>
> - Daniel

Yeah i kept it too. "swaret --install jdk" is trouble free all the
same. But the bad thing is dependency checking. Swaret is able to
identify that libstdc++.so.6 is missing, but is unable to find out
which package is it in (cxxtools) and install it. I just dunno why. A
real bummer for someone like me...

Mahy

Mahy <jkotuc@gmail.com> skrev 2006-05-16:
> D Herring wrote:
>> I wouldn't go that far. For me, swaret is an awesome tool for
>> downloading and installing *what I tell it to*. Think of it as a
>> network-aware version of packagetools that has some basic error checking
>> (such as missing libraries), not as a magic upgrade wizard.
>>
>> - Daniel
>
> Yeah i kept it too. "swaret --install jdk" is trouble free all the
> same. But the bad thing is dependency checking. Swaret is able to
> identify that libstdc++.so.6 is missing, but is unable to find out
> which package is it in (cxxtools) and install it. I just dunno why. A
> real bummer for someone like me...
>

Slackpkg from slackware/extra does a very fine job, when searching
for a missing package:

slackpkg search libstdc++.so.5

The list below shows all packages with the selected pattern.

[ installed ] - cxxlibs-5.0.7-i486-1
[ installed ] - gcc-g++-3.3.6-i486-1


--
Morten L