This is not a call to be royally trolled.
I don't understand why FreeBSD does not offer support for DRM content like Netflix. Netflix is served on a FreeBSD appliance. I'm guessing this is a Netflix proprietary issue?
This is not a call to be royally trolled.
I don't understand why FreeBSD does not offer support for DRM content like Netflix. Netflix is served on a FreeBSD appliance. I'm guessing this is a Netflix proprietary issue?
This is what those who use server do not understand, in the daily life, people use programs to develop in their jobs, there are certain programs that are in linux but are not compatible with FreeBSD, there are other programs that are on windows but are not compatible with other systems. Some people use wine, and others prefer to install virtual machines and palliate the deficiencies that FreeBSD has.
As I really can't agree with one single of these statements (in my experience, all these things are remarkably simple and clear in FreeBSD), it seems there are some things you don't understand. But to help with that, I guess you'd have to open threads about specific problems and go into some detail...
My answer is related to the things that I do not understand open in the main topic. You will understand it, but it is cumbersome for me because I am not a professional in systems.
Why not? I use Wine for a few very "special" tools for C64 development (editors for sprites and charsets). They're closed-source and Windows-only. They're not complex software, so maybe one day when I have too much time, I will create similar tools just using Qt instead
(I already created a GUI disk editor for C64 disks, which is even available in ports ... before I did that, I also needed Wine for that....)Agreed. But some special cases will almost always exist. With Emulation, Virtualization, Jails and the "Linuxulator" (compatibility on syscall-level), FreeBSD offers more than enough ways to run "almost anything"
"Special cases" in my case include:
Yes, I believe so. I don't think the issue is so much that FreeBSD can't support DRM services (like Widevine), as it is that they don't want to support them, and this is because FreeBSD prefers to support the open-source and free software communities, of which they are a very important part, more than they wish to support the proprietary intellectual property communities that deliver DRM content, like Netflix. And I think, as cracauer stated above, that the issue is also very much one of control. Allowing DRM software control of the FreeBSD kernel is perhaps the primary problem... but...
Agreed. Hard to build a custom kernel? Ever try to build a custom Linux kernel config? Yowza. FreeBSD’s almost feels like it’s too easy in comparison. Include generic, give it a name, and tweak the options you need changed and away you go…
I'm guessing that Netflix simply did a very clean separation between reading data (supporting Widevine for visual display) and moving data (copying any file from place to place over a Content Delivery Network (CDN). An unmanaged switch does not have the software to play a movie from Netflix, but it's still an essential part in moving the movie file/stream.Yes, I believe so. I don't think the issue is so much that FreeBSD can't support DRM services (like Widevine), as it is that they don't want to support them, and this is because FreeBSD prefers to support the open-source and free software communities, of which they are a very important part, more than they wish to support the proprietary intellectual property communities that deliver DRM content, like Netflix. And I think, as cracauer stated above, that the issue is also very much one of control. Allowing DRM software control of the FreeBSD kernel is perhaps the primary problem... but...
freezr elaborated on some other problems with proprietary control of intellectual property. in the following thread:
, I'm so thankful bhyve exists. I'm tired of this idiotic trend.
make config, then VLC will play just about everything, and I'm happy. I tried doing the same thing in Linux, and the process varies from distro to distro, and I spent way too much time trying to get a handle on the process. Then throw in the dependency hell on top of that. FreeBSD has dependency hell, too, that's part of Open Source turf. At least I'm sensing that FreeBSD has some direction... If Linux distros (especially one-dev shows of 'Look how I can roll my own!') are puddles, FreeBSD is a river.The Forums here actually are a good place to ask questions about pkg/ports. The best way to learn is to play with it, make mistakes, ask questions, read the manual pages, and spend time with it.
pkg(7) is the FreeBSD equivalent of RPM (which stands for RedHat Package Manager). Ports are for those who don't like the default options provided by pkg(7), and want to compile that same software with more features. And that's just a start.
Please, read again what FreeBSD is (and what it is not)....
You likely don't use rpm directly. You use
yum or dnf. Clarity soon reduces compared to the simplicity of FreeBSD's approach of not needing a metadata database.FreeBSD actually does have a metadata database for
pkg... every repo has a 6 MB metadata.txz that gets downloaded every so often when pkg is invoked.
Simple answer, it shouldn't be tied to base release cycles. Ports are independent from base, and whenever ports frameworks get new features, there's a chance pkg must support them as well. So, all that will be in base is some "minimal" pkg just good enough to "bootstrap" pkg, and this is certainly to stay that way.
Well, that makes sense actually. One thing less I don't understand.
There's many ways to interpret it...
git, learning it would benefit me as a FreeBSD user, but I know enough to know that it's not an OS thing like sysctls... and I'm not too worried about my ability to put in effort, RTFM, and get the results I want on my machine. 