Re: 10 hours lost because stupid laptop wouldn't boot! GRRR!
The problem is that you should know what to expect. Some people know what to expect and you have no right to complain about their practices. And if you don't know what to expect, you get your machine blown up, plain and simple. This is especially true if you're not watching it, whether it's on your own personal machine running a long term task or on a server that you don't have access to the console.
I run Gentoo and see these potential problems every time I do software updates on multiple machines. Logfile fillups have never been a problem for me building hundreds of packages over the years, I *know* when disk should be used and stop it before it becomes a problem, if it becomes a problem at all. Even the system logs kept for long term analysis have never an issue.
400 days uptime is a useless "brag". When there's a library update, chances are, you need to reboot, else you will not get all instances of the software replaced in memory. Windows forced reboots for a reason, Un*x users get complacent and think "OH, NO REBOOT NEEDED!" and get 0wn3d when someone exploits an old copy of a library still in memory, like /sbin/init's copy of libc and tons of other daemons that never gets restarted because, oh no, it would drop your availability because you really needed to restart almost every service because they depend on each other ... oh too bad, so sad.
Looks like you should take another look at your practices instead of bitching at someone else for differing with your own problems, and especially creating nonsense to inflate your oh so big ego.
The problem is that you should know what to expect. Some people know what to expect and you have no right to complain about their practices. And if you don't know what to expect, you get your machine blown up, plain and simple. This is especially true if you're not watching it, whether it's on your own personal machine running a long term task or on a server that you don't have access to the console.
I run Gentoo and see these potential problems every time I do software updates on multiple machines. Logfile fillups have never been a problem for me building hundreds of packages over the years, I *know* when disk should be used and stop it before it becomes a problem, if it becomes a problem at all. Even the system logs kept for long term analysis have never an issue.
400 days uptime is a useless "brag". When there's a library update, chances are, you need to reboot, else you will not get all instances of the software replaced in memory. Windows forced reboots for a reason, Un*x users get complacent and think "OH, NO REBOOT NEEDED!" and get 0wn3d when someone exploits an old copy of a library still in memory, like /sbin/init's copy of libc and tons of other daemons that never gets restarted because, oh no, it would drop your availability because you really needed to restart almost every service because they depend on each other ... oh too bad, so sad.
Looks like you should take another look at your practices instead of bitching at someone else for differing with your own problems, and especially creating nonsense to inflate your oh so big ego.
Comment