[HN Gopher] Adventures of Linux Userspace at Meta [video]
       ___________________________________________________________________
        
       Adventures of Linux Userspace at Meta [video]
        
       Author : iso8859-1
       Score  : 53 points
       Date   : 2024-01-06 19:02 UTC (3 hours ago)
        
 (HTM) web link (media.ccc.de)
 (TXT) w3m dump (media.ccc.de)
        
       | theyinwhy wrote:
       | Meta at CCC, I did not think that was possible.
        
         | jaeckel wrote:
         | Their media hosting platform is used by many conferences.
         | That's a video of a non-CCC conference, called asg, earlier in
         | 2023, not to be confused with the recently held congress or
         | other CCC headlined events.
        
         | dontupvoteme wrote:
         | It's changed a lot in the last few years.
         | 
         | Rather captured one might say.
        
         | pengaru wrote:
         | Meta was a primary sponsor for the most recent all-systems-go,
         | and employs several folks contributing upstream to systemd.
         | 
         | Also note Lennart is no longer even at RedHat, he's at
         | Microsoft nowadays. I'm surprised Microsoft wasn't a major all-
         | systems-go sponsor alongside Meta...
         | 
         | There's been a lot of earth shifting under these projects, for
         | better or worse.
        
       | JustAPerson wrote:
       | Slides: https://cfp.all-systems-go.io/media/all-systems-
       | go-2023/subm...
        
       | pixelbeat__ wrote:
       | It's worth noting that this discusses the centos based
       | provisioning and hardware management platform.
       | 
       | The actual distribution used to _run_ all Meta backend services
       | is completely separate and built from source (it does share the
       | kernel). This is done for flexibility, performance, service
       | isolation reasons
        
       | otterley wrote:
       | I'm curious as to why Meta settled on CentOS Stream. Isn't that
       | unstable by design? How do they manage change in such a system?
       | What are its benefits and drawbacks vis-a-vis the alternatives?
        
         | leoh wrote:
         | It may be due to them testing fairly rigorously before
         | deployment and thereby benefitting from the latest kernel
         | security patches, for example. Google does something similar
         | with Debian internally on workstations.
        
         | matthews2 wrote:
         | CentOS Stream isn't unstable in the way that something like
         | Arch Linux or Debian Sid is.
         | 
         | They effectively only got rid of point releases. Instead of
         | going from CentOS 7 to 7.1, you just regularly get updates.
         | Since they're a part of the same major release, they don't
         | contain breaking changes.
         | 
         | It's no different from running Debian Stable with the -updates
         | repository enabled.
        
           | elromulous wrote:
           | Just to add to this. It's basically a way to get a rolling
           | release.
           | 
           | Google did the same thing with Debian and rodete (ROlling
           | DEbian TEsting).
           | 
           | https://cloud.google.com/blog/topics/developers-
           | practitioner...
        
       | brcmthrowaway wrote:
       | Out of 1 million standard LAMP stack machines, how many will
       | randomly fail?
        
       ___________________________________________________________________
       (page generated 2024-01-06 23:00 UTC)