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
"To prepare for a kernel panic, you need the system source code installed. You need one (or more) swap partition that is at least one MB larger than your physical memory and preferably twice as large as your RAM. If you have 512MB of RAM, for example, you need a swap partition that is 513MB or larger, with 1024MB being preferable." And people bash Windows for its lack of stability. I'm sorry, but an OS that can crash for seemingly no apparent reason, can barely be fixed, and requires a bunch of preparation just to prepare is too complicated for me. If I were a server admin with a few years experience with this OS and going the long way around to ensure a smooth ride, I might be more enthusiastic about the whole thing. At least with Windows based OSes all you need is a bit of veteran intuition and skill to find out what is wrong. Even if the problem isn't obvious, the solution usually is, or its easy to figure out.
Job? I don't have time to get a job! Who will sit around and bitch about being broke and unemployed then?
'Any' key? Where's the 'any' key? I see 'ke-tarl', 'esk', and 'pig-uh', but there doesn't seem to be any 'any' key!
Phew, all this computer hacking is making me thirsty.
Not Found The requested URL /adi/N815.slashdot/B936343;sz=336x280;P_Site=S 656;ord=101755271101755271 was not found on this server.
Apache/1.3.20 Server at localhost Port 80
Details: I just love the chicks in the blue and white dress. Especially Shannon, who works at UNATCO, and the chick who works near the entrace to the Lucky Money. "I like a man with a lot of zippers." Well unzip my pants for a big surprise, baby. Anyway, I haven't actually masturbated during the game yet, but I've thought about it.
--
"Negative One, Troll."
A golden badge of honor,
worn on my penis.
That's the downside of extreme stability...stupid people can get admin jobs, and since the OS doesn't crash, there's no chance for the admin to demonstrate their idiocy and get fired.
Seven years ago?
One of these machines is a dual PII/400
Whatever.
Was BSD Dying in 1995 as bad as it is now?
Do NOT mod up people who have been blatantly trolled. This is simple common sense. The person who was trolled is a jackass for losing, but the person[s] who modded his post up is a COMPLETE FUCKING IDIOT.
That's true. A brief, objective summary of *BSD, for those people that have never used it, like some of the Linux folks on Slashdot.
.NET support, and yet leave Linux out in the cold?
Fact: BSD has no hardware support. You may have heard people griping about this on USENET or IRC -- it's absolutely true. BSD actually has no hardware support whatsoever, and its users are forced to run the entire OS in a VM. VMs, as we have all learned from Java, are incredibly slow.
Fact: BSD programmers are Satanists. FreeBSD's *official mascot*, something that users are intended to admire, is a *demon*!
Fact: BSD is Microsoft's whore. Why else would MS favor it with official
Fact: BSD is slow and obsolete. NetBSD is slow. OpenBSD is nearly ancient.
Fact: BSD's keyboard sucks. Some of you have heard things like "Sun's keyboards suck". Well, SunOS has *nothing* on BSD. As a matter of fact, you've probably never even seen a BSD keyboard, because even BSD users can't stand them and hide them away in closets.
Fact: BSD is a rip-off of the MacOS. You may remember that Microsoft ripped the MacOS's UI. Yet even Microsoft won't descend to the depths that BSD has: not only did the BSD guys copy extensive portions of MacOS X, they *ripped code right from MacOS X!* And they're incredibly brazen about it, as well...you can hear them "boasting" that MacOS X and BSD share code all the time.
Fact: BSD is highly insecure. Perhaps everyone's heard of the Land and Bonk attacks -- the only reason that these worked was because many operating systems inexplicably used the bug-ridden BSD networking stack...and sure enough, when someone bothered to pop the top, everyone had systems all over vulnerable to all the bugs one could find. Plus, who *hasn't* heard of the OpenSSH exploits that have been trumpeted all over Slashdot? OpenSSH is from the *same people* that make OpenBSD. Why they keep trying to eliminate the mature and secure telnet is beyond me.
Fact: BSD loses your data. If you read the article, you know that BSD can randomly overwrite and break kernel core dumps, especially if you don't have a lot of swap.
Fact: BSD developers are all hippies. BSD LSD, and both came from Berkely.
Fact: BSD developers can't spell. Take a look at a bunch of utilities on a BSD system sometime...lots of them have a random lowercase "g" prefix.