Eskating cyclist, gamer and enjoyer of anime. Probably an artist. Also I code sometimes, pretty much just to mod titanfall 2 tho.

Introverted, yet I enjoy discussion to a fault.

  • 14 Posts
  • 767 Comments
Joined 3 years ago
cake
Cake day: June 13th, 2023

help-circle

  • I mean if they can really just do nothing, then that is also something it would be good to be sure about.

    Nintendo has shown that it is possible to attack open source projects at the repository level, and while that wouldn’t necessarily stop development, it would be a step down to force development technically “underground”.

    And if instances have to start being regularly replaced, that WILL cause attrition.




  • But there are no hacks required to install it on old hardware.

    Yes there are.

    If you used rufus or ventoy, you’ve just applied them without knowing.

    Unmodified Windows 11 ISOs will refuse to install on any hardware with a CPU older than Ryzen 3000 or Intel 8000.

    In fact there are less hacks required to install / upgrade to windows 11 then there are to install any Linux distro.

    What?

    On the vast majority of systems, the vast majority of linux distros will install and run with zero “hacks” of any kind. Literally just boot the ISO as-is and have at it.

    genuine copy of windows will receive all and any updates

    No. On many machines, while windows will install just fine due to the modifications to the installer applied by rufus/ventoy, the yearly major version updates can fail catastrophically.

    A lot of hardware will update without issue, but there ABSOLUTELY is risk.

    Windows is just an os. As long as it is compiled for the correct CPU architecture, it is just as supported as any other hardware. The hardware is supported by individual drivers, normally provided by the hardware manufacturer, not Microsoft.

    You are confusing functional, and supported.

    Something can “technically still work” without being officially supported.

    Not being supported means Microsoft can make breaking changes in updates, because they made no promises your hardware would be accounted for in the future.

    Just because it works today, no longer means it will tomorrow.


  • Every year or so.

    My NAS is self-built.

    I used to buy one more drive whenever my pools would start getting full. I’m now in a place where I can discard data about as fast as I get more to store, I don’t predict needing new drives until one fails.

    I’ve re-arranged my volumes to increase or decrease parity many times after buying drives or instead of buying drives.

    Mergerfs makes access easy, the underlying drives are either with or without parity pairs, and I have things arranged so that critical files are always stored with mirroring, while non-critical files are not.


  • I rather enjoy the added storage capacity.

    So do I.

    It’s just that I use btrfs, mergerfs, or lvms to pool storage. Not RAID.

    Making changes to my storage setup is far easier using these options, much more so than RAID.

    Mergerfs especially makes adding or removing capacity truly trivial, with the only lengthy processes involved being bog-standard file transfers.

    Hard drive storage is pretty cheap. And the effort it takes to make changes to a raid volume as my needs change over the years, just isn’t worth the savings.


  • Rebuilding parity requires processing power. Copying a mirror does not.

    There’s also the fact that the rebuild stresses the drives, increasing the chance of a cascade failure, where the resulting rebuild after a drive failure, reveals other drive failures.

    It all results in management overhead, which having to “just tweak some parameters” makes worse, not better.

    In comparison to simple mirroring and backing up offsite, RAID is a headache.

    The redundancy it provides is better achieved in other ways, and the storage pooling it provides is better achieved in other ways.










  • Yes. But you don’t have to switch.

    People say “start” with simpler distros because if you go past just using it as-is, and grow to understand linux closer to the system level, you’ll likely eventually end up preferring something more complex.

    There’s little point to starting at the deep end, like arch, since you don’t know whether you’ll end up staying in the shallows yet. Either way, it’s the start. It can also be the end, but that is unknowable.


  • The closest thing I can think of, is Soulseek.

    You can find almost anything on there. People share their entire collections, and almost everyone has some niche stuff they like.

    I’ve spent hours exploring other people’s curated libraries, finding stuff I’ve never heard.

    I don’t see how this would work financially, tho. Soulseek doesn’t make anyone money, except when i go out of my way to buy something on qobuz or bandcamp when I really like something.

    Music is art. Like visual artists, it’s simple enough for one or a couple people to produce, but unlike visual art, it’s less commonly done on comission. Which means freely sharing your music, doesn’t typically put food on the table.

    Hence, musicians sell albums or singles. Preferably directly to their fans. Souncloud, YT, and Soulseek regularly help me find new artists I like… But for actual listening I pull up Symfonium, hooked up to my Jellyfin server, serving my carefully curated personal collection.


  • Sorry, I must’ve misremembered about systemd. It’s how my installs start up, and the unit file is not in the usual location for systemd units I’ve created myself, so my assumption was it came with Kopia. There is no systemd timer though, and one isn’t needed.

    Edit: Just confirmed no systemd file came with kopia on my system either, my mistake.

    in the past week, it did not backup anything. Hence, there is no scheduler built into kopia automagically as described/ hinted in the docs.

    Was Kopia running during that time?

    If you run a Kopia command, then it will perform the instructed task, and then exit. It will obviously not do anything after completing whatever command was given, as the process will have exited, leaving no kopia process running on the system. This is for when you use it in cron or your own scripts.

    The other way of doing things is to run it in server mode kopia server start, which will set it running as a background daemon. When running, it allows you to log into the web interface or configure it via cli to do whatever you like. And as long as the process starts along with the host system, that’s all there is to it.

    How the daemon is set up to start, doesn’t really matter.