this post was submitted on 02 Jan 2024
91 points (87.0% liked)

Linux

48008 readers
1424 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] toothbrush@lemmy.blahaj.zone 19 points 10 months ago* (last edited 10 months ago) (2 children)

cool article! However, counterpoint: What is a flake?? The article doesnt say...

Is it like a makefile?

[–] Euphoma@lemmy.ml 8 points 10 months ago (1 children)

Nix flakes are a feature of the nix package manager to make nix packages more reproducible.

[–] toastal@lemmy.ml 3 points 10 months ago (1 children)

Wut. It’s just as reproducible, flakes are mostly just a common unifying API with some extra CLI sugar for usability.

[–] Atemu@lemmy.ml 6 points 10 months ago (1 children)

While that is true, it's also r13y on another level: Reproducible evaluation. That mostly stems from pure eval and locking.

In the "before times", you'd get your Nix expressions from some mutable location in the Nix path, so running i.e. a nixos-rebuild on your configuration could produce two different eval results when ran at two different times, depending on whether anything about your channel configuration changed in the mean time. This cannot happen with flakes as all inputs are explicitly given and locked.

You could achieve the same using niv etc. before but that had its own issues.

[–] toastal@lemmy.ml 2 points 10 months ago (1 children)

It was usually recommended to lock to inputs anyhow with all the fetchers requiring a hash which I hated having to manually update & like the UX flakes provides (I really wish they supported more than Git & Mercurial tho). You can still have different evals tho if you point to latest.tar.zstd or other non-hashed thing like a branch where the referred to can change & it won’t reproduce. I haven’t used channels in years, but doesn’t that just refer to the running system, not using Nix to build projects?

[–] Atemu@lemmy.ml 1 points 10 months ago (1 children)

I haven’t used channels in years, but doesn’t that just refer to the running system, not using Nix to build projects?

I have no idea what you're trying to say here.

[–] toastal@lemmy.ml 1 points 10 months ago (1 children)

Aren‘t channels for NixOS, and you’d use overlays for building packages? Now you can do that all with flakes.

[–] brukernavn@lemm.ee 2 points 10 months ago

No, channels are a simply a mechanism for managing what's in your NIX_PATH.

[–] Samueru@lemmy.world 2 points 10 months ago

A flake from cornflakes