The fat32 formated partitions are EFI System Partitions used to boot your PC. I assume that sda3 is the one Windows created, while a later Linux install created sda5 as an alternative. Yet sda5 doesn’t seem to be really used (with that cute 9MB used), so your Linux boot stuff -including a bootloader that would allow you to start Windows (or you picking directly from EFI?)- is probably all sitting alongside Windows’ EFI stuff in sda3.

In fact I wouldn’t touch anything there without some backup.

A platform platform…

Yes, the older ones of the rotating backups are still readable.

But that’s not even the actual problem nowadays: CDs and DVDs were nice when their size was still relevant in comparison to usual amounts of data. The real problem behind their decay is that we are lacking a widely available, properly scaled backup solution for more than a decade. So the mean reason people have now unreadable optical data is that they stopped thinking about it a long time ago for an utter lack of options.

in the name of nvidia of all corporations

So that’s the conversion you are hallucinating and reacting to, instead of my simple light remark that “nearly a decade after support dropped is not the usual definition of old”. Explains a lot.

I have not clue who you think or rather hallucinate to talk to… Go troll someone else.

And it’s wrong. You can downvote me every single time, yet reality will not change.

I you’ve got an old piece of hardware with nvidia hardware you know the pain. Nvidia stopped supporting 390 drivers back in 2022.

That’s literally the beginning the post setting the baseline for “old” here.

Sure it is, but I would call my hardware old already. Your “old” means reaching end of support life nearly a decade ago (390 was the last one released with support for those cards… in early 2018 - don’t know where you got 2022 from, that’s when they dropped everything pre-Maxwell).

an old piece of hardware

“old” does an incredible amount of heavy lifting here: nvidia390 is the one supporting 15 year old Fermi Cards. 😆

the agent is a tool you used

My hammer is also a tool. But if I start using (and talking about) it to wash my cloth and do my dishes I would really hope to get called out for being stupid.

• yes

• yes

• only if your hardware agrees and you can do without some features

• as just an init system: no, but you get a much more complete package

• who cares?

I’m using the default calendar app that a long time ago came with that lineageos install.

Should be this one iirc…

Don’t host the calendar, just host some WebDAV/CalDAV. That format is supported by basically all apps on every platform (usually including the default app on most phones), so everyone can pick what they want (or just stick with what they already use).

My personal pick for that purpose is Radicale.

A mandatory [AI] tag? Sure.

A [NOT AI] tag? No, that’s the default. Why normalise AI bullshit even further?

(heavy?)

And right there lies your misconception. Newer software is not heavier by definition. Quite the contrary it often gets more efficient because of constant optimisation and improvements.

The concept of newer software using up ressouces like crazy is the scam used by corporate OS’ so you buy new hardware constantly.

with Cinnamon DE: very Windows-esque UI

While I support the general advice, “very Windows-esque UI” is not a benefit for less tech-literate people. It’s the former Windows-users that conditioned themselves to expect Windows UI with all it’s shortcomings. The average elderly relative who doesn’t use anything but ~3 pre-installed programs does not care normally and can get much eaiser and more intutive UIs than those close to Windows.

Yes, the system expects regular updating. But Arch is entirely pragmatic. What has enough popularity and a mainainer to do the work will be kept in the repositories, even more if you include the AUR (also stuff moving between them when popularity and/or demand of packages changes). And because it is constantly moving on with new packages a lot is kept in parallel: There are a lot of packages in the repos in different versions, one being cutting edge, one being the lower version dependency for other packages not upgraded yet.

For reference: Yes, Arch for example expected you to update to the new open source NVIDIA drivers the day NVIDIA dropped the Volta, Pascal and Maxwell cards (GTX 1080 and below). But at the same moment the nvidia-580xx driver was introduced to the AUR, including explicitly being supported officially still. And the same happened every time a set of hardware got dropped (nvidia-470, nvidia-390, nividia-340), still kept unofficially for legacy reasons as long as it’s technically feasible. So I can in fact still run graphics cards from 2006 20 years later…

Or for another example: Yes, Arch runs kernel 7.0.12 right now and updates the kernel on a weekly basis. Yet it also has the LTS version 6.18 (guaranteed to get support until end of 2028 upstream) fully supported in the repos. And again, including the AUR I can still run the oldest still officially supported (until end of this year) long-term-support Linux kernel 5.10.

And those are basically the most extreme examples in terms of losing support, one being the constantly developed core of the whole system, the other on proprietary drivers of a private company. Otherwise the amount of 1990s tech still support by Linux is actually insane.

— Written on an ancient toaster (AMD FX series from 2011, gtx750ti from 2014, non-EFI motherboard) running Arch… which nowadays runs -given: older- games with better performance than years ago, because “the newest stuff” does introduce constant improvements and optimisation instead of new drains on your ressources like you are used to because they want you to buy new stuff.

Well… People finding and disclosing security flaws are often much closer to hackers than what happened with the AUR.

Calling people adopting outdated and orphanded packages hackers is like calling the guy that finds a banknote on the ground a bankrobber.

The term “hacked” seem to have lost all meaning…

There is the option to explicitly set DefaultTimeoutStartSec and DefaultTimeoutStopSec per systemd service.

If you don’t specify it in a service file, the default values from /etc/systemd/system.conf (both set to 90s) will be used, so you can change those values to 30s, too, to affect all services (that don’t have their limit set explicitly) globally.