So that’s why my system was suddenly pulling a hundred something packages when I randomly check for update.

Good one.

While old packages do ruin experiences, stuff changing too rapidly can as well.

Arch as well as OpenSUSE Tumbleweed a good example at this.

Damn, I wish I have that level of dedication toward something.

They’re still going at it??

While I’m aware that it’s completely feasible and even practical to setup desktop on alpine, what drove me away was the fact we’d be ditching musl & busybox for more full-featured solutions anyway.

The systemd units are easier to create and maintain compared to the init scripts. The systemd itself can also be used as a one stop solution for cron, hostname, ntp client, dns resolver, tmpfile manager, even bootloader, and many more.

Don’t get me wrong, I’d use OpenRC where I can, but I totally see why systemd is popular.

As for the XLibre, I’ve never used it myself since I’d be upgrading to Wayland instead. My legacy systems remain on X11. I’ve read it’s quige buggy tho. At the same time, there are a lot of fanatics who are making this a big deal out of proportion.

AFAIK, they’re not switching to systemd in the first place, at least for its base system. PostmarketOS is tho, and I can see why they’d want to facilitate that.

I too would like to know more about this controversies. Some quick web search found me some articles about xlibre rejection as well as preparation for systemd compatibility, none of which should be a big deal.

As for myself, I avoid running Alpine for a full-featured desktop system simply for the fact they’re designed for embedded systems.

I have in fact tried setting it up for desktop use. What made me end up abandoning it was that I ended up having to get rid of the stuff that make the distro special (i.e. busybox and musl) since even the lightest distro requires udev and all.

Careful, that’s how you get bugs in your code.

Do correct me if I’m wrong here, but aren’t those embedded libc only excel in taking less space? I wouldn’t be so sure if they’d be less resource intensive. If any, it may be more, due to the CPU vs memory trade-off.

You can disable it thru the command akonadictl. You can’t remove it easily tho, as a lot of KDE components depend on it. One thing tho is you can make sure it pulls SQLite instead of MySQL or PostgreSQL as its dependency.

Not sure about the bang for the buck, as the 3.5 tend to be more expensive where I’m at. Worry not, tho, I won’t be a cheapskate for when it matters.

As for the size, I’m looking for exactly the 2TB one, for which there’s no issue in finding either.

As for the manufacturer, I’m leaning more toward Seagate, which have both types. I already have a few from them, one of which is a 2TB 2.5 HDD for a laptop, which I’m happy with. This one will be for my desktop.

I’ve read that larger cache size can be an indicator of SMR drives. Other than that, I don’t really care about it.

To confirm your uncertainties, I can indeed use the external caching mechanisms on btrfs.

How much would the RPM affect things? I’d think the lower RPM would be less problematic, at least where longetivity and noise is concerned.

Also, what’s your reasoning for the extent size?

I’m not gonna break my bank for nothing…

You mean like uConsole?

Still, fuck HP.

Meh, they’re shit anyways.

This simply means the person isn’t finished talking.

Really?

I thought it’s great, since those exploits didn’t just come from thin air. It would be bad if someone got their hands on a zero-day and managed to do something catastrophic, like shutting down airports, or blowing up a power plant.

Also, it’s not like they’re losing money over this.

Debian & Alma of course!