Xubuntu did me for years but I hate the new snap thing that happened to Ubuntu so I assume that will happen to Xubuntu too.
Debian Testing seems to be the way to go now.
Xubuntu did me for years but I hate the new snap thing that happened to Ubuntu so I assume that will happen to Xubuntu too.
Debian Testing seems to be the way to go now.
I call bull, unless you’re on a beta channel.
When was the last time you had to reboot macOS for an update, and how long ago was the second-last update?
And cannot remember the last time any one of the 100+ windows 10 machines I administer had a forced reboot.
Meanwhile there are plenty of horror stories of people being unable to work, or worse, losing their work, because of Windows 10 updates.
I installed sshd using what I thought was apt. It actually happened that Xubuntu installed a snap. I also couldn't enable or start/stop `sshd` using systemctl, for some reason.
I'm quite sure there's some way I could learn to manage services in snaps... or maybe it was a bug? Either way, I don't want to waste my time. I don't see how this change makes my workflow any easier than centralised package and service management. I'm looking at MX Linux/AntiX now.
`sshd` isn't a valid package name in Ubuntu repos which Xubuntu uses directly and without modification (it's openssh-server you are looking for) so apt would throw a package not found error.
Also `sshd` doesn't exist in the snap store[1], neither does `openssh-server`[2].
Given Canonical/snapcraft.io are the only source of snaps what you have described is impossible.
While the package wasn't named "sshd", that's an abbreviated way to refer to the ssh daemon. The package name varies between distros, but the config file and executable are known as "sshd". I was installing the ssh daemon package by whatever name the Debian/Ubuntu maintainers christened it.
Something else must've broken it, then.