XPost: alt.comp.os.windows-11, comp.os.linux.advocacy, comp.sys.mac.advocacy   
   From: brock.mcnuggets@gmail.com   
      
   On Nov 20, 2025 at 4:19:00 PM MST, "Lawrence D´Oliveiro" wrote   
   <10fo7l3$39kk9$7@dont-email.me>:   
      
   > On 20 Nov 2025 20:42:14 GMT, Brock McNuggets wrote:   
   >   
   >> On Nov 20, 2025 at 1:18:07 PM MST, "Lawrence D´Oliveiro" wrote   
   >> <10fnt1v$36q3t$2@dont-email.me>:   
   >>   
   >>> On 20 Nov 2025 15:34:05 GMT, Brock McNuggets wrote:   
   >>>   
   >>>> On Nov 19, 2025 at 9:35:55 PM MST, "Alan" wrote   
   >>>> <10fm5rb$2ni8b$1@dont-email.me>:   
   >>>>   
   >>>>> macOS has no Linux sub-system.   
   >>>>   
   >>>> Right... it has a virtualization system.   
   >>>   
   >>> Apple made a big deal about some kind of “lightweight   
   >>> virtualization” where the Linux kernel is shared among the Linux   
   >>> instances.   
   >>>   
   >>> Linux calls this “containerization”. Apple is making a big deal   
   >>> about a feature that they didn’t have to do any work to implement,   
   >>> because Linux already provides it for free!   
   >>   
   >> That’s not really what’s going on. Apple isn’t hyping a “Linux   
   >> feature they get for free.” They’re using macOS’s virtualization   
   >> stack to run full Linux instances, with some clever memory sharing   
   >> so multiple guests don’t store identical kernel pages.   
   >   
   > That’s what Linux “containers” do -- like I said.   
      
   Containers are not full VMs.   
      
   > They let you run   
   > multiple entirely independent userlands under the same kernel. Linux   
   > already gives you that for free: all that “clever memory sharing”   
   > among “multiple guests” is something Linux is doing, not macOS!   
      
   Independent userland is not the same as a VM.   
   >   
   >> Linux supports this, sure, but the host still has to handle   
   >> scheduling, memory management, I/O, and security boundaries — that’s   
   >> Apple’s work, not something handed to them.   
   >   
   > Linux already has superior capabilities for that,   
      
   We can debate which is better, but macOS is handling that in macOS.   
      
   > for isolating   
   > containers one from the other. They can have different filesystems   
   > visible, different network interfaces (with different LAN visibility),   
   > different sets of running processes in different IPC namespaces --   
   > Apple doesn’t have to do any work to get all that, beyond having its   
   > marketing department somehow suggest that Apple deserves the credit   
   > for all this.   
      
   macOS is not using a container but a VM.   
   >   
   >> And they’re not “making a big deal” out of it.   
   >   
   > More kind of embarrassed about having to embrace Linux, then?   
      
   Do you understand what open source is? LOL! Heck, do you understand how much   
   of macOS is open source? Even Darwin is open source.   
      
   --   
   It's impossible for someone who is at war with themselves to be at peace with   
   you.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)