Netflix uses FreeBSD 9.0
signup.netflix.com
signup.netflix.com
(Almost.)
Of course that majority will also never be given a choice.
Sony PlayStation users are using FreeBSD. I doubt they will complain.
Imagine, for the purposes of a thought experiment, a majority of users would be receptive to using FreeBSD. Imagine that instead of staring at a screen that says "Buffering...", the user could transfer files to the her home computer with something as simple as:
tnftp -o /home/netflix/nextmovieinqueue.mp4 ftp://netflixftpserverlocatedatisp.netflix.com/requestedmovie.mp4
And when the download completes, the user could serve the video to the devices that are connected to her WiFi router:
tcpserver -vRHDl0 192.168.2.0 80 bozohttpd -snX /home/netflix
And then she accesses the file as she would any video on the www, by pointing her web browser/http client at http://192.168.2.0/nextmovieinqueue.mp4
In this imaginary scenario, how could "DRM" be implemented without forcing the customer to use a particular OS, browser or video player, or some other closed source program?
Could it be done?
The problem is there is no port of Silverlight with the necessary DRM. The latter is unethical in the context of free software.
However, from what I've read, Netflix intend on switching fully to HTML5 in the near future. This will make their platform OS-agnostic, while still benefiting from things like Encrypted Media Extensions (EME).
Though breaking EME is probably more interesting for a certain class of developer than implementing all of Silverlight with DRM is.
they cannot implement eme because they are open source.
Personally, I think this licensing difference is what makes companies use code from one but not the other. E.g. Apple's Darwin and it's kernel (XNU) contains code from BSD. While Darwin is "open source", it acts as the core/foundation of a closed source OS. Had they used a GNU kernel like Linux, or GNU libraries (glibc) then they'd have had an issue or two with certain uses in conjunction with closed source software (e.g. statically linking glibc). I reckon that influences decisions on what to use.
Perhaps the best example to fit your comment is JunOS, a closed source, FreeBSD based OS.
In Netflix's case, it does seem that they modify some of FreeBSD to fit their use case, and they boast about how they will contribute back to the FreeBSD project any changes that they make. The BSD license does _not_ require them to do so, and who are we to know if they're actually contributing everything back. If they used a GPL'd OS, they might be obliged to do it, but I'm not a lawyer.
I don't believe, however, that the license played any part in Netflix's choosing of FreeBSD, and I don't believe that what your comment points out should be considered trolling :)
[0] https://en.wikipedia.org/wiki/Affero_General_Public_License
If we are talking about open as in permission to use, modify and distribute, then both licenses are equally "open".
If we are talking about open as in permission to close down the permission for others to modify or distribute newer version, and sue anyone who acts different - Then we do have one license that is more "open".
One could also argue that a standard business model of today rely on being able to threaten users with lawsuit if they modify or share the software. The "openness" to use such model is only available for one kind of licenses and not by others.
I might not go as far as calling it more open, but then I have a distinct opinion on the word open.
That means, for developers who build a startup using the XaaS business model, only MIT or BSD works really well. While LGPL and GPL may work, but require legal steps, where there is no money for lawyers and such. These startups cannot compete against the corporate enterprise market, like Google for example. And according to the theory of "The rich get richer", this will not change, unless someone clever enough, uses system theory to subvert and defeat the corporate culture, or the whole society backs this idea, ie. to stop the inevitable destruction of the remaining planetary resources. Guess why SpaceX wants to mine asteroids. It's not that resources are rare or something, they are simply rare, because someone with the budget reserved a large amount for himself, to control the market. Yes this is virtually a power Google also has, it could make the barrier of entry for any startup so hard, that those who want succeed need to be financed by them (through acquiring) or by visionary investors. Please don't get this as Google hate, it's just a logical observation and I am also doing human errors from time to time. When you find a logical flaw, I'm curious to discuss that with you.
They are stuck, the movie people want DRM, but nothing really exists on Linux for such. So they had to go with Silvershit.
Netflix does not seem interested in enforcing their "Linux (/*BSD) ban"[1], I can even use a desktop recorder to rip straight from Netflix if I wanted which essentially makes it a "take what you want" service.
[1] http://www.omgubuntu.co.uk/2012/02/netflix-no-plans-to-suppo...
Comparison to others: https://wiki.archlinux.org/index.php/Arch_Compared_to_Other_...
Gentoo still uses a BSD Ports-like system called Portage. You can still have a sync'd directory of Ebuilds, which correspond to FreeBSD Makefiles, only you have the added benefit of USE flags, compilation options, and even binary packages.
You can run Portage on FreeBSD.
Gentoo still uses, by default, OpenRC, which is a BSD-like init system that also handles dependencies. It is compatible with other FreeBSD and NetBSD scripts as well.
You can run OpenRC on FreeBSD and NetBSD.
Arch, on the other hand, has Fedora's systemd, which is completely incompatible with any of the BSD's thanks to its use of cgroups, which are a Linux kernel only feature, and the developers of systemd have dismissed, openly, the BSDs as outdated and unimportant.
Arch also uses binary packages for most of its packages, which is closer to rpm/dpkg than it is to Portage/ports.
The AUR is a limited system designed for pulling in alternative and source packages. It lacks USE flags and compile-time and runtime end user control. The AUR is mostly managed by the community, and many AUR packages have a lower quality than the base pacman available packages. The less popular a particular AUR package, the less people will be involved in it, and the lower quality it will be.
On the flipside, the BSDs have impeccable quality packages. They're not configurable without tweaking stuff manually, but the defaults are rock solid.
Gentoo's core Portage tree packages are managed by official developers who are assigned duties. And like the AUR, the community is able to apply any number of "overlays" on top of the Portage tree, giving the community direct ease of modification of not only community packages, but core ones as well.
So, how is Arch the "best of BSD and Linux" when it has absolutely nothing to do with BSD?
You're being a little biased here.
Systemd has been default since 2012, yet Archlinux started in 2002. Before systemd, the default system (initscripts[0]) was very much BSD-like by design. Not anymore, that's true.
Regarding packages, you don't have to use binary packages; you can very well use the ABS [1], which AFAIK really is what ports are about:
- You get a tree where you can download recipes. They're called PKGBUILD in Arch, ebuild in Gentoo, but essentially do the same thing. Take a look at nginx's PKGBUILD [2], and you will recognize a logic similar to the corresponding ebuild [3], yet far simpler (because less configurable, I hear you coming)
- You have a set of tools to create a fake root, calculate dependencies, build the package according to global properties (there are compile flags [4], but I have no idea how they compares to the famous USE flags) and install the package.
- Pre-built packages are just packages that were built by the Archlinux team with sensible defaults and have proven to be stable enough (by Arch's standards), so I as a user don't have to bother re-compiling. But the process behind is completely done with PKGBUILDs.
The AUR is "just" a staging zone where packages get to be tested by the community at large. When it's popular enough and a Trusted User commits to maintaining the package, the PKGBUILD can be part of the [extra] repository, where all packages are automatically built and proposed to arch users... but still, with the same build process.
To me, Arch sits between Gentoo/*BSD and "higher-level" distros: it keeps the process as close as possible to upstream applications by providing a minimal framework to install and update them, so that users can get understand how gluing packages together works, and what they have to do to have a functional system that does what they want, and not spend time on understanding how the packages work inside. Arch is more about understanding and using the system as a whole, than understanding every brick.
[0] https://wiki.archlinux.org/index.php/Initscripts [1] https://wiki.archlinux.org/index.php/ABS#What_is_the_Arch_Bu... [2] https://projects.archlinux.org/svntogit/community.git/tree/t... [3] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/www-... [4] https://wiki.archlinux.org/index.php/Makepkg#Architecture.2C...
I look at BSD / MIT as foundational licenses that anyone can use. Those companies that don't understand the business case for getting their changes put back into the mainline of a project just aren't worth your time. It is a nice self selection process by companies and a good indicator if they will get the whole open source thing. Its like a spam filter for source code.
For example, Netflix is contributing source and money back.
So few people use *BSD as a desktop that the demand for it is not going to make it happen, however.
I'm pretty sure the DRM used in the Netflix silverlight player is Microsoft's "PlayReady", so no... Netflix can't port it if they want.
Some good details on the OCA http://people.freebsd.org/~scottl/Netflix-BSDCan-20130515.pd...
FreeBSD is a natural choice if you want stability, even over Linux. I enjoy their update scheme although the lack of an official 'pkg' repository gives in to my nerves.
So, why is this news, is beyond me...
ps. I see a lot of people complaining that they use an open platform (FreeBSD in this case) to create a closed product. If I'm not mistaken (I'm not a US citizen and Netflix doesn't work in my country) it's a media-content rental service. So what exactly is the open source alternative, www.PirateFlixbay.org? :-)
Why? I believe the leader of their core group works for Netflix.
I think instead of a page thanking FreeBSD for software, Netflix, alongside many other large companies who use free software, could make more of an effort to actually contribute to the software proportionally to their use of it.[/s]
I apologise, clearly I had misinterpreted it and was wrong!
• Camcontrol mods to download SATA firmware
• IPv6 ref counting fixes
• ixgbe interrupt mitigation, RX optimizations
• Fixes for isci driver for firmware download
• Collaboration with FF, Isilon on Unmapped I/O
• VM/VFS Tuning: vfs.read_min
1) https://news.ycombinator.com/item?id=6949244https://www.freebsdfoundation.org/donate/sponsors
Or search for "Sponsored by: Netflix" in the commit messages.
>We've been working hard on stabilizing the FreeBSD IPv6 stack for production-level traffic, and I recommend that all users of IPv6 update to the latest patches in 9-stable and 8-stable. Contact me directly if you have questions about this.
Surely that work has gone back into FreeBSD and is not just for Netflix alone.
Edit: wow, I'm really getting reamed for this comment.
"We will contribute changes we make as part of our project to the community through the FreeBSD committers on our team."
BSD and MIT are trying to protect their own concept of freedom.
The same goes for VxWorks, and IOS (the cisco one).
IOS XR runs on QNX and tends to be used on routers in a carrier role.
IOS XE runs on Linux and tends to be used on service/aggregation routers.