4 ms·
> I hate the new snap thing that happened to Ubuntu I installed sshd using what I thought was apt. It actually happened that Xubuntu installed a snap. I also
by HeckFeck 6y ago
> I hate the new snap thing that happened to Ubuntu
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.
- deadbunny 6y agoSorry but I'm calling bs. `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. 1. https://snapcraft.io/search?q=Sshd https://snapcraft.io/search?q=Sshd 2. https://snapcraft.io/search?q=Openssh https://snapcraft.io/search?q=Openssh
- HeckFeck 6y agoI wasn't fibbing; it is disingenuous to lie in support of a cause. I did genuinely encounter this issue. But with what you've said, I'll accept that it wasn't to blame upon snap. 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.