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.
What is the big problem? where is the conflict with slackware philosophy that stops a working player, like VLC, from being shipped?
There are two issues to consider here.
1. Slackware does not come with software that could infringe copyright/patent. Other common examples are recent Oracle java, Broadcom wireless networking firmware and drivers, Apple audio codecs and until recently font handling (sub-pixel rendering, bytecode interpreter). A user can enable all of these by installing appropriate packages and/or recompiling software with appropriate switches.
2. Slackware is a base system that allows the user to add the applications that they want and need. VLC has no place on my Slackware server at work but Alien Bob's VLC package works very well for me on my home system.
On the other hand, if you're a bit lazy (which is perfectly legit), you'd probably be better off with Slackware derivative Salix. Just launch their Multimedia installer, watch some 60+ packages install automagically, and be armed to your teeth for multimedia content.
My "restricted" version of VLC (restricted in the sense that it contains code that violates stupid US patent law, and therefore can not be made available on a US server) has an internal version of libdvdcss and is totally self-contained: http://taper.alienbase.nl/mirrors/pe...ackbuilds/vlc/
My "restricted" version of VLC (restricted in the sense that it contains code that violates stupid US patent law, and therefore can not be made available on a US server) has an internal version of libdvdcss and is totally self-contained: http://taper.alienbase.nl/mirrors/pe...ackbuilds/vlc/
My "restricted" version of VLC (restricted in the sense that it contains code that violates stupid US patent law, and therefore can not be made available on a US server) has an internal version of libdvdcss and is totally self-contained: http://taper.alienbase.nl/mirrors/pe...ackbuilds/vlc/
If you are new to slackware, then why are you running -current? Use the official stable version as -current may break at any moment.
Thanks for the input.
But I have tried for weeks to get slack stable running on my new hardware without success.
These past 48 hours running -current have been bliss!
But I heed your warning and hold myself ready to do some work again if it breaks and I learned A LOT by the experience of fighting with, then renouncing stable, in favour of -current.
There are two issues to consider here.
VLC has no place on my Slackware server at work but Alien Bob's VLC package works very well for me on my home system.
Thanks.
I'm getting it now.
The heavy hint of acrimony in my tone was uncalled for but largely result of extenuation brought on by weeks of unwonted frustration and denial of king-baby's wishes (king-baby being me)
Thanks for the voice of moderation, information and balance, as is your customary style.
You have to reach out and grab the distro. Not the other way around.
Ceci est tres bien dit.
Well put; i totally agree with this sentiment; but i think it is well paired with the following input from BrianL. I refer to his comment about slack's power of attraction (I'd call it mesmeric!)
cheers d'un australien qui se passionne pour le francais
Thanks for the input.
But I have tried for weeks to get slack stable running on my new hardware without success.
These past 48 hours running -current have been bliss!
What hardware do you have? Try the following command:
Code:
$ /sbin/lspci
Paste the output into your answer window, and then we'll see what's the trouble with Slackware stable.
@textillis: there's a fat chance you can run Slackware stable if you build in Initrd before the initial reboot. I have a similar problem with two machines with an Intel chipset. I have some documentation on the subject.
@textillis: there's a fat chance you can run Slackware stable if you build in Initrd before the initial reboot. I have a similar problem with two machines with an Intel chipset. I have some documentation on the subject.
If you use Firefox, you might set the encoding explicitly to Unicode (UTF8) to display these pages correctly.
cheers,
Niki
I didn't knowingly "build in Initrd before the initial reboot ..."
I just did the install, followed by the usual post-install stuff.
Then I upgraded to kernel 3.7.1, hoping to get better support for my graphics, on advice from senior members here.
Then, when that didn't work, I went for -current, and all my problems seemed to have been solved!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.