Slashdot Mirror
Preparing for the Worst in FreeBSD
LiquidPC writes "In Part I of this series,
Michael Lucas, from ONLamp.com, goes over preparing your FreeBSD computer for the worst in case of a system panic."
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
Where are the color-coded states of emergency? This is no respectable anti-panic plan.
Witness the rebirth of ENRON!
tcd004
Big_Scary_Daemons.html
Yep, that is the name of the page.
Michael Lucas lives in a haunted house in Detroit, Michigan
Maybe we could move the ghost to Seattle?
"It is a greater offense to steal men's labor, than their clothes"
I'm a Sun admin by day, and Sun has always (since at least SunOS 4.1, when I started) made provisions to do this. I'll admit that I'm rarely cutting-edge with my Linux systems, so I haven't had any panics that I wanted to track down, so I don't know if Linux does this sort of stuff for you. I'm shocked that OpenBSD doesn't.
Nothing for 6-digit uids?
And you run Windows?
--Brett GLass
Very recently the head of our IT department decided that we were going to switch every one of our networks over to Windows XP Professional.
Windows is an Operating System, not a network. Your network probably "runs" TCP/IP, Netbios, and a handful of other protocols. Windows runs on desktops, laptops, and servers.
he decided to change all of the Computer Administrator passwords on a few of the XP Professional boxes sitting around in the server room. This caused absolute havoc, as Dell had failed to send along administrator passwords for the new boxes. Our company could not make use of these computers for three days. It took Dell that long to get us the administrator passwords.
This last paragraph is a touch more concerning...first of any Windows box I've purchased from Dell, or others, have no administrator password, or are set to "admin". Why would Dell have set specific passwords for your systems? I'm just a little bit confused.
On a related point, even for those systems that come pre-installed with an OS, it's [my] standard practice to bare-iron re-install from scratch. I'm not a huge fan of MS (quite the opposite), however, in the hands of someone who has a solid understanding in operating systems, it IS possible to build a stable Windows box. I have an NT 4 server, running a database, and a mail exchange, that has an uptime of 94 days. It was rebooted for a disk addition. It was up 86 days prior to that (it's installation date.)
That said, I prefer and use Linux and Solaris much more frequently, and, unlike the windows example above, am not surprised by the continued uptime of my hosts! ;)
Now, I've gotta ask...why did you just sit at your desk waiting for the bad news?? I've (and my VP) have recieved visits from MS cronies in the past. The thing is, those people are sales/marketing weenies. Get in on the meeting, and use your own skills to ask very pointed questions. Its not very difficult to run circles around these droids. Keep it calm, polite, and just bury them in the technical truths which they simply cannot refute. If they try to call you a "Linux zealot" you know you're on the right track, and they're in the process of losing their cool. As long as you keep it together, and don't let them change the topic, I've found that its pretty easy to expose others in my company to MS's shortcomings...right in front of MS folks themselves.
If you just sit back and let non-techs make tech decisions without, at least, making them aware of the ramifications of such things, then you really can't blame them. Its kind-of what they say about voting, right? If you don't vote, you don't have the right to complain?
Now, if you work in a super huge corporation where such things are a fact of life, I'm sorry, and you probably don't have a choice. Well...other than to extract yourself from between Mr. Rock, and Mr. Hardplace.
This is most likely a hardware failure, possibly memory. Try memtest86 before you go on a kernel debugging hunt... basically, if your server has worked great for 12 months and then craps like this it probably ain't software.
I mean c'mon. We get tons of mentions of .NET around here, talk about how Microsoft is only into closed source, etc. Now Microsoft actually releases 1.9 million lines of source code spread among almost 10,000 files that people can compile to get .NET up and running on their FreeBSD boxes, and Slashdot suddenly clams up about it?
Who can honestly say that this isn't a story of interest to a large amount of people here, whether they hate .NET or not? There's a lot of discussion to be had about it. Comparisons to Mono/DotGnu? The licensing details? The performance? Comparisons to Java on FreeBSD? To pretend it doesn't exist is just silly and does seem to call Slashdot's motives into question.
Well, for FreeBSD users who might be interested, I'll go ahead and post a link to a few articles about it myself, from O'Reilly's site who's been doing a pretty decent job of breaking it down: http://www.oreillynet.com/dotnet/. Discuss amongst yourselves. ;)
For more info, check out the FreeBSD Release Engineering Page
Disclaimer:
Yes, there's a slight chance you might come across some new bug in the 4.x tree; however, it's unlikely.
SELECT * FROM USERS WHERE A_WINNER = "YUO";
I've been running two FreeBSD systems for over seven years each. I've had to do a grand total of *ONE* reboot that I can remember, aside from powering down to swap hardware, update the kernel, or to move the equipment.
It's a damn stable OS. One of these machines is a dual PII/400, serving 700-1000kbps day in day out, with hundreds of active TCP connections at any given time, starting 15-20 new processes per second. The other machine is for a single, fairly busy web site doing 700kbps traffic.
FreeBSD is rock solid. I have absolutely no need to plan for a kernel panic.