• 14 Posts
  • 392 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle


  • Never ask a man his pay, a woman her weight, or a data horder the contents of their stash.

    Jk. Mostly.

    I have a similar-ish set up to @Davel23 , I have a couple of cool use cases.

    • I seed the last 5 arch and opensuse (a few different flavors) ISOs at all times

    • I run an ArchiveBot for archive.org

    • I scan nontrivial mail (the paper kind) and store it in docspell for later OCR searches, tax purposes etc.

    • I help keep Sci-Hub healthy

    • I host several services for de-googling, including Nextcloud, Blocky, Immich, and Searxng

    • I run Navidrome, that has mostly (and hopefully will soon completely) replace Spotify for my family.

    • I run Plex (hoping to move to Jellyfin sometime, but there’s inertial resistance to that) that has completely replaced Disney streaming, Netflix streaming, etc for me and my extended family.

    • I host backups for my family and close friends with an S3 and WebDAV backup target

    I run 4x14TB, 2x8TB, 2x4TB, all from serverpartsdeals, in a ZFS RAID10 with two 1TB cache dives, so half of the spinning rust usable at ~35TB, and right now I’m at 62% utilization. I usually expand at about 85%






  • Kata1yst@kbin.socialtolinuxmemes@lemmy.worldArch with XZ
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    3 months ago

    Amazingly, for someone so eager to give a lesson in linguistics, you managed to ignore literal definitions of the words in question and entirely skip relevant information in my (quite short) reply.

    Both are widely used in that context. Language is like that.

    Further, the textbook definition of Stability-

    the quality, state, or degree of being stable: such as

    a: the strength to stand or endure : firmness

    b: the property of a body that causes it when disturbed from a condition of equilibrium or steady motion to develop forces or moments that restore the original condition

    c: resistance to chemical change or to physical disintegration

    Pay particular attention to “b”.

    The state of my system is “running”. Something changes. If the system doesn’t continue to be state “running”, the system is unstable BY TEXTBOOK DEFINITION.



  • What the hell did you want them to do? Are you just looking for reasons to be outraged?

    That’s boiler plate EULA language for PR/forums, which is what it actually was for in full context. Believe me, I’ve read a ton of them for my job. Is it right? No. Is it enforceable? Largely no, it won’t completely hold water if challenged in court. Is it effective at helping the legal department craft C&Ds, and terminate accounts when necessary? Absolutely. Purely a risk mitigation / CYA measure.

    And someone took issue with it. Vultr didn’t think it was an issue, but listened and took decisive, effective action anyway well before they would have been forced to. Then they made a full blog post to be transparent and owned it rather than hid from it. All in all, a pretty mature, proactive, community focused response.

    Honestly I’m impressed by it, I find the negativity baffling.


  • I think the confusion comes from the meaning of stable. In software there are two relevant meanings:

    1. Unchanging, or changing the least possible amount.

    2. Not crashing / requiring intervention to keep running.

    Debian, for example, focuses on #1, with the assumption that #2 will follow. And it generally does, until you have to update and the changes are truly massive and the upgrade is brittle, or you have to run software with newer requirements and your hacks to get it working are brittle.

    Arch, for example, instead focuses on the second definition, by attempting to ensure that every change, while frequent, is small, with a handful of notable exceptions.

    Honestly, both strategies work well. I’ve had debian systems running for 15 years and Arch systems running for 12+ years (and that limitation is really only due to the system I run Arch on, rather than their update strategy.

    It really depends on the user’s needs and maintenance frequency.




  • Disingenuous how? You don’t think Linux solved a real day to day need of it’s first users?

    Sure, from Torvald’s perspective, it was a project specifically to solve a small problem he had. He wanted to develop for a nix platform, but Minix wouldn’t work on his hardware, and the other *Nixs were out of reach.

    And this was generally true in the market as well. Linux arrived just in time and was “good enough” to address a real gap, where Minix was limited in scope to basically just education, Hurd was in political development hell, and the other Nixs were targeted at massive servers and mainframes. Linux filled the “*Nix for the rest of us, inexpensively” niche, eventually growing in scope to displace its predecessors, despite their decades of additional professionalism and maturity.

    That niche is now filled, the gap no longer exists. A “New Linux” wouldn’t displace Linux, because the original already suits the needs we have well enough. This is precisely why the BSDs and Solaris were “too little, too late”. They were in many ways better than Linux, but the problems they solve compared to Linux are tiny and highly debatable. Linux addressed a huge, day to day need of people who were motivated to help.