Slashdot Mirror

← Back to Stories (view on slashdot.org)

System Panics, Part 2: Recovering and Debugging

Posted by timothy on from the lifejackets-and-axes dept.

LiquidPC writes: "This is Part 2 in a two-part series on system panics. In his first column, Michael Lucas talked about how to prepare a FreeBSD system in case of a panic. In this column, he talks about what to do when the worst happens."

3 of 26 comments (clear)

  1. Solution! by Icephreak1 · · Score: 1

    "In this column, he talks about what to do when the worst happens."

    This one's too easy: switch to Linux

    1. Re:Solution! by ASyndicate · · Score: 2

      I tried Gentoo, hated it. :(
      I am no newbie either. Its just, They patch anything and everything without any regard for side effects, I have had 4 different boxes corrupt a filesystem with gentoo. Then I said, thats it. I have had enough. Bye.

      If you tell me that there isnt a system that the worst can happen, I had a deal that you could make 10,000 at home.

      --
      This page left intentionally blank.
  2. Re:*BSD is dying by boltar · · Score: 1

    Any box thats been running for 1200 days (ie over 3 years!!) deserves to be hacked since the admin
    is obviously too lazy or just too irresponsible to have done any security patches to the machine
    (which would require a reboot). There is NO operating system unix or otherwise which has not
    found some sort of security flaw either in the kernel or in a server app in that length of time.