Tried for half the weekend to get elementary to work, it just refused to install for reasons unknown.
Gone with Mint for now.
I like the hardware (an old Intel MacBook Air) and didn’t want it to go to waste.
I’ll see how I get on with this desktop. Went feet first straight to bare metal because I couldn’t be bothered with dual boot. It was too much faff. Would value any insight from others who’ve found a lovely distro/DE combo with these tiny machines.
Making my first moves away from proprietary software. Thanks largely to being inspired by you delightful folk.
I agree with that assessment whenever it's not connected to the internet. But, if it is, I actually find it hard to justify for myself to not (at least) receive the security updates. Which, in the case of non-frozen packages, suggests applying regular updates.
But yeah, more than anything, I think this touches on threat models. Which are very subjective by themselves and thus probably not very interesting to discuss 😜.
My apologies, perhaps I should have been more elaborate. So,
paccache'smanpage mentions a systemd timer it refers to as paccache.timer. With it, package cache can be cleaned periodically. And, by default, it does so weekly.As to why this suggests weekly updates as a lower bound,
paccacheremoves old packages. Thus, from my understanding,paccachegoes hand in hand with updates; updates yield the old packages which will be deleted bypaccache. As such, for two consecutivepaccaches to do anything, an update has to have occurred in between. Thus, if paccache.timer defaults to weekly cleanups, then it has to be accompanied with at least a weekly update.Of course,
paccachewill handle higher update frequencies without any problem. Thus, updating only once a week becomes a lower bound for paccache.timer's default functionality.To be clear, I only said "suggest" :P . I can't do any stronger claims 😅.