When you install a package with Nix, all you are doing is drop a symlink in your ~/.nix-profile pointing to some /nix/store/ item.

When you build a package with Nix (also does not require root privileges), it happens inside a container that can only write to /nix/store/.

The is a cryptographic hash based on all the inputs (dependencies) to the package (also /nix/store/ items) as well as the build script.

Indeed the similarity with Ganeti is only on the surface: being a scalable infrastructure management tool, DRBD as a first-class supported disk backend, etc.

The cluster replication and consensus model is very different: Ganeti has a single "master" node that makes all the decisions and replicates cluster state to other nodes.

Thanks for checking the dates, I thought Proxmox was newer.

Googles Ganeti is strikingly similar to Proxmox, to the point where I suspect Proxmox started as a reimplementation:

http://www.ganeti.org/ (developed at https://github.com/ganeti/ganeti)

It does not come with a GUI, though there are a few third party ones. It has API endpoints for everything, a fully featured CLI client, and is extremely stable.

Googles marketing department does not want you to know this, but Ganeti runs most of its internal infrastructure (not public facing stuff).

No affiliation, just a happy user.

https://bugs.python.org/issue40018

And broke the ABI in 1.0.2g:

https://bugzilla.redhat.com/show_bug.cgi?id=1313509

I don't mean to bash on OpenSSL here and agree they generally do an exceptional job at keeping the public interface stable. Just offering some context. These things are difficult.

I hear Nix even works on macOS too! :-)

There is a maintained nonfree Guix channel here if you don't care about such blobs or need other proprietary software: https://gitlab.com/nonguix/nonguix

Here is a technique I have developed after many years of almost daily brewing. I call it the "30-30-30" (anyone get the reference?), but each step has a lot of room for variance, no timer necessary.

* Mount the AeroPress on a 3dl mug and add ~17g of medium-coarse freshly ground coffee.

* Add 20-30g of hot water to let it "bloom", which releases CO2 and other gases trapped in the beans from the roasting process. Leave it for 15-30 seconds until most bubbles have popped (if any). Very fresh beans should bloom longer.

* Pour water up to just above the 4 mark. I like to spin the AeroPress while pouring to stir it, but you can also pour in circles like a pour-over. Try to make it foamy by having the water break just before it hits.

* Let it drip for ~30s (or until the water level is just above the 3 mark).

* Slowly plunge for another 20-30s.

That's it! The water temperature should be between 85 and 95 °C; any hotter will burn the grounds and lower temperatures won't be able to extract as much flavour.

Comments URL: https://news.ycombinator.com/item?id=21564430

Points: 2

# Comments: 0

It was released under a Creative Commons license on recommendation from the EFF, so that the U.S. House of Chambers could not stop it (yes, they tried!).

The movie is a documentary of sorts, featuring two people who go to conferences posing as high-profile businesses, promoting oft-ridiculous products to make a point...the only problem is, people keep taking them seriously (even Halliburtons SurvivaBall).

At one point they end up live on BBC news and inadvertently wipes $1B+ off a companys public stock value.

It is hilarious, and well worth the watch.

Comments URL: https://news.ycombinator.com/item?id=19965778

Points: 75

# Comments: 32

Each of these "artifacts" are actual isolated builds of complicated programs such as Chromium or GCC. The technical term is "derivation", which produce "outputs".

All of those packages can be reproduced from source now or 100 years into the future and SHOULD produce the exact same binary output. If they don't, it's a bug.

I maintain my own build farm and tried comparing my results against the official CI server:

  $ guix challenge --substitute-urls="https://ci.guix.info"
  14,224 store items were analyzed:
    - 4,972 (35.0%) were identical
    - 265 (1.9%) differed
    - 8,987 (63.2%) were inconclusive

All of these items can be (and have been) built entirely from source, starting with Guix' initial "binary seeds", on (probably) different hardware and kernel compared to the CI system.

Comments URL: https://news.ycombinator.com/item?id=18946694

Points: 1

# Comments: 1

  wget https://git.savannah.gnu.org/cgit/guix.git/plain/etc/guix-install.sh
  sudo bash guix-install.sh

The vast majority of Guix users are on other (so-called "foreign") distributions (i.e. not GuixSD) -- I think the opposite is true for Nix/NixOS.

I'm not sure what's "sticky" about it, can you elaborate?

Comments URL: https://news.ycombinator.com/item?id=18620263

Points: 4

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=18278424

Points: 4

# Comments: 0