HSVSphere
45.6K posts

HSVSphere
@HSVSphere
A colorful sphere, here to grudge. Its opinions will never budge. A vibrant orb, with hues so bright, Unwavering in its stances and might.
The Chromatic Citadel Katılım Ağustos 2024
979 Takip Edilen19.1K Takipçiler

Mosh + native ssh sessions are all you need. And you only need mosh because ssh doesn't use QUIC.
Tmux is a bad idea.
Nick Khami@skeptrune
it frustrates me to no end that making "know how to use tmux and a vps" a job requirement would make it impossible to hire people so many of the "software engineers" in our industry are completely uninterested in pursuing excellence
English

Life is lifegem
† lucia scarlet 🩸@luciascarlet
Life is awesome! 🤩 I love being alive so much! 🌞
English
HSVSphere retweetledi

@uwukko can helium remove the checks that Chromium does to prevent phising stuff that writes to the policy as an opt in? on macos it refuses some policy settings (such as default browser, extension installation not from chrome store, etc) if you don't have a corporate profile installed. this is quite bad for declaratively managed stuff

English

@HSVSphere @maria_rcks this genuinely has to be the worst bug of all time😭 genuinely why is it even like that
English

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
East River Source Control@erscio

@jakesicles Next you're going to ask why they have little fat bellies they're shaking around in a kawaii way
English

HSVSphere retweetledi

@NekoWitchMary I'm aware of microvm.nix, but this is for a real host OS
English

@HSVSphere Dunno what you're doing, but take a look at microvm.nix project. It's too bloated overall, but it has some awesome ideas you can borrow.
If you want something super minimal system,
but still enough to self-build itself, you probs need registration info.
#L104" target="_blank" rel="nofollow noopener">github.com/microvm-nix/mi…
English

@buckberi @TK_HelpDesk Kardeşimin laptopda Fedora 44 var, denedim giriş oluyor Firefox'da. Network sekmesinden ne olmuyor diye kontrol ettimiz mi?
Türkçe

The way nix reclaims storage is by garbage collecting the /nix/store. And for garbage collection, you need some form of gc roots to determine what to keep. On NixOS, the roots will be 1) your working system 2) previous rollback systems 3) other nix-built stuff being referred to on the fs or by live processes.
You can remove these roots, and then run `nix store gc`. There's a helper nix-collect-garbage --delete-old that removes all systems other than the current one and the one before that, then runs the GC. You can also do --delete-older-than, which should not be hard to guess what it does
English

my main worry would be disk space. there needs to be a way to prune history (including pruning bad tangents that you abandon)
In my work on enterprise level storage systems, I've seen more grief caused by snapshots than you would easily believe, and on a badly designed system, the problem is hard to eliminate without throwing away all of your history (eliminate one snapshot and the changes just roll to the next one)
you need a way to re-write the history while leaving out some of it.
yes, disks are huge today (my first pc had a 70M drive, of which I could only use 60m with dos because of the 1024 cylinder limit, my earlier z80 machines used cassette tapes), but it's still too easy to fill them up if you do too much experimentation.
English

One of the consequences of looking through the possible alternatives for a new Linux distro: I now believe that easy rollback is a thing that Cannot Be Unseen. In a good way!
NixOS people can get a bit fanatical and weird about this, but I now think they're essentially correct. Once you grasp what it's like for your software installation's history to be a series of snapshot states, any one of which you can revert to at any time to back out of an update problem, it starts to seem silly and self-sabotaging to not have that.
I don't know if NixOS or some other distribution fundamentally built around this concept is going to win. I do think we're going to see a trend towards package managers turning into system-snapshot managers. Setups functionally like pacman + snapper + limine will become the normal out of the box experience rather than optional extras.
Because... Cannot Be Unseen. Once you know this is possible, why on Earth would you *not* do it?
English

No, not "snapshot managers". You don't need snapshots if your system is build properly. It's similar to using immutable datastructures (like trie maps) for your app state, and for "rollbacks" you just keep around tips of the old systems. No snapshotting, as every new system means a new state (in NixOS, this is a Nix store path & its deps)
Relying on filesystem snapshots for this means you haven't solved this on the fundamental level and are coping by bundling the base system with other data in snapshots. Nix(OS) and Guix are input/content addressed so they solve this better.
English















