SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Please built all speakup modules in generic kernels.
Due to a bug, if all speakup kernel drivers are modularized, speakup_synth fails to be loaded.
As a consequence blind users relying on the speakup software synthesizer (i.e. most of people using speakup) do not have speech if they use a generic kernel.
live555 is not in Slackware and MPlayer provided in Slackware doesn't ship its own version.
besides that, also if they were linking against live555, the first url in the article you linked says:
Quote:
However, according to an email sent to by Ross Finlayson of Live Networks, Inc., to HackRead, the vulnerability does not affect VLC or MPlayer because both media players only use LIVE555 to implement an RTSP client.
“This vulnerability does not affect VLC or MPlayer, because they use LIVE555 only to implement an RTSP client,” Finlayson told HackRead “The bug affected only our implementation of a RTSP server, which these media players don’t use. (VLC does have an embedded RTSP server, but that uses a separate implementation, not LIVE555’s.)”
Some time ago wget got l/libunistring dependency.
l/tagfile still says "libunistring:OPT".
Is it good idea to change "libunistring:OPT" to ADD or at least REC?
Is it good idea to add /usr/lib*/libunistring.so.* into aaa_elflibs package?
Me vote for both. :-)
I'll change the status from OPT to REC at some point soon, though I'll note that none of those tags are any guarantee that dependencies in Slackware will actually be met. Only a full install is.
Since libunistring is a rather large library I'm not inclined to add it to the aaa_elflibs package, especially since wget isn't part of the A series. And again, I'll note that these series divisions are largely legacy and shouldn't really be paid much attention.
The cryptsetup v2+ added support for Forward Error Correction (FEC) as used on almost all newer Android devices and is thus needed when working on Android images.
Please just let me know if I can do something more that would help getting this upgrade in.
We've been using the v2 series for a while now (with focus on Android image files).
Are you sure the Guest Additions are still beneficial with an up-to-date distro?
I was strugging with Ubuntu 8.10 in VirtualBox until I realized that I wasn't actually supposed to install the Guest Additions, and it was working perfectly without them. My impression is that the newer X and kernels already provide their functionality.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.