6 ms·

The forced reboots meant there was no happy path in Windows 10 for me. Xubuntu did me for years but I hate the new snap thing that happened to Ubuntu so I assu

The forced reboots meant there was no happy path in Windows 10 for me. 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.

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 ago
  Sorry 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 ago
    I 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.
vt240 6y ago
For what it's worth, Windows 10 since 1809 has supported prompt-before-download for Windows Update, and corrected many of the other annoying "do as I want, not as I say," issues from previous releases.
maccard 6y ago
I assume you mean forced reboots for updates? Linux is definitely leading here, my MacBook needs a reboot fairly frequently for updates, I'd almost guess at more often than my win10 machines. That said, one reboot a month isn't an outrageous ask I don't think.
- Razengan 6y ago
  > my MacBook needs a reboot fairly frequently for updates, I'd almost guess at more often than my win10 machines. 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?
  - jrace 6y ago
    I had to reboot to do the update from 10.15.4 to 10.15.5 And cannot remember the last time any one of the 100+ windows 10 machines I administer had a forced reboot.
    - Razengan 6y ago
      In 10 years I have never had a forced reboot on macOs, that I explicitly did not allow. Meanwhile there are plenty of horror stories of people being unable to work, or worse, losing their work, because of Windows 10 updates.
    - fortran77 6y ago
      I don't get forced reboots either. I'm running a stock Windows 10 Pro, and I haven't changed very many settings from the default. I'll get a notice that I should reboot to get an update about once a month, but not a forced one.
- Sangeppato 6y ago
  There's a difference though: on macOS the system will say "there's an update, do you want to install it now?". If you select "yes" the system will upgdate and eventually reboot, otherwise you can go on with whatever you're doing without worrying. On windows instead you get a notification that says "I just installed an update and you need to reboot, if you don't do it right now the machine will reboot outside of the active hours". I just don't understang why Microsoft doesn't put a simple toggle for automatic updates in W10. MacOS has it, all the linux distro have it, even iOS has it, why is it so difficult for them?
da_n 6y ago
Why do you hate snaps?

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 ago
Sorry 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 ago
  I 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.

vt240 6y ago

For what it's worth, Windows 10 since 1809 has supported prompt-before-download for Windows Update, and corrected many of the other annoying "do as I want, not as I say," issues from previous releases.

maccard 6y ago

I assume you mean forced reboots for updates? Linux is definitely leading here, my MacBook needs a reboot fairly frequently for updates, I'd almost guess at more often than my win10 machines. That said, one reboot a month isn't an outrageous ask I don't think.

Razengan 6y ago
> my MacBook needs a reboot fairly frequently for updates, I'd almost guess at more often than my win10 machines. 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?
- jrace 6y ago
  I had to reboot to do the update from 10.15.4 to 10.15.5 And cannot remember the last time any one of the 100+ windows 10 machines I administer had a forced reboot.
  - Razengan 6y ago
    In 10 years I have never had a forced reboot on macOs, that I explicitly did not allow. Meanwhile there are plenty of horror stories of people being unable to work, or worse, losing their work, because of Windows 10 updates.
  - fortran77 6y ago
    I don't get forced reboots either. I'm running a stock Windows 10 Pro, and I haven't changed very many settings from the default. I'll get a notice that I should reboot to get an update about once a month, but not a forced one.
Sangeppato 6y ago
There's a difference though: on macOS the system will say "there's an update, do you want to install it now?". If you select "yes" the system will upgdate and eventually reboot, otherwise you can go on with whatever you're doing without worrying. On windows instead you get a notification that says "I just installed an update and you need to reboot, if you don't do it right now the machine will reboot outside of the active hours". I just don't understang why Microsoft doesn't put a simple toggle for automatic updates in W10. MacOS has it, all the linux distro have it, even iOS has it, why is it so difficult for them?

da_n 6y ago

Why do you hate snaps?