10
Votes
Aug 16, 2011 5:48 AM
11 comments
Well, after all, it never asks for one.
Now you may ask, “What if I update the system? Do I need to reboot it?”
Here’s the thing – Linux is a very, very sophisticated operating system, and that means once you have run “yum” or “apt-get”, the operating system will simply take care of the rest for you.
Like leaving old binary images running in memory:
Image courtesy of Linsuxoid.
Comments
So it does need rebooting, it just doesn’t tell you when it does! That’s great!
See, that’s what happens when you stick these things in user (root) space.
Everyone knows that the best thing to do is to completely rewrite the code, recompile it against the latest minor version of the kernel, do a few modprobes, make sure that you have the latest version of grub …
I mean, why do things the Windows way?
Now that would be ebil. Ebil!
No ebilness allowed in the people’s* OS!
“Now that would be ebil. Ebil!”
Or, alternatively:
That would not be different! And innovative!
Guys! Guys! I think you’re missing the big picture here!
Linux doesn’t NEED reboots! – Unlike “that other OS” which feeds on innocent reboots, or otherwise gives you 24 BSOD’s a day.
The thing about restarting is, is it really that big of a deal?
Yes, it is a pain in the ass when you get a new computer or just install Windows and there are tons of updates which require you restart quite often… But after that, when? Every Patch Tuesday? So once a month.
My computer is almost always on, same for my netbook — though my netbook hibernates, of course. But I have no other reason to restart, except when my family does because they are just weird.
“Yes, it is a pain in the ass when you get a new computer or just install Windows and there are tons of updates which require you restart quite often… But after that, when? Every Patch Tuesday? So once a month.”
It’s actually more about that uptime thing endlessly bleated on about by supposed *nix “sys-admins”. Because, you know, redundancy and caching (see AD authentication) are such non-existent solutions that you just need to keep your server running with thousands of holes in it. But, hey, knowing the fact that you are running the backbones of an entire business operation with that one magic Durden box is all that matters, right?
“It’s actually more about that uptime thing endlessly bleated on about by supposed *nix “sys-admins”. Because, you know, redundancy and caching (see AD authentication) are such non-existent solutions that you just need to keep your server running with thousands of holes in it. But, hey, knowing the fact that you are running the backbones of an entire business operation with that one magic Durden box is all that matters, right?”
Of course they’re right! After all businesses have people working 24/7/365! So the administrator certainly couldn’t set up the server to, oh, I don’t know, restart itself after everyone leaves? Crazy! C-R-A-Z-Y!
“Of course they’re right! After all businesses have people working 24/7/365! So the administrator certainly couldn’t set up the server to, oh, I don’t know, restart itself after everyone leaves? Crazy! C-R-A-Z-Y!”
You are thinking about silly domain controllers only that other OS™ uses.
We are talking about Fortune 500™ companies using a real OS™ to conduct real business™, and I’ll be damned if they can by any chance afford some sort of fail-over here and there.
Yeah, because the companies spent too much on Winblows so they couldn’t afford any extra servers and what not.
But if they used Linux they wouldn’t need any redundancy stuff because LinuxDoesNotRequireReboots™! Who needs redundancy when you have the Linux Durden box, which is rock solid, I might add.
Exactly how does that screenshot prove Linux needs reboots?
You must be signed in to leave comments.