- codeberg.org/cerement
- cerement.codeberg.page
- @cerement@social.targaryen.house
- he/him or your choice of neutral
- header credit – Randall Mackey, The Lonely Cosmonaut
- 2 Posts
- 7 Comments
Joined 2 years ago
Cake day: June 10th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
For the young the days go fast and the years go slow; for the old the days go slow and the years go fast.
—Anna Quindlen, Lots of Candles, Plenty of Cake (2012)
cerement@slrpnk.netto
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com•Good old Finland (subtitle is commentary, not in text)English
2·1 month ago(paraphrased) “The user of the illegal service may fund the activities of criminal organisations, says Executive Director Jaana Pihkala from the copyright organisation TTVK.”
as opposed to paying the even more criminal publishers scalping the rights and screwing the creators
cerement@slrpnk.netto
Asklemmy@lemmy.ml•Reddit Exodus lead me to Lemmy and i am realy happy about it. Where should GitHub Exodus lead me to?
0·3 months ago- Codeberg
- sourcehut
- radicle
- self hosted
cerement@slrpnk.netto
Linux@lemmy.ml•What's up with all these immutable distributions? What are the benefits and disadvantages of them?
1·2 years agothe whole concept of immutable is focused on stability and safety of your system – yes, it is still possible to break an immutable distro, but it’s a LOT harder and takes some actual effort – there’s also a few concepts wrapped up into the “immutable” phrasing:
- immutable filesystem – the root filesystem is set as read only, updates are queued up and applied during an upgrade (some distros require a reboot, some don’t)
- VanillaOS keeps two copies of the root system (ABroot), upgrades the inactive copy and then swaps them out
- NixOS has everything defined in a master config file and keeps an archive of previous generations of the config file allowing you to boot into whichever generation you want
- atomicity – updates are applied individually and checked, if the update breaks then it’s reverted to the previous working state (ie. you are never left with a borked system)
- containerized apps – user space apps isolated or sandboxed in some way like Flatpaks or Docker containers or OCI so if they break, they don’t take anything else down with them
- declarative systems – the whole system (and packages and configs) are defined (declared) in one master config file – back up that config file and if something happens to your system, you just need that one file to do a full rebuild (or make an identical copy of your system on another computer) – NixOS and GNU Guix are the two more well-known in this space
- EDIT: minor side-effect of this is you can easily tell exactly what packages are installed on your system at any given time – no hunting through
historyor trying to remember what you installed last month when you were testing out video players
- EDIT: minor side-effect of this is you can easily tell exactly what packages are installed on your system at any given time – no hunting through
- immutable filesystem – the root filesystem is set as read only, updates are queued up and applied during an upgrade (some distros require a reboot, some don’t)






Project Cybersyn