Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)C
Posts
0
Comments
235
Joined
3 yr. ago

  • Yes corrected. But I still can never remember what the correct spelling for this is, I actually thought about it. That was the one my keyboard picked with swyping so I just left it...

  • Wether or not that's a plus or minus depends on perspective.

  • I fundamentally dislike the concept of flatpacks. It's fine and/or necessary for immutable distros, but I see little point in loading every dependency individually for every app. It's fine for an app or two, but adds up to a lot relatively quickly when used as the default system. To each their own I guess, but I'm very happy with the ecosystem of the huge, up-to-date native repo + availability of the AUR.

  • This is just complete and utter nonsense.

  • It just is a real alternative by now. Has been for a while. I have no idea why they say "getting closer".

    If you want to just try it out, there nothing stopping you. Most distros allow you to just live-boot and use it without installing. It install into a 2nd boot SSD (a 30$ 128gig is fine), so you can dual boot.

    I would not recommend the frequently recommended Mint though, as is somewhat outdated advice. It's good advice for people who just use a computer, but not really "power users". As a power user myself, who switched relatively recently, I am incredibly happy i went with CachyOS. While also targeted at gaming, it just works very well for any use case and being incredibly polished and honestly stable (despite being based on Arch, which is a rolling release). It's also very well setup to run Windows apps in general if the need arises. Wine and associated tools are there and available as optimized packages (with some selected patches).

  • I don't know what the time frame or interval of these events is. I switched to CachyOS 5+ months ago now, updated in the evening before going to bed (basically daily, bleeding edge as you might say).

    I had zero issues. Maybe it'll be an issue one day. But while I could check for any critical known issues, and that would be an extra step (I don't, so it's not), it has saved me so much time just having up to date packages on literally everything just in the repo. It's insane compared to especially Debian, where things can be years behind and the only way to get a reasonable recent version is to build from source, find a .deb repo for it or install a manually downloaded package directly (like on Windows).

  • Yes. That's basically the point. They call it a "drop in replacement", but last I used it manually there were some extra steps for what I wanted to do. To be clear: not for every thing you want to setup, just one if the things I read don't up required extra steps. But I also hear that those things have changed since then and it's mostly seamless now.

  • Especially without any additional context or knowledge about their background, directed at someone clearly only starting out, this is incredibly bad advice.

    Edit: typos (italic), sorry that was probably hard to read.

  • Proxmox and Docker don't really do the same thing. They live in the same area, but the coverage is very different. You can always use docker when your host is running proxmox: either individually or in groups inside of an lxc, or all in w dedicated VM, or even natively on the same house if you prefer chaos. But you can't do the opposite: Sometimes you just need a VM. Maybe you only need a couple of devices, and you know they run on or are even designed for docker, then that's the better option. In all other cases, and when just getting started, proxmox is just the way more universal solution if you're only planning on having a single host (for now).

    The management tools in proxmox are great. The community scripts are a fantastic resource and only work with proxmox. I would suggest you set it up natively, not on top of Debian though, even if that's already installed. Not the least of the reasons are to be able to use ZFS easily, including on on the boot partition (select that in the installer).

    Finally, if you're gonna stick with docker, like others said: consider podman. That really does the same thing docker does, but it's fully open source. Arguably it's better in some areas, but on the flip side might, in occasion, require fiddling with something intended specifically for docker and using advanced setups.

    Also there really is no wrong answer, either. And you can always change whatever you choose.

  • Ironically, many Europeans could drive through it with their vehicle. Actual Americans, probably less so...

  • If I remember right, problems of that type are either NP-Complete or even NP-Hard, meaning they are incredibly hard to compute and/or don't have a known solution. They have been studied for centuries, so there should be ample scientific research (see the links the other commenters posted already), but my point is a "perfect solution" probably isn't a realistic goal. I would aim for an approximation that's "good enough" for your use case.

  • Weird, my desktop interface isn't any of those things. Huh.

  • You don't need to hard update your IP every 5 minutes. The typical DNS updaters (just use ddclient) can simply check if your IP is up to date and only update if it isn't.

  • I have a love-hate relationship with it. Due to work reasons I'm more familiar than I want to be with tortoiseSVN, and the git version is similar enough to feel at home. But that's also it's biggest downfall: it does a lot of things the "SVN way" despite being a git client. The workflow can be kinda made to work, but it always feels like it's not a native git tool, because it isn't. I would go so far as to say that it encouragedrl bad habits on git, especially for those used to tortoiseSVN.

  • I actually have. A can of tomatoes is (or at least was back then) cheaper than a pack of pasta, and can also last for more than 1 or even 2 servings. If I add (just) butter to the pasta, I'm making it worse because I'm one of the seemingly 5 people on earth who don't like butter.

    But my comment was meant for pasta with (any) sauce, see my other reply.

  • Yes my statement was probably a bit too broad. I meant any pasta with a sauce you generally don't want butter (or oil) on, as it causes the sauce to stick less to the pasta. Which is the whole point of having the sauce in the first place.

  • If you're doing anything with pasta that involves butter you're doing it wrong, but you do you.

  • ARC is the in-memory cache used by ZFS. If it's completely off the effect can be dramatic. Under no circumstances should a larger cache cause anything to get slower, ever. Even the raspi didn't have memory that is that slow that this is a reasonable outcome. By default on most distros, ARC size is capped to 50% of physical system memory. Keep in mind it is a cache: if something else needs needs the RAM, it will be released.

    As a concrete example: I was recently working on a server where a maintenance task that should take like 12hrs or so at the worst somehow took 2 weeks (!) and still wasn't finished. That was ARC being disabled.

  • What size is the ARC set to? I've seen cases where it was fully disabled, which (unsurprisingly) seemed to murder performance and is probably even worse when in such a CPU limited platform. You stating that only 1.5 GB of 16 GB were in use makes this seem likely.

    In general, if you care even remotely about performance, a raspberry pi is probably the wrong choice for a NAS. Even a single disk should have no issues saturating a 1gbe link. That being said, even a pi should manage 1 GBit/s on ZFS, especially when reading.