Whatever you get for your NAS, make sure it’s CMR and not SMR. SMR drives do not perform well in NAS arrays.

I just want to follow this up and stress how important it is. This isn’t “oh, it kinda sucks but you can tolerate it” territory. It’s actually unusable after a certain point. I inherited a Synology NAS at my current job which is used for backup storage, and my job was to figure out why it wasn’t working anymore. After investigation, I found out the guy before me populated it with cheapo SMR drives, and after a certain point they just become literally unusable due to the ripple effect of rewrites inherent to shingled drives. I tried to format the array of five 6TB drives and start fresh, and it told me it would take 30 days to run whatever “optimization” process it performs after a format. After leaving it running for several days, I realized it wasn’t joking. During this period, I was getting around 1MB/s throughput to the system.

Do not buy SMR drives for any parity RAID usage, ever. It is fundamentally incompatible with how parity RAID (RAID5/6, ZFS RAID-Z, etc) writes across multiple disks. SMR should only be used for write-once situations, and ideally only for cold storage.

I explained my reasoning and you made no attempt to engage with it and just asked a question I already answered in depth. I’m not sure what you want, but it’s clearly not an answer.

Hard disagree. Everything you learn on Arch is transferable because Arch is vanilla almost to a fault. The deep understandings of components I learned from Arch have helped me more times than I can count. It’s only non-transferable if you view each command as an arcane spell to be cast in that specific situation. I’ve fixed so many issues over the years using this knowledge, and it’s literally what landed me my current job and promotions.

Arch is why I know how encryption and TPM works at a deeper level, which helped me find and fix the issue a Windows Dell PC was having that kept tripping into Bitlocker recovery. Knowledge of Grub and kernel parameters that I learned from Arch’s install process is why I was able to effortlessly break into a vendor’s DNS server whose root password was lost by the previous sysadmin before me when everybody else was panicking. Hell, it even helps in installing other distros, because advanced disk partitioning is a hot mess on a lot of distro GUI installers, so intimate knowledge of what I actually need helps me work around their failings. Plus all the countless other times that knowledge has helped me solve little problems instantly, because I knew how it worked from implementing it manually. When my coworkers falter because the GUI fails them and they know nothing else, I simply fix it with a command.

If you use Arch and actually make the effort to learn, not just copy and paste commands from the wiki, you will objectively learn a lot about how Linux works. If you seek a career in Linux, there’s nothing I can recommend more than transitioning to using Arch (not Garuda, not Manjaro, Arch) full-time on your daily driver computer.

Anyways, after about a decade I’ve recently switched to NixOS. Now there’s a distro where the skills you learn can’t be transferred out, but the knowledge I gained from Arch absolutely transferred in and gave me a head start.

I think they’re just making fun of the bad font kerning in the app which causes a gap in the word Unmanaged

RETURN OF THE KING

Your response is “why are you doing X, you should do Y”

Because they’re right, you shouldn’t do X. I know that’s not a satisfying answer for most people to hear, but it’s often one people need to hear.

If the process must run as root, then giving a user direct and unauthenticated control over it is a security vulnerability. You’ve created a quick workaround for your issue, and to be clear it is unlikely to realistically cause you problems individually, but on a larger scale that becomes a massive issue. A better solution is required rather than recommend everybody create a hole in their security like yours in order to do this thing.

If this is something that unprivileged users reasonably want to control, then this control should be possible unprivileged, or at least with limited privilege, not by simply granting permanent total control of a root service.

This is ultimately an upstream issue more than anything else.

Refurbished drives get their SMART data reset during the process, they absolutely had more than that originally.

Recent NixOS convert, where has this work of art been all my life

There’s 102 people mentioned in that commit and two of them happen to meet in the comments of a meme thread on Lemmy of all places. I love the Internet.

Docker is open source, licensed under Apache-2.0. Not really sure what you’re talking about.

This is so cozy and giving me some inspiration for my own environment!

“Because I feel like it.”

So in other words, because she wants to? As in, “because it’s her body and she can do whatever she wants with it”?

It really seems like you didn’t have an actual argument, you just wanted to whine and duck away from any pushback.

it’s probably time to come to terms with the fact that better alternatives would have arisen had anyone thought they could truly manage it.

This is the most important takeaway. There’s a lot of people whining about Wayland, but Wayland devs are currently the only people actually willing to put in the work. Nobody wants to work on X and nobody wants to make an alternative to Wayland, so why do we keep wasting time on this topic?

The full details are complex but I’ll give you the basic gist. The original GPL licenses essentially say that if you give somebody the compiled binary, they are legally entitled to have the source code as well, along with the rights to modify and redistribute it so long as they too follow the same rules. It creates a system where code flows down freely like water.

However, this doesn’t apply if you don’t give them the binary. For example, taking an open source GPL-licensed project and running it on a server instead. The GPL doesn’t apply, so you can modify it and do whatever, and you aren’t required to share the source code if other people access it because that’s not specified in the GPL.

The AGPL was created to address this. It adds a stipulation that if you give people access to the software on a remote system, they are still entitled to the source code and all the same rights to modify and redistribute it. Code now flows freely again, and all is well.

The only “issue” is that the GPL/AGPL are only one-way compatible with the Apache/MIT/BSD/etc licenses. These licenses put minimal requirements on code sharing, so it’s completely fine to add their code to GPL projects. But themselves, they aren’t up to GPL requirements, so GPL code can’t be added to Apache projects.

Most Snaps have apt or Flatpak alternatives.

I’m simply not going to support a distro that creates a proprietary service and ships it as the default source of software. I will support and use distros that open source their code so that everyone can benefit from it. Whether workarounds or alternatives exist is unimportant, my prime issue with Ubuntu and Canonical is with their principles, not Ubuntu’s quality as a product to be consumed by me.

Look, I’m usually first in line to shit on Canonical, but I can’t get mad at them adopting AGPL. This is objectively the best license for server software. Incus should also switch to AGPL for all Canonical code, and seek to have contributors license their code as AGPL as well.

I will however point out the hypocrisy and inconsistency of it, because the Snap server is still proprietary after all of this time. If this is their “standard for server-side code” then apply it to Snaps or quit lying to us.

The only difference between Tumblr and Facebook is size. Facebook isn’t uniquely evil; it does exactly what any corporation would do at that scale. The systems that molded Facebook into what it is would also mold Tumblr or anything else into the same abomination.

I would respect principled opposition to megacorps even if I think it’s still misguided in this instance, because at least that’s overall based. But all of the discourse focuses on the specific wrongdoings of Facebook as if any other corporation wouldn’t have done exactly the same thing in their position. It feels very kneejerk.

I want to federate and use it to destroy their platform. The biggest problem with the periodic social media “migrations” that always fail is that it creates a fragmented diaspora. Take Twitter as an example. When the big migration off Twitter was supposed to happen, some went to the Fediverse, some went to Threads, some went to BlueSky.

You know what happened? After a few weeks, most of them went back to Twitter, because that was the only common place between them, where they knew they could all meet and communicate. If Twitter was forced to federate with all other platforms, it would have been snuffed out by now. But if that was even proposed, everybody would have a kneejerk reaction, because Twitter bad. Nobody is thinking of the big picture.

I find it kind of strange that people seem so hesitant about it

I simply want the Fediverse to be a proper alternative option for social media access, not just another secret nerd club. We have enough of those already. That requires not completely closing off access to the things the typical person will want to access. I want all social media to eventually be interoperable like email is, preferably on the ActivityPub standard and not whatever centralized bullshit BlueSky is trying to cook up. That is the only way we’re going to break the corporate stranglehold on social media.

Put simply, if you make people choose between our platform and the large corporate-backed platform with orders of magnitude more users, they will choose the corporate platform almost every time. And I think that’s a bad outcome for all involved.

If you’re waiting for Jellyfin to run some kind of relay like Plex, you’ll be waiting a long time. That takes a lot of money to upkeep, and the demand for people who self-host FOSS and then want to depend on an external service is very minimal, certainly not enough to sustain such a service. I’d recommend just spending a weekend afternoon learning how to set up Nginx Proxy Manager and being done with it, the GUI makes it very easy.