Hacker News new | past | comments | ask | show | jobs | submit login

We have these old Windows admins now learning to work with Linux. What drives me insane is their habit of randomly rebooting machines if something isn't working right. There is a problem with a Linux box, they ask you to take a look at it, you SSH in, type "uptime"... bam, it's two and a half minutes. A lot of precious diagnostic information has been lost.

This Reboot-to-Fix mindset encroaches on other domains as well. My car had a weird issue when it would't pair to the phone, auto-technician: "reboot!" Someone here say that I'm probably a *nix admin vs a Windows user, and that's true, but every time I try to do adminsy things on a Windows box, the tools are just not there, or the interface to the tool is like controls in an alien spaceship. I find myself completely and hopelessly lost. Trying to find stderr, stdout, logging, grepping, finding, the tool to work with PKI certs, all fearsome in their inscrutability. Are there Windows kernel old-timers who can help me with the learning curve? No. Most Windows admins don't have a habit of digging deep because that's not the culture, because the tools weren't/aren't there. And reboot fixes most things on Windows.

alias reboot='echo "This is not Windows!"'

Real Linux admins know how to invoke the real 'reboot' command.

Make sure to set SSH to log in directory to vim. Unlike Real Linux admins know how to quit vim so it will be no issue for them.

Wouldn't their login session end after quitting vim?

Yes, but you can get to a shell without quitting vim. <esc>:sh

Oh please, they started Gnome and used the shutdown command from the menu.

init 6

With the growing ubiquity of the linux port of svchost.exe(systemd), nested hypervisors, containerization, et al. Rebooting (where feasible) has already become a front line option.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact