Have to say... Your sig.. Man it is annoying to hear plebs say "forward" slash. Or when people say backslash and they are talking about a normal slash.. Sucks being a nerd sometimes..
I suppose they don't fully comprehend us humans' perception of a line leaning forward (right) and backward (left) on a 2D plane, which is pretty sad. You don't have to be smart - you just have to be, well, human. It's wired into our way of thinking. I as well can't think of how many times I've heard someone read a URL and call them backslashes.
I've preferred MacPorts/DarwinPorts because it's very similar to BSD Ports in regards to it using libraries separate from the base install, unlike the way homebrew works in regards to a number of libraries. Also MacPorts has gone a long way when it comes to having precompiled packages ready. I remember the 10.6 days and how much you compiled but now - 95% (my personal estimate) of the dependencies and target ports you're trying to install has precompiled packages for your specific Darwin version ready to go. Many times there's no compiling involved at all.
Yes, it did work after 2013. No issues that I experienced. If Cydia didn't work correctly then the jailbreak app which installs Cydia with it was faulty somehow. I remember a couple times where it didn't initially work and redoing the jailbreak would fix it. I've lost interest in it probably since iOS 11 but I actively jailbroke before then.
alt.binaries.* never went away, you just need to pay for a provider as no one is going to give you access to petabytes of data covering thousands of days of retention for free. Then there are the websites that index the content and provide generated NZBs, most of the decent ones being private these days. Binary content on usenet is very much alive and active.
As a side note, I'm pretty sure that Xorg isn't shipped on a default OpenBSD install, so it would have to be installed first from the ports.
OpenBSD install media comes with binary distribution sets xbase**, xfont**, xserv**, xshare** (** being the version number, latest being 64 for version 6.4) for installing Xorg support which you can select when you install the OS.
And I'll just add that it's annoying that on neither TFA or on this/. post is the actual setting comp-lzo specifically mentioned. You have to interpret the patch diff linked in TFA.
To disable lzo compression, make sure "comp-lzo no" is included in the config as mentioned in my parent post.
My AirVPN configs have had "comp-lzo no" in it since I've been using them so no worries about that. Looking up more info, it seems some of the AirVPN ovpn files generated for specific devices have it enabled because it would otherwise not work on that device (eh what?), but they still have lzo compression disabled on their server end so it is not used regardless.
This is probably the last pull request for 4.19 from our side.
Please remind about the gvt-fixes vs gvt-next conflict that I mentioned yesterday on drm-intel-fixes pull request.
Here goes drm-intel-next-2018-07-12: On GVT there's the addition of vGPU huge page support for guest, with one BXT fix and gvt dependency handling.
On Display side there's: - More PSR clean up and fixes (Rodrigo, DK and Tarun) - GMBUS improvements for HDCP2.2 compliance (Ram) - Fix strncpy truncation on intel_tv (Dominique) - Cleanup modesetting on load-error path (Chris)
On GEM side: - Gem init hw fix (Michal) - More selftests fixes (Michal, Chris) - Execlists optimizations (Chris) - Introduce i915_address_space.mutex (Chris) - Stolen memory support for Ice Lake (Paulo) - Unwind HW init after GVT setup failure (Chris) - Other fixes for gpu parking, gem_suspend, and handcheck reset (Chris)
drm-intel-next-2018-07-09: Higlights here goes to many PSR fixes and improvements; to the Ice lake work with power well support and begin of DSI support addition. Also there were many improvements on execlists and interrupts for minimal latency on command submission; and many fixes on selftests, mostly caught by our CI.
General driver: - Clean-up on aux irq (Lucas) - Mark expected switch fall-through for dealing with static analysis tools (Gustavo)
Gem: - Different fixes for GuC (Chris, Anusha, Michal) - Avoid self-relocation BIAS if no relocation (Chris) - Improve debugging cases in on EINVAL return and vma allocation (Chris) - Fixes and improvements on context destroying and freeing (Chris) - Wait for engines to idle before retiring (Chris) - Many improvements on execlists and interrupts for minimal latency on command submission (Chris) - Many fixes in selftests, specially on cases highlighted on CI (Chris) - Other fixes and improvements around GGTT (Chris) - Prevent background reaping of active objects (Chris)
Display: - Parallel modeset cleanup to fix driver reset (Chris) - Get AUX power domain for DP main link (Imre) - Clean-up on PSR unused func pointers (Rodrigo) - Many PSR/PSR2 fixes and improvements (DK, Jose, Tarun) - Add a PSR1 live status (Vathsala) - Replace old drm_*_{un/reference} with put,get functions (Thomas) - FBC fixes (Maarten) - Abstract and document the usage of picking macros (Jani) - Remove unnecessary check for unsupported modifiers for NV12. (DK) - Interrupt fixes for display (Ville) - Clean up on sdvo code (Ville) - Clean up on current DSI code (Jani) - Remove support for legacy debugfs crc interface (Maarten) - Simplify get_encoder_power_domains (Imre)
Icelake: - MG PLL fixes (Imre) - Add hw workaround for alpha blending (Vandita) - Add power well support (Imre) - Add Interrupt Support (Anusha) - Start to add support for DSI on Ice Lake (Madhav)
Thanks, Rodrigo.
The following changes since commit e1cacec9d50d7299893eeab2d895189f3db625da:
drm/i915: Update DRIVER_DATE to 20180620 (2018-06-20 14:10:48 -0700)
for you to fetch changes up to f7cf1a1829f9ff776fb5504c9c5ffa0e9d2baf79:
drm/i915: Update DRIVER_DATE to 20180712 (2018-07-12 23:54:26 -0700)
Well that's the most open source digital rights management I've ever seen. This is very specifically referring to direct rendering manager: https://github.com/torvalds/li...
People running OSes that come with the root account disabled. Having the root account disabled is being used as a security feature. Ubuntu follows the similar practice of disabling the root account by default, and there is no password set there either. You can of course enable it if you want but most people don't, as disabling the root account and limiting superuser actions to sudo isn't a bad idea at all. The fact that in 10.13 you're able to re-enable the root account by trying to use it with a blank password a few times is pretty upsetting and really has nothing to do with the practice of disabling root at all.
You have a weird definition of 'open source'. By your above link, I see a bunch of bsd/OSS/other open source software bits, most of them just... glue bits.
Where's the kernel?
The kernel is xnu. It's listed there. They've been releasing the source code for it since the beginning. Here have some source tarballs: https://opensource.apple.com/tarballs/xnu/
With them providing the source code - by choice by the way, since not releasing the source code would not violate the BSD/CMU licenses - is what has made it possible to modify the source and recompile for using AMD CPUs and other supported CPUs with OS X/macOS.
Firmware? Ability to build the entire OS from scratch?
By this claim (a page with some OSS bits), you'd be able to call Windows "open source" too. It has bash, and lots of other OSS bits now. So?
(NOTE: this isn't a reason to hate Apple, any more than it's a reason to LIKE Apple... you can be open source and evil, and closed source and good)
They've always kept a lot of their OS X UI closed up but running Darwin by itself and launching X11 off it for a UI (similar to Linux or *BSD) has always been an option. I'd say though since Darwin 10/11 (OS X 10.6/10.7) they've been making it harder, closing updated versions of core driver components up. Same goes for some of the other device drivers for networking cards, newer hardware etc. - in the early 10.0-10.5 days they seemed to be more open about it but they haven't been so open with new device support. It doesn't mean it isn't possible which is why devs have written many of their own drivers to support unsupported hardware. PureDarwin is the current project for running a complete OS based on the open source components of macOS and they're currently working with Darwin 16 (macOS 10.12).
You're making a very fair point but it seems most people who like to point this out don't seem to be too knowledgeable about the OS, what Apple still provides the source for, and what you can do with it.
With the cultural ignorance regarding what eating loads of junk food does to the body and the "healthy at any size/fat is beautiful" movement that the internet helped spread, it'll probably take a lot more than this to convince people otherwise.
If we're talking about the mainstream, then it's obvious - it's thin and fit sexy women and roided up hunks, which btw, usually have to have extremely defined muscles which also indicate an unhealthy body fat percentage which also means they haven't been eating much.
muscles require more calories to maintain than fat, even if you aren't working out. this is pretty common knowledge. A very muscular person has to eat enough so their muscles aren't used calories in order to reach their metabolic rate with what their body is currently trying to maintain, and this amount is farrrrrrrr more than the common caloric intake of your average, somewhat physically fit human. There is no such thing as a man who has been under-eating long term with extremely defined muscles.
Those aren't "magic filenames" - they're just device nodes that populate at boot time and unlike reserved strings like the ones in Windows, their paths have value. And that link you gave makes no reference to them. the only "filenames" that you cannot use in unix OSes are . and..
Seriously anyone here claiming that watching a movie or TV show on your mobile device is better than a good sized TV screen with quality audio is insane.
Children with weakened immune systems are very rare. How many kids at your local public school have rare immune system disorders? How many are receiving chemotherapy? Children with decent immune systems who are unvaccinated are far more common. Babies between 2 and 6 months old also have weakened immune systems, as the antibodies passed from the mother have died off and antibody production hasn't fully kicked in.
Seriously you're asking why one is different from the other? Someone who hasn't been vaccinated and has a good immune system who gets infected with certain viruses still has a fighting chance. Someone with a weakened immune system has no chance if they got infected with said viruses, let alone the weakened variants that are in vaccines.
That's why people are sympathetic to one side and critical to the other. The growing amount of unvaccinated kids are causing outbreaks and while they may have a chance of surviving, it's a death setence to a very small minority who depend on everyone else to not carry these viruses.
.. and disabling the device in Windows 10 or the BIOS isn't enough, then just remove the wireless card. If by PC you mean desktop PC, unless it's a USB wifi chip soldered onto the motherboard, it'll be a typical miniPCIe or M.2 card. Remove it. For laptops a physical switch or hotkey for disabling the wifi card at the firmware level is common, but the same goes for that. They're not soldered onto the board (with some very rare exceptions) - they're miniPCIe or M.2 cards that are removable. Whether they're easily accessible varies by laptop model, but they're still removable.
Look kids. Get over the small minded philosophical hangups. Understand that the MacBook OS is a BSD kernel + the GNU OS (tool chain) + Plus the NSstuff that Next brought. That's it. The vast majority of code is already open, because it has been developed by the community over 30 years.
the XNU kernel is an evolved version of the XNU kernel from NextSTEP that uses some BSD components, CMU Mach microkernel components and C++ I/O Kit which replaced NextSTEP's ObjC DriverKit. It's not a "BSD kernel" per say. the toolchain is definitely not GNU at all. LibSystem uses no GNU code at all. It uses the BSD standard library libc, not glibc. clang is the compiler, not gcc as that's something they got rid of many years ago. They do still use some software preinstalled that are under GPL but it's no "toolchain". See Apple’s great GPL purge.
A number of important components are completely closed which are needed to boot XNU on its own, like PlatformExpert. So you're not exactly correct in your statement here.
Forget about the closed GUI frameworks and software - Apple closed up a number of mandatory kernel extensions needed in order for XNU to boot since Darwin 9 (OS X 10.5) - this is one of the main reasons why the PureDarwin project has pretty much halted.
If you want to make an open source version of Darwin then it involves some very extensive reverse engineering. A number of tarballs for the kernel extensions that they still provide are completely outdated and many things have changed since then. The current Darwin version is 16.
The extent of the XNU source code these days is used for adding AMD CPU support for osx86.
Faking the CPUID and patching the kernel binary either through the bootloader or manually has been done forever for unsupported CPUs for Hackintoshes. We've gotten many newer Intel CPUs working before Apple added official support. It was done with Haswell-E, Sandy Bridge, and many more. Unsupported Xeon models have been fully functional as well. Apple also releases the xnu kernel source code which is how AMD CPU support has always been added. So you're wrong here - Hackintoshes run better CPUs than Macs all the time and if there's an issue getting in the way with the vanilla kernel then there's no doubt a way to get around it.
Can anyone explains why *BSD matters? It sucks. Nobody uses it. Linux is better for servers, has better hardware support, has more software, and is far better supported. Why would anyone care about any BSD system? It sure looks like *BSD is dead.
Here's a list of products that use FreeBSD or modified versions of FreeBSD:
Adara Networks Software Defined Networking products
AKIPS network monitoring system
Apple Inc.'s OS X and iOS, the core of which (Darwin) is built on the XNU kernel (part Mach, part FreeBSD, part Apple-derived code). Much of the UNIX userland tools are mostly based on FreeBSD code.
Blue Coat Systems network appliances
Calexium MailFountain is based on FreeBSD 8.1
Borderware appliances (firewall, VPN, Anti-SPAM, Web filter etc.) are based on a FreeBSD kernel
Check Point IPSO security appliances
Citrix Systems Netscaler application delivery software is based on FreeBSD
Coyote Point GX-series web acceleration and load balancer appliances
Dell Compellent enterprise storage systems (all 64-bit versions)
Isilon Systems' OneFS, the operating system used on Isilon IQ-series clustered storage systems
Juniper Networks Junos
Junos prior to 5.0 was based on FreeBSD 2.2.6
Junos between 5.0 and 7.2 (inclusive) is based on FreeBSD 4.2
Junos 7.3 and higher is based on FreeBSD 4.10
Junos 8.5 is based on FreeBSD 6.1
Junos 10.0 is based on FreeBSD 7
Junos 15.1 is based on FreeBSD 10
KACE Networks's KBOX 1000 & 2000 Series Appliances and the Virtual KBOX Appliance
LineRate Proxy appliances
nCircle's IP360 security products use FreeBSD 6.x
McAfee SecurOS, used in e.g. Firewall Enterprise (aka Sidewinder)
NetApp filers based on Data ONTAP
Netasq intrusion prevention appliances
Netflix Open Connect appliances
COMP VPN gateways, some of them certified by the Internal Security Agency for processing classified data
Panasas parallel network storage systems
Panasonic uses FreeBSD in their Viera TV receivers
Sandvine's network policy control products
Silicon Graphics International uses FreeBSD in their ArcFiniti
Sony Computer Entertainment's PlayStation 3, consumer gaming consoles.
Sophos Email Appliance
Spectra Logic nTier Verde backup appliances
Statseeker, Network Monitoring Software
St. Bernard Software iPrism web filter appliance
Symmetricom Timing Solutions
The Weather Channel's IntelliStar local forecast computer
Whatsapp
Wheel Systems FUDO and Lynx
Here's why Netflix uses FreeBSD:
FreeBSD was selected for its balance of stability and features, a strong development community and staff expertise. All code improvements, feature additions, and bug fixes are contributed directly back to the open source community via the FreeBSD committers on our team. We also strive to stay at the front of the FreeBSD development process, allowing us to have a tight feedback loop with other community and partner developers. The result has been a positive open source ecosystem that lowers our development costs and multiplies the effectiveness of our efforts.
Regardless of the FreeBSD is dead meme, it's very much actively used and companies that use it contribute to its code. NetBSD, however, is a completely different thing altogether when it comes to people using it.
Slashdot Mirror
Dongs. Just dongs.
Have to say... Your sig.. Man it is annoying to hear plebs say "forward" slash. Or when people say backslash and they are talking about a normal slash.. Sucks being a nerd sometimes..
I suppose they don't fully comprehend us humans' perception of a line leaning forward (right) and backward (left) on a 2D plane, which is pretty sad. You don't have to be smart - you just have to be, well, human. It's wired into our way of thinking. I as well can't think of how many times I've heard someone read a URL and call them backslashes.
I've preferred MacPorts/DarwinPorts because it's very similar to BSD Ports in regards to it using libraries separate from the base install, unlike the way homebrew works in regards to a number of libraries. Also MacPorts has gone a long way when it comes to having precompiled packages ready. I remember the 10.6 days and how much you compiled but now - 95% (my personal estimate) of the dependencies and target ports you're trying to install has precompiled packages for your specific Darwin version ready to go. Many times there's no compiling involved at all.
Yes, it did work after 2013. No issues that I experienced. If Cydia didn't work correctly then the jailbreak app which installs Cydia with it was faulty somehow. I remember a couple times where it didn't initially work and redoing the jailbreak would fix it. I've lost interest in it probably since iOS 11 but I actively jailbroke before then.
Bring back USENET!
alt.binaries.* never went away, you just need to pay for a provider as no one is going to give you access to petabytes of data covering thousands of days of retention for free. Then there are the websites that index the content and provide generated NZBs, most of the decent ones being private these days. Binary content on usenet is very much alive and active.
As a side note, I'm pretty sure that Xorg isn't shipped on a default OpenBSD install, so it would have to be installed first from the ports.
OpenBSD install media comes with binary distribution sets xbase**, xfont**, xserv**, xshare** (** being the version number, latest being 64 for version 6.4) for installing Xorg support which you can select when you install the OS.
And I'll just add that it's annoying that on neither TFA or on this /. post is the actual setting comp-lzo specifically mentioned. You have to interpret the patch diff linked in TFA.
To disable lzo compression, make sure "comp-lzo no" is included in the config as mentioned in my parent post.
My AirVPN configs have had "comp-lzo no" in it since I've been using them so no worries about that. Looking up more info, it seems some of the AirVPN ovpn files generated for specific devices have it enabled because it would otherwise not work on that device (eh what?), but they still have lzo compression disabled on their server end so it is not used regardless.
Source for this info: https://airvpn.org/topic/29036...
Hey bro, what is Revelations?
Allegory for the fall of Rome that many modern-day Christians interpret as prediction of a still-to-come event.
The AC is pointing out that it's called Revelation, not Revelations.
what TFA is referring to:
Hi Dave,
This is probably the last pull request for 4.19 from our side.
Please remind about the gvt-fixes vs gvt-next conflict that I mentioned
yesterday on drm-intel-fixes pull request.
Here goes drm-intel-next-2018-07-12:
On GVT there's the addition of vGPU huge page support for guest,
with one BXT fix and gvt dependency handling.
On Display side there's:
- More PSR clean up and fixes (Rodrigo, DK and Tarun)
- GMBUS improvements for HDCP2.2 compliance (Ram)
- Fix strncpy truncation on intel_tv (Dominique)
- Cleanup modesetting on load-error path (Chris)
On GEM side:
- Gem init hw fix (Michal)
- More selftests fixes (Michal, Chris)
- Execlists optimizations (Chris)
- Introduce i915_address_space.mutex (Chris)
- Stolen memory support for Ice Lake (Paulo)
- Unwind HW init after GVT setup failure (Chris)
- Other fixes for gpu parking, gem_suspend, and handcheck reset (Chris)
drm-intel-next-2018-07-09:
Higlights here goes to many PSR fixes and improvements; to the Ice lake work with
power well support and begin of DSI support addition. Also there were many improvements
on execlists and interrupts for minimal latency on command submission; and many fixes
on selftests, mostly caught by our CI.
General driver:
- Clean-up on aux irq (Lucas)
- Mark expected switch fall-through for dealing with static analysis tools (Gustavo)
Gem:
- Different fixes for GuC (Chris, Anusha, Michal)
- Avoid self-relocation BIAS if no relocation (Chris)
- Improve debugging cases in on EINVAL return and vma allocation (Chris)
- Fixes and improvements on context destroying and freeing (Chris)
- Wait for engines to idle before retiring (Chris)
- Many improvements on execlists and interrupts for minimal latency on command submission (Chris)
- Many fixes in selftests, specially on cases highlighted on CI (Chris)
- Other fixes and improvements around GGTT (Chris)
- Prevent background reaping of active objects (Chris)
Display:
- Parallel modeset cleanup to fix driver reset (Chris)
- Get AUX power domain for DP main link (Imre)
- Clean-up on PSR unused func pointers (Rodrigo)
- Many PSR/PSR2 fixes and improvements (DK, Jose, Tarun)
- Add a PSR1 live status (Vathsala)
- Replace old drm_*_{un/reference} with put,get functions (Thomas)
- FBC fixes (Maarten)
- Abstract and document the usage of picking macros (Jani)
- Remove unnecessary check for unsupported modifiers for NV12. (DK)
- Interrupt fixes for display (Ville)
- Clean up on sdvo code (Ville)
- Clean up on current DSI code (Jani)
- Remove support for legacy debugfs crc interface (Maarten)
- Simplify get_encoder_power_domains (Imre)
Icelake:
- MG PLL fixes (Imre)
- Add hw workaround for alpha blending (Vandita)
- Add power well support (Imre)
- Add Interrupt Support (Anusha)
- Start to add support for DSI on Ice Lake (Madhav)
Thanks,
Rodrigo.
The following changes since commit e1cacec9d50d7299893eeab2d895189f3db625da:
drm/i915: Update DRIVER_DATE to 20180620 (2018-06-20 14:10:48 -0700)
are available in the Git repository at:
git://anongit.freedesktop.org/drm/drm-intel tags/drm-intel-next-2018-07-12
for you to fetch changes up to f7cf1a1829f9ff776fb5504c9c5ffa0e9d2baf79:
drm/i915: Update DRIVER_DATE to 20180712 (2018-07-12 23:54:26 -0700)
Well that's the most open source digital rights management I've ever seen. This is very specifically referring to direct rendering manager: https://github.com/torvalds/li...
People running OSes that come with the root account disabled. Having the root account disabled is being used as a security feature. Ubuntu follows the similar practice of disabling the root account by default, and there is no password set there either. You can of course enable it if you want but most people don't, as disabling the root account and limiting superuser actions to sudo isn't a bad idea at all. The fact that in 10.13 you're able to re-enable the root account by trying to use it with a blank password a few times is pretty upsetting and really has nothing to do with the practice of disabling root at all.
You have a weird definition of 'open source'. By your above link, I see a bunch of bsd/OSS/other open source software bits, most of them just ... glue bits.
Where's the kernel?
The kernel is xnu. It's listed there. They've been releasing the source code for it since the beginning. Here have some source tarballs: https://opensource.apple.com/tarballs/xnu/
With them providing the source code - by choice by the way, since not releasing the source code would not violate the BSD/CMU licenses - is what has made it possible to modify the source and recompile for using AMD CPUs and other supported CPUs with OS X/macOS.
Boot scripts?
You mean launchd?
Firmware? Ability to build the entire OS from scratch?
By this claim (a page with some OSS bits), you'd be able to call Windows "open source" too. It has bash, and lots of other OSS bits now. So?
(NOTE: this isn't a reason to hate Apple, any more than it's a reason to LIKE Apple... you can be open source and evil, and closed source and good)
They've always kept a lot of their OS X UI closed up but running Darwin by itself and launching X11 off it for a UI (similar to Linux or *BSD) has always been an option. I'd say though since Darwin 10/11 (OS X 10.6/10.7) they've been making it harder, closing updated versions of core driver components up. Same goes for some of the other device drivers for networking cards, newer hardware etc. - in the early 10.0-10.5 days they seemed to be more open about it but they haven't been so open with new device support. It doesn't mean it isn't possible which is why devs have written many of their own drivers to support unsupported hardware. PureDarwin is the current project for running a complete OS based on the open source components of macOS and they're currently working with Darwin 16 (macOS 10.12).
You're making a very fair point but it seems most people who like to point this out don't seem to be too knowledgeable about the OS, what Apple still provides the source for, and what you can do with it.
With the cultural ignorance regarding what eating loads of junk food does to the body and the "healthy at any size/fat is beautiful" movement that the internet helped spread, it'll probably take a lot more than this to convince people otherwise.
If we're talking about the mainstream, then it's obvious - it's thin and fit sexy women and roided up hunks, which btw, usually have to have extremely defined muscles which also indicate an unhealthy body fat percentage which also means they haven't been eating much.
muscles require more calories to maintain than fat, even if you aren't working out. this is pretty common knowledge. A very muscular person has to eat enough so their muscles aren't used calories in order to reach their metabolic rate with what their body is currently trying to maintain, and this amount is farrrrrrrr more than the common caloric intake of your average, somewhat physically fit human. There is no such thing as a man who has been under-eating long term with extremely defined muscles.
Those aren't "magic filenames" - they're just device nodes that populate at boot time and unlike reserved strings like the ones in Windows, their paths have value. And that link you gave makes no reference to them. the only "filenames" that you cannot use in unix OSes are . and ..
https://www.youtube.com/watch?...
Seriously anyone here claiming that watching a movie or TV show on your mobile device is better than a good sized TV screen with quality audio is insane.
Seriously you're asking why one is different from the other? Someone who hasn't been vaccinated and has a good immune system who gets infected with certain viruses still has a fighting chance. Someone with a weakened immune system has no chance if they got infected with said viruses, let alone the weakened variants that are in vaccines.
That's why people are sympathetic to one side and critical to the other. The growing amount of unvaccinated kids are causing outbreaks and while they may have a chance of surviving, it's a death setence to a very small minority who depend on everyone else to not carry these viruses.
.. and disabling the device in Windows 10 or the BIOS isn't enough, then just remove the wireless card. If by PC you mean desktop PC, unless it's a USB wifi chip soldered onto the motherboard, it'll be a typical miniPCIe or M.2 card. Remove it. For laptops a physical switch or hotkey for disabling the wifi card at the firmware level is common, but the same goes for that. They're not soldered onto the board (with some very rare exceptions) - they're miniPCIe or M.2 cards that are removable. Whether they're easily accessible varies by laptop model, but they're still removable.
.. and then cover it up with an Otterbox case or something
The bundling style from OS X is an evolved version of NeXTSTEP application bundling from 1989.
Look kids. Get over the small minded philosophical hangups. Understand that the MacBook OS is a BSD kernel + the GNU OS (tool chain) + Plus the NSstuff that Next brought. That's it. The vast majority of code is already open, because it has been developed by the community over 30 years.
the XNU kernel is an evolved version of the XNU kernel from NextSTEP that uses some BSD components, CMU Mach microkernel components and C++ I/O Kit which replaced NextSTEP's ObjC DriverKit. It's not a "BSD kernel" per say. the toolchain is definitely not GNU at all. LibSystem uses no GNU code at all. It uses the BSD standard library libc, not glibc. clang is the compiler, not gcc as that's something they got rid of many years ago. They do still use some software preinstalled that are under GPL but it's no "toolchain". See Apple’s great GPL purge.
A number of important components are completely closed which are needed to boot XNU on its own, like PlatformExpert. So you're not exactly correct in your statement here.
Forget about the closed GUI frameworks and software - Apple closed up a number of mandatory kernel extensions needed in order for XNU to boot since Darwin 9 (OS X 10.5) - this is one of the main reasons why the PureDarwin project has pretty much halted.
If you want to make an open source version of Darwin then it involves some very extensive reverse engineering. A number of tarballs for the kernel extensions that they still provide are completely outdated and many things have changed since then. The current Darwin version is 16.
The extent of the XNU source code these days is used for adding AMD CPU support for osx86.
Faking the CPUID and patching the kernel binary either through the bootloader or manually has been done forever for unsupported CPUs for Hackintoshes. We've gotten many newer Intel CPUs working before Apple added official support. It was done with Haswell-E, Sandy Bridge, and many more. Unsupported Xeon models have been fully functional as well. Apple also releases the xnu kernel source code which is how AMD CPU support has always been added. So you're wrong here - Hackintoshes run better CPUs than Macs all the time and if there's an issue getting in the way with the vanilla kernel then there's no doubt a way to get around it.
Source: me - I helped support unsupported CPUs in the 10.6 kernels. http://wiki.osx86project.org/w...
Looks like wikipedia hasn't updated the list, but just like the PS3, the Sony PS4 is still running a modified version of FreeBSD 9 called Orbis OS.
Can anyone explains why *BSD matters? It sucks. Nobody uses it. Linux is better for servers, has better hardware support, has more software, and is far better supported. Why would anyone care about any BSD system? It sure looks like *BSD is dead.
Here's a list of products that use FreeBSD or modified versions of FreeBSD:
Here's why Netflix uses FreeBSD:
FreeBSD was selected for its balance of stability and features, a strong development community and staff expertise. All code improvements, feature additions, and bug fixes are contributed directly back to the open source community via the FreeBSD committers on our team. We also strive to stay at the front of the FreeBSD development process, allowing us to have a tight feedback loop with other community and partner developers. The result has been a positive open source ecosystem that lowers our development costs and multiplies the effectiveness of our efforts.
Regardless of the FreeBSD is dead meme, it's very much actively used and companies that use it contribute to its code. NetBSD, however, is a completely different thing altogether when it comes to people using it.