mDNS solves this. It may actually work out of the box. Try ssh’ing into your-device-name.local. If that fails, check your devices’ names and if they have Avahi/Bonjour/mDNS enabled.
Something like Tailscale will set up a VPN with hostnames and IP addresses for you (and you can host your own entry server if you don’t want to use the cloud stuff). That’ll work across networks. It’ll also add overhead and it’s probably overkill for your use case, though.
Thanks, it does indeed work. I guess I’ll add a wireguard tunnel so that I won’t have to bother with the “do you trust the fingerprint?” every time I’m on a different network or when the IP changes.
If you use the .local syntax, and the device name stays the same, I think the domain name based fingerprint should prevent the “do you trust this fingerprint” problem.
If you want to avoid the question all together, you could set up an SSH certificate authority (quick guide here, less dense guides are available on the internet). By signing the servers’ host keys, you can prevent the trust on first use prompt entirely, even for servers you may not have logged into before.
Actually I want to use the wireguard tunnel regardless because right now I am tunneling VNC through SSH, which is laggy because it’s TCP. But thanks either way.
I don’t see atomic systems on desktop computers. They make sense on more embedded and stable systems that still need eventual updates like ATMs and industrial machinery control panels but not desktops. Atomic systems kill customization that is one of the core advantages of Linux. Probably it also has something to do with my not-so-enthusiastic opinion on Flatpak idk.
I’m always surprised by the toxicity of Lemmy. Anyways I think it was relevant to the topic because the OP asked for opinions on atomic systems. Are you arguing because you have a drastically different one?
No, I understand your points. I may think you need to specify what you mean by “customizable”. A lot of stuff users normally do, like theming, installing random stuff etc, works. You can layer, build your own image etc.
But this is not the point as OP was frustrated about having an OS that even though promising to be reliable still breaks.
And whining about “oh I cant tweak it” is just not at the correct place there.
But of course my answers were kinda harsh, sorry for that. But these issues are really nonissues if your priority is having a working system.
Yeah. I use Aurora on my laptop, but, to be fair, I don’t reboot it as often. Maybe every 2-4 weeks I guess.
I saw the announcement about the failing updates, tried to update my system, and that went as announced, failing to verify.
I then executed the script, updated my OS successfully and rebooted.
The system worked fine now for a few days. Yesterday I shut off the device, and today I got greeted by the failed secure boot, having to resort to the image before and fix it.
On my gaming PC I use Bazzite, but I didn’t turn the PC on the last days. I only executed the update-fix-script, installed the pending updates, played for half an hour and then shut it off again.
I will keep you up to date with the results once I come home.
Btw, I asked my partner about her opinion on this. She said that problems like this may happen anywhere, no matter which software, and as long as the devs announce that and offer a simple fix, there’s nothing one can do about it.
She only suggested a small “news channel” built into the OS.
Do you think that might be possible to integrate, for example into the MOTD in the terminal? I don’t know if there are possible solutions out there.
Are accounting firms subject to the same requirement as businesses that file themselves? It almost sounds like it’d be a good idea to have someone do all the filing for you so that when there’s a leak and you’re damaged by it you have legal recourse…
Sorry, linux is boring now now I found that on OpenSUSE. Once getting past the learning curve of linux and OpenSUSE’s general use, It has updated flawlessly for years and there is never anything to tinker with.
Not tumbleweed, right? I recall generally recall liking it until the kde 6 update broke everything if you tried to update from konsole in kde, and I remember others having the same issue. Not sure how they didn’t catch that.
It’s fixed. In general no distro is fail safe, recently even an immutable distro (our current hopeful advance in update reliability) had a hickup on an update that required manual intervention. It basically boils down to that it’s not possible to test for everything, we can only hope to continually add more test cases and improve human procedures based on post mortems.
I think they use the Fedora Kernel which would still be problematic, as the current 6.6 LTS kernel is still way newer than the 5.14 CentOS kernel (with tons of backports).
The beauty of Fedora Atomic is that anyone effected by the recent update (including me) could simply rollback to the previous image and boot as normal in order to troubleshoot. This is exactly why nearly all of my devices are running Silverblue or Kinoite now.
I think it’s worth mentioning that significant bugs happen across all major OS platforms.
Recently, Microsoft pushed a patch requiring effected users to manually resize their EFI recovery partition. Shortly after that, it was announced that all Apple Silicon Macs suffered from an unpatchable vulnerability which can defeat encryption. These are just a couple of examples from recent memory…there are many others.
To truly avoid serious software vulnerabilities or bugs is to avoid software entirely. Operating systems are highly complex, multilayered software, and shit happens.
As someone who works in an environment with many Windows and Linux VMs, I can pretty accurately state that Windows updates have caused far more critical problems than Linux ones over the past 2 or 3 years. Microsoft’s Patch QC has been AWFUL. (Print Nightmare fixes caused ongoing problems that are still breaking printing. You mentioned the EFI change, there’s also patching completely failing for machines that had too small a recovery partition. Fine if there was none, or it was large, but all updates fail after that if your machine has a partition that Windows itself silently created.) There’s literally dozens of major Windows update failures recently.
As you say, shit happens. Paying for something doesn’t make that any less.
Fedora is Fedora and uBlue is uBlue, a separate project. Blaming Fedora for uBlue issues is like blaming Ubuntu for Mint issues.
And on Silverblue issues on updated happen from time to time. On immutable distros such issues won’t break the system unrecoverable, this is the whole reason for immutables, but there are no promises for lacking of issues.
And you are disappointed because you have encountered two different issues at once. But it is a purely random event, and I have not noticed any changes in frequency.
But saying about Silverblue, I think probably it doesn’t get much attention from the Fedora project lately, because few recent releases didn’t have any improvements either.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.