#office-hours (2019-07)

Public #office-hours starting now! Join me here: https://zoom.us/meeting/register/dd2072a53834b30a7c24e00bf0acd2b8

Have any questions? This is your chance to ask us anything.

missed it today, had a meeting conflict.

https://sweetops.slack.com/archives/CCT1E7JJY/p1563318580146300

@Blaise Pabon I finally remembered the OS… it’s called NixOS

What was the the name of the sandbox style package manager for red hat?

Oh! I remember nixOS! my old boss Ariya is a huge fan of their package manager Nix

Yep!

OK, so the redhat OS package manager is ostree

for the system image

Do you know how ostree compares to nix? Or is it apples to oranges

and the next-gen package manager for applications is called flatpak.

Sooo… ostree is for the system image

https://ostree.readthedocs.io/en/latest/manual/related-projects/#nixos-nix

right and NixOS has a similar approach to system images of NixOS.

rpm-ostree is for RHEL style os

actually the genealogy is more like this:

CoreOS begat ostree (which is mostly found on RedHat systems)

NixOS begat nix (although now nix runs on other OS, including Mac OS!)

IF you’re booting NixOS, then nix can manage your system images.

If you’re booting CoreOS, then ostree will manage your system images.

…and since CoreOS has tight collaboration with Fedora and RHEL, the ecosystem of .rpms is ported over…. whereas there are fewer nixOS binaries and some packages you will have to build from source.

I suspect that NixOS will become the NetBSD of the devops world: bombproof, stable, late to adopt. and CoreOS/OStree will become the RHEL of the Enterprise world.

Don’t get me wrong, ‘nix is a very kickass solution if you are switiching beteween monolithix development environments (python, Java) where a sdk version can mean a whole different set of dependencies.

@here Public #office-hours with cloud posse starting now! https://zoom.us/s/508587304 join if you have any questions or want to listen in.