News for hackers. Stuff that matters.
Re:Log4Shell update: second Log4j vulnerability published by staticassertion on Wednesday December 15, 2021 @03:40AM (#29563423)
Server uptime used to be a point of pride. Now people try to shut them down as often as they can. Funny how things change.
Re:Log4Shell update: second Log4j vulnerability published by Bluecobra on Wednesday December 15, 2021 @08:19AM (#29565505)
Indeed, I remember going though great lengths to keep the Solaris hosts up that I used to administer. The graybeards I worked with treated rebooting as last resort, like admitting defeat. It was a dirty word, only reserved for lesser operating systems like Windows 95, that needed rebooting often. There was an art to systems administration that seems to be lost now. Or maybe I am just looking back though rose colored glasses. :)
Re:Log4Shell update: second Log4j vulnerability published by count on Wednesday December 15, 2021 @12:43PM (#29569156)
To be fair, it also used to take sometimes an hour+ to reinit a system. All those SCSI busses had to be enumerated, all the RAM checked for error, ah, the old days...
Re:Log4Shell update: second Log4j vulnerability published by viraptor on Wednesday December 15, 2021 @05:38AM (#29564135)
We moved a lot of things from "that one server that's setup just-so by hand" to automated and repeatable setups. If we had more/ cheaper servers before, we'd likely get there earlier.
Re:Log4Shell update: second Log4j vulnerability published by Sitio on Wednesday December 15, 2021 @04:50AM (#29563842)
My server had 80kbyte bandwidth and doing very little in a much slower time.

Kernel patches were not on top of my head 15 years ago.

Re:Log4Shell update: second Log4j vulnerability published by joshstrange on Wednesday December 15, 2021 @12:00PM (#29568589)
That seems to go hand-in-hand with the "Cattle not pets" concept, which I'm a huge fan of.