Thicket data repository for the EEG
anil.recoil.org
1{
2 "id": "https://ryan.freumh.org/2024-02-05.html",
3 "title": "5 Feb 2024",
4 "link": "https://ryan.freumh.org/2024-02-05.html",
5 "updated": "2024-02-05T00:00:00",
6 "published": "2024-02-05T00:00:00",
7 "summary": "<div>\n <span> Previous: <a href=\"2024-01-29.html\">29 Jan 2024</a> </span>\n <span> Next: <a href=\"2024-02-12.html\">12 Feb 2024</a> </span>\n </div>\n \n \n\n <h3>Shark</h3>\n<p><span>I spoke to Michael about\nVanillaOS:</span></p>\n<blockquote>\n<p><span>It uses OCI images and ABRoot to provide\nimmutability and atomic updates. Iirc it’s similar to Fedora Silverblue\nin that it’s an ‘immutable’ operating system, but Silverblue uses OST\nwhich is a ’git for binaries (keeps track of metadata and I think GCs).\nThis is also used by flatpak.</span></p>\n<p><span>Nix is a bit more general in that is allows\ntwo packages to have different versions of a dependency by specifying\nthem be absolute path rather than hard linking like ABRoot/OSTree. NixOS\nmodules make it system configuration version controlled and\nrollback-able, and you don’t have to deal with ‘configuration updates’\nlike e.g. Ubuntu prompt you with. The downside is that you need to write\nyour system config in this esoteric DSL.</span></p>\n</blockquote>\n<p><span>I think there’s something in ‘Nix for data’,\nsomething that came up from <a href=\"https://nlnet.nl/\">nlnet.nl</a> in\nthe NixOS room at…</span></p>\n<h3>FOSDEM</h3>\n<p><span>I attended FOSDEM and wrote up some notes <a href=\"./fosdem.html\">here</a>!</span></p>",
8 "content": "<div>\n <span> Previous: <a href=\"2024-01-29.html\">29 Jan 2024</a> </span>\n <span> Next: <a href=\"2024-02-12.html\">12 Feb 2024</a> </span>\n </div>\n \n \n\n <h3>Shark</h3>\n<p><span>I spoke to Michael about\nVanillaOS:</span></p>\n<blockquote>\n<p><span>It uses OCI images and ABRoot to provide\nimmutability and atomic updates. Iirc it’s similar to Fedora Silverblue\nin that it’s an ‘immutable’ operating system, but Silverblue uses OST\nwhich is a ’git for binaries (keeps track of metadata and I think GCs).\nThis is also used by flatpak.</span></p>\n<p><span>Nix is a bit more general in that is allows\ntwo packages to have different versions of a dependency by specifying\nthem be absolute path rather than hard linking like ABRoot/OSTree. NixOS\nmodules make it system configuration version controlled and\nrollback-able, and you don’t have to deal with ‘configuration updates’\nlike e.g. Ubuntu prompt you with. The downside is that you need to write\nyour system config in this esoteric DSL.</span></p>\n</blockquote>\n<p><span>I think there’s something in ‘Nix for data’,\nsomething that came up from <a href=\"https://nlnet.nl/\">nlnet.nl</a> in\nthe NixOS room at…</span></p>\n<h3>FOSDEM</h3>\n<p><span>I attended FOSDEM and wrote up some notes <a href=\"./fosdem.html\">here</a>!</span></p>",
9 "content_type": "html",
10 "categories": [],
11 "source": "https://ryan.freumh.org/atom.xml"
12}