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)
I am a Computer Information Systems Professional at a major Fortune 500 corporation. 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. We had previously been running OpenBSD on all our quad processor Xeons. Some of them had had uptimes approaching a year! My personal favourite, Gerbil, had been running without a reboot for three years.
One day one of those Microsoft shills that you often read about on the Register came by for a visit. I grew very suspicious about what was going on when my boss and the Microsoft representative walked by my desk, and entered the server room. I could hear muffled voices through the closed door. The Microsoft representative was asking what we were running on our servers! My worst fears had come true. I sat at my desk for the rest of the day, silently awaiting the bad news. The news did not come until the next day. It was worse than I had feared. We were to be a Microsoft only shop from that day on! I could not believe it. The Microsoft representative had told my boss that the operating and support costs would actually go down. And my boss had fully bought into it, hook, line, and sinker.
Tough times hit our company in the last month, and we were forced to lay off a few of the less experienced IS/IT workers. One of them took this rather hard. As a last minute attempt at corporate sabotage, 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. It is strictly because of Microsoft's poor implementation of a multi-user computing environment that our company lost three days of productivity.
Needless to say, I had our quad Xeons back running OpenBSD by the end of the week. Gerbil is back on its way to another glorious 3 years of uptime.
Where are the color-coded states of emergency? This is no respectable anti-panic plan.
Witness the rebirth of ENRON!
tcd004
they know well how to prepare for the worst in computer behavior.
may be so, but OSX/Darwin (BSD core) is on the way up. So BSD ain't quite dead, just evolving
"I think it would be a good idea" Gandhi, on Western Civilisation
Now: Postulate anger, boredom, grief, cheerfulness and serenity -
in that order. This is continued until you are sure that you
can create any emotion.
ot6
OS_X (OH S TEN) is now the single largest install base of *NIX
"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?
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"
Panic 12 as described in the article is most likely a hardware fault somewhere on the mainboard. It is by far the most common cause of a panic on FreeBSD. Exchange mainboard, CPU and memory against working components and you are back up and running without the panics.
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?
the problem is that code compiled with -O2 option behaves (in bug cases) way different from code compiled without optimization, that's it: it may never trigger bug you are looking for if it is compiled with -g.
'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.
common, give us this screen dump, we wanna see.
I know this was offtopic, but the topic sucked and I wanted to post anyway.
Aye, the topic is really, really suck so I look at his sig instead:
Michael Lucas lives in a haunted house in Detroit, Michigan with his wife Liz, assorted rodents...
I wouldn't want to read from those who married rodents!
Yes. I've yet to encounter a FreeBSD kernel panic that wasn't a hardware issue, two recent ones that I've had have been memory related. Now, my standard mode of operation is to put in a memcheck86 floppy and reboot before I do anything else.
come on, what kind of geek are you ? : ) there's always a technical solution to a social problem : ) what you need to do is go to www.smartin-designs.com/hosts_info.htm , grab a hosts file, modify it as needed, and wave bye bye to all the ads.......this works great for me, and kills a lot of spyware too.
Lawyers, MBA's, RIAA? A jedi fears not these things!
You don't need to use paint shop pro to get a screen capture. Just press Print Scrn to capture the whole screen, or ALT+Print Scrn to capture the active window.
its on my machine at work, at home tonight
can post it up to a website later, I will
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.
Yes I agree -it's getting to the stage with some sites where
the Hey I'm a flashing ad!
story Look at me!
you Hey over here!
want
to
read
Flash!Flash!Flash! is
so
squashed
by
ads Have I got your attention yet?
you
keep
having
to
Do you want to save money?
scroll
down
Personally I just turn pictures off when I get to a site like that.
Video Game cheats, hints a
If you've got FreeBSD installed, you've already got the worst.
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. ;)
Details: Since Windows always works, you will be able to use this second machine to search Deja^H^H^H^HGoogle Groups for troubleshooting information. Microsoft understands that most people use computers for the purpose of using applications, and created Windows so that we could use applications without having to worry about what the operating system is doing. You will never have to worry about mounting disks, recompiling your kernel, or downloading hacked amateur device drivers -- so when your FreeBSD or GNU/Linux machine breaks, you can rely on Microsoft Windows to provide access to online Unix-wannabe documentation. But why are you using an operating system, such as GNU/Linux or FreeBSD, which purposefully places obstacles in front of the potential user? Just listen to several testamonials from satisfied Windows users.
So there you have it! Windows is superior to both FreeBSD and GNU/Linux. But, if you really have enough time to waste configuring and using such models of antiquated technology, make sure that a properly licensed copy of Microsoft Windows is nearby. You can rely on it.--
"Negative One, Troll."
A golden badge of honor,
worn on my penis.
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
I had to fire up PSP and do a screen capture.
You don't need to fire up PSP to capture a screen.
Hold down [shift] and [alt] and hit the printscreen button.
voila. The active window is captured to the clipboard and can be pasted into most decent apps to capture the image. If you are on a bare-metal Windows machine, you can use Wordpad to contain the screen dump as a regular bitmap.
It's just another example of the 'hidden functionality' built into the Windows GUI. The kind of thing they'll have on a Linux Desktop in a few years, if it happens to scratch somebody's itch. Otherwise, oh well.
I don't know why I typed "OpenBSD", I knew it was "FreeBSD", I guess that my fingers were typing ahead of my brain. Sorry if I offended anyone.
Nothing for 6-digit uids?
nowhere does it say that this site is a linux site. If it had to be labeled anything it should be an opensource site, thats why you get new about linux, bsd, mac os x.
Apple's Aqua environment on top of BSD is like cement shoes on a ferarri.
Oh, and btw- RTFM, and get a clue, idiot.
Details: Slashdot is a very reliable source for negative Microsoft news. They believe that by posting only negative Microsoft news, and posting only positive Linux-related news, that people will believe Linux is superior. Unforunately, the intelligent computer user does not rely on Slashdot's week-old link reposts for unbiased information. Slashdot is unable to accept that Linux is not, and will never be, all things to all people. Slashdot is also unable to accept that Microsoft provides a lot of very cool technology.
The bottom line is that the Cheap Software world is behind the game on a lot of technologies that matter to business. And .NET allows developers to build very powerful solutions around web services much more quickly -- and remember, Slashdot, some of us work in the real world, where time, and not banner ads, equals money -- than with Java and Apache's XML libraries. I've worked extensively with both technologies, and anyone who has also worked with both will agree with me. That's not to say that .NET doesn't have its weaknesses, but if you're an ASP and are prepared to commit to the framework, you have no excuse for not evaluating .NET. The Apache solutions remain viable for Arab terrorists and others who are unable to access Microsoft technology, but for businesses -- real businesses, not Slashdot/VA Linux wannabe stuff -- the investment is worth it.
Microsoft's release of the framework for FreeBSD is very interesting. I imagine its purpose is to allow the parts of Hotmail that still run on FreeBSD to interact with the .NET-enabled portions of Microsoft's enterprise services divisions. But do not be fooled into thinking that .NET on FreeBSD is a viable business solution; like J#, this technology will shortly disappear. I am curious, however, how .NET on FreeBSD compares to Java on FreeBSD. In terms of performance, .NET on Windows 2000 absolutely decimates Java on any platform -- you should read about how Microsoft reimplemented Sun's "Pet Shop" J2EE demo in .NET and acheived a 7X performace increase. I also wonder if .NET on FreeBSD allows the same access to legacy code that .NET on Windows does -- because that's another benefit of .NET, the ability to leverage existing components without even recompiling them.
Anyway, Slashdot is just a bunch of losers, and they'll be out on the street giving blowjobs for quarters before the summer. And then, their ignorant viewpoints won't even be a factor.
--
"Negative One, Troll."
A golden badge of honor,
worn on my penis.
I am not on crack, damnit.
I can hardly wait to know what to do with my kernel dump
Flush it down the toilet?
Do you even lift?
These aren't the 'roids you're looking for.
sincerely,
shoeboy
Comment removed based on user account deletion
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.
Right on. I know plenty of people who've submitted stories about all aspects of Rotor. I've also seen a port commit in FreeBSD to build Rotor. What's more, the FreeBSD port maintainer already patch like 6 critical bugs in Microsoft's code.
What the hell, Slashdot? Run a damn story already. Just like to the MS page, for crying out loud.
Details: I know exactly the ads that you're talking about -- animated full screen motherfuckers that take over the browser window for ten seconds or so. Another type of annoying ad is the "cool" animated Flash object that will show up while you're reading and require you to click to close them. Actually, I hate all Flash ads, because they waste CPU and fuck up the smooth scrolling in my IE web browser.
But these are the way of the future, and when a formerly "cool" company such as Yahoo! stoops that low, you know that the end of the world is coming. Makes you appreciate Google even more, those Scientologist bastards.
In other news, I'm highly amused by Slashdot's new "below the story" block ads. Hey, losers, you'll be out on the street taking it up the ass for a dollar by June, no matter how many ads you sell. VA Linux^H^H^H^H^HSoftware is dead, so you should be spending your time trying to find a nonviolent pimp.
--
"Negative One, Troll."
A golden badge of honor,
worn on my penis.
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";
This is funny in more than 2 ways. It deserves a +5
no ads at all. although on my windows box, I got this really useful error message:
anotherboguserror.jpg
after I wrote my new host table and disabled my DNS caching and putting in a static IP. The machine only has one NIC.
take that back, preview reveals the need to ad ssads.osdn.com for some of those slashdot ads.
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.
Yet another crippling bombshell hit th beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as further exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking extremely bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 93% of its core developers.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
*BSD is dying
Would that be a kernel dump or a dump with kernels?
eh?
unless you're some limey scumbag; of course.
If you want to install *BSD on a computer, you sure are preparing for the worst.
Install base getting closer to 0% every day, support for new hardware as good as crap, forget it, I'll stay with Linux.
You gays can wank off on *BSD if you like, but do it at home.
Guess the icon of the story is wrong, it should be the "funny, laugh" one. It's indeed laughable to have the two words "secure" and "*BSD" in the same sentence. LOL!
Oh, of course - the ksymoops! Man, I loved how *nix makes their commands so obvious.
Let me take it apart: ksymoops = "kernel symbolic oops". In general, if something starts with a 'k' on Linux, it's either inside the kernel or some part of KDE.
For another thing, how is it obvious that a "chair" is something you sit on while in front of a desk, other than the fact that you've been using the word since you were two? As you learn Linux debugging, you pick up its special vocabulary.
Will I retire or break 10K?
"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."
I've never been able to get a straight answer as to why the swap rule of thumb is double the ram. I guess that explains it, although since Linux puts the backtrace to the console and syslog maybe there is another reason as well...
-----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d? s: a-- C++++ UL++++ P++ L+++ E- W++ N o-- K- w--- O- M+ V PS+ P
The article is informative and clearly written, but crashdumps are more useful for determining kernel software problems than hardware ones.
If the system is a stable release, and has been running without crashes for about a year, I'd start by running diagnonstics on the hardware - specifically, memory and disk - before trying to debug the kernel.
Ubi dubium ibi libertas: Where there is doubt, there is freedom.
Le coeur de cette région se compose de 2 municipalités bien imbriquées l'une dans l'autre: Ste-Agathe-des-Monts et Ste-Agathe-Sud. Si bien bien imbriquées ensemble qu'elles ont fusionnées. Mais pour les gens de l'extérieur, ces divisions administratives ont peu d'importance: on vient passer ses vacances à Ste-Agathe!
Cette région est bien garnie en infrastructures de tourisme et Ste-Agathe peut se vanter d'avoir accueilli des générations de villégiateurs et de touristes. Quels que soient vos besoins, Ste-Agathe peut se vanter de pouvoir les combler sur place. L'hôtellerie et la restauration y tiennent une place de choix.
Le train ne passe plus à Ste-Agathe? Qu'importe! On rénove la gare et on transforme le chemin de fer en piste cyclable, un concept unique en Amérique du Nord. Fruit d'une concertation de la région touristique des Laurentides le parc linéaire "Le p'tit Train du Nord" traverse des dizaines de villages tout au long de ses 200 kilomètres. Vous pouvez l'utiliser le plus facilement du monde à partir de Ste-Agathe, au site de l'ancienne gare, par les différents moyens adaptés aux saisons: motoneige, ski de randonnée, cyclisme et randonnée pédestre. Ce parc est probablement l'une des plus belles réalisations touristiques des Laurentides.
Dans cette grande région, les sports et les activités d'hiver n'ont rien à envier à celles de l'été. L'hiver en Nord, grande fête de l'hiver à Ste-Agathe, permet de bien apprécier les splendeurs de l'hiver. L'été apporte également son lot d'activités: plage, natation, motomarine, bateau, voile, cyclisme, randonnée pédestre, et encore plus...
Quel que soit votre séjour dans la grande région de Ste-Agathe, nous pouvons vous assurer que vous en partirez enchanté. Et que vous y reviendrez!
For example, if it's dying?
sulli
RTFJ.
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.
As usual, an ignorant post get moderated up, sigh. .NET article.
Here is your
It was correctly posted only to a section, since I don't think the average slashdotter will start compiling it, let alone show interest in it.
im not sure about you, but i just shit out bits of corn, not the whole kernel. you should see a doctor.
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.
Anyone else notice how the poster of this comment appears to have inserted _no_ irony or sarcasm whatsoever into their post? In other words, the poster was being serious? And yet the comment is modded as "Funny". I love slashdot; any community that can laugh at a windows user who takes themself seriously is a place I can feel at home ;-)
Okay, I'll bite. What "cool technologies" does MS provide?
".NET allows developers to build very powerful solutions around web services much more quickly". So what about perl and java? What are they?
7x performance? Bullshit. Yes, Java isn't fast, but the limiting factor with modern, good VMs (like IBM's) is *not* the CPU but the fact that it eats RAM like there's no tomorrow. Java generally runs more than 1/7 the speed of a compiled C program. You are not going to convince me that MS's newcomer C# compilers run 7 times faster than Java, which would be faster than C benchmarks.
May we never see th
The thing is that Linux was designed to be flexible. You want this kind of functionality?
echo "\"xwd -out screenshot\"\n shift + alt + printscreen" -e >> ~/.xbindkeys
And voila, you have the same functionality.
Of course, most Linux distros don't turn on all the bells and whistles by default...you get to find 'em.
May we never see th
When you are close to something, you sometimes overlook reality. No offense intended, but in your mind you seem to have greatly exagerated the importance of FreeBSD. Outside of the rather insular BSD community, most people, including most computer users, have no idea or even interest in FreeBSD. Most people struggle along with their Windows and Video Professor tutorials. So don't take it as a snub if the rest of the world is not interested in your hobby. It's not meant as a snub; it merely happnens to be the way that the cookie crumbles. A website that specializes in FreeBSD might be a better place to find the information you enjoy.
Details: "BSD" has existed for almost twenty years. Today's BSD software -- BSDi, FreeBSD, NetBSD, OpenBSD, and Mac OS X -- are derived from 4.4BSD-lite, the last public release from Berkeley CSRG. What is CSRG, you ask? Well, UNIX was originally developed at Bell Labs (AT&T), and AT&T released the source (sound familiar?) to academic and research institutions in the late seventies/early eighties. These groups did a lot to improve UNIX, but none did more than the Computer Systems Research Group ar Berkeley. They created the primary non-AT&T variant of UNIX, called BSD (Berkeley System Distribution). BSD played a huge part in the early years of the Web -- DARPA, the government agency whose ARPAnet was the precursor of the WWW, contracted CSRG to add TCP/IP support to BSD. BSD was the first OS to have integrated TCP/IP, actually -- it was the original Internet platform. BSD had a good number of other innovations as well, and the CSRG freaks added many loved/hated things to UNIX culture (such as Bill Joy's C shell and vi), but none is as significant IMNSHO as TCP/IP.
The CSRG was winding down in the late eighties, after DARPA funding dried up. They were going to call it quits, and decided to release the BSD source to the public. Well, there was still some AT&T code in there, so AT&T had a hissy fit and sued. Bottom line: CSRG removed the AT&T code., and "4.4BSD-lite" was released in 1994 IIRC, and it was that same year (IIRC) that Free- and NetBSD started becoming popular. This is 2002, so it is very possible that the poster has been using FreeBSD for eight years, and if he's referring to BSD as an OS family, it's quite obvious that he could have been using it for eight years.
Just because you're a clueless newbie doesn't mean that everyone else is!
Continuing my history of BSD... OpenBSD is a fork of NetBSD, created when Theo the Rat^H^H^H^H^H^H^Hde Raadt became enraged when fellow NetBSD developers would not give him the title of "Grand NetBSD Master of the World" and allow him to appear naked on the cover of NetBSD CDs. OpenBSD claims to be ultra-secure because Theo has personally read every line of code, but in truth it's really sort of amateurish and its "amazing" history of few exploits is due to the fact that its userbase is like five people, including Theo's dead mother and his dog Farmer, whom he has hot dog sex with.
BSDi, a company whose board included several original CSRG members, produced a 4.4BSD-based OS called BSD/OS (creative, eh?). This OS was used by many ISPs and webhosts, but the company is gone now. BSDi had bought Walnut Creek, FreeBSD's primary supporter and distributor, last year, but BSDi is now owned by Wind River, a small loser company that doesn't seem to know what the fuck to do with BSD/OS. (They don't even put their prices on the website. I emailed and asked. I was returned a Word document with a price list. A Word document! I mean, sure I use NT as my primary workstation platform, but they're not going to sell anything to the BSD nazis by writing a price list in MS Word!) I'm honestly not sure what the status or future of FreeBSD is at this point, but going to FreeBSDMall.com and buying some daemon crap certainly won't hurt.
SunOS, the kernel of what is today called "Solaris," was once BSD. Many choose to exclude this from their histories, but you cannot change the fact that SunOS was once the most popular BSD OS. (You do know that famed BSD hacker and possibly homosexual Bill Joy is Sun's Chief Scientist, right?) In a controversial move, Sun moved to a Sys V kernel in the late eighties, to help show solidarity with AT&T's goals of standardizing the many UNIX variants. AT&T soon stopped caring, and ownership of UNIX moved from Bell to Novell and then to SCO (just about bankrupt, eh?).
Today, UNIX branding is controlled by the Open Group, the official publisher of the UNIX specs and certifier of UNIX operating systems. It's because GNU/Linux doesn't pass the OG's tests that it cannot be called real UNIX. Real UNIX operating systems include Solaris, AIX, HP-UX, IRIX, Tru64/Digital, and UnixWare. Notice anything missing? That's right, BSD is not a real UNIX! UNIX specifies a SysV system, and since BSD-lite doesn't include any original AT&T code, no modern BSD has any ties to real UNIX. Nevertheless, this is a very hazy area from a legal standpoint, so the OG seems to have no problem in letting BSD users call their systems "UNIX." (Note the absence of any trademark/copyright marks.)
But back to BSD! The only other BSD system worth mentioning is Mac OS X. Mac OS X is really sort of a bastard, having a lot of fucked up Apple and Mach shit mixed in with its FreeBSD roots. System-level development is different than normal BSD system development. However, because it's similar from a userland perspective, you can call it Unix, I guess. If Apple is to be believed, Mac OS X has made "Unix" a major player in the desktop market. (And if you want to really think about that, and all of the Microsoft software that runs natively on OS X, it will weird you out!)
Today, *BSD truly is dying. I'm sorry, but it is. The market is fueled by business users' money, and business users often require specific applications, applications which only NT, UNIX, and GNU/Linux can provide. BSD will remain a nice platform to run Apache, but you're not going to see FreeBSD be a targey platform for many business projects. (Note: Sony Japan runs their website on FreeBSD, but that case can be safely ignored because they're crazy Japanese and can be counted on to rice-up even the best of computer systems.) FreeBSD developes have noticed this, and most have chosen to spend their time working on GNU/Linux -- which, while equally lame, at least looks better on a resume than BSD. (PHB: "FreeBSD? What's that? Oh, you've used Linux too! I read about that last year in PHB Monthly, the PHB's guide to buzzwords and trends!")
I hope that this post has been Interesting and Informative (hint, hint).
--
"Negative One, Troll."
A golden badge of honor,
worn on my penis.
And regarding your comment re: Perl and Java, it's obvious that you've never practiced what you preach. I've done web services in Perl, Java, and C++, using both Apache's and Microsoft's XML libraries and models. And .NET blows them all away. You sound like some sort of "armchair developer," like Malda.
--
"Negative One, Troll."
A golden badge of honor,
worn on my penis.
Let me follow up my victorious post by mentioning that the performance gain is due to much more than CPU utilization. You obviously have no idea about the factors involved in building a multitier web application. But, you're an amateur, so you can be forgiven. You can go on thinking that a Linux box with Perl is just as good, since you'll never have any impact on the industry. Terrorist scum.
--
"Negative One, Troll."
A golden badge of honor,
worn on my penis.
I'm going to be serious for a moment. You're exactly the kind of moron who makes me afraid to mention that yes, I have a GNU/Linux box, in public. You aren't helping anything, or anyone. You aren't cool. I know you because I used to be you. Grow up. Please. I hope that once Slashdot shuts down that people like you give up.
--
"Negative One, Troll."
A golden badge of honor,
worn on my penis.
FreeBSD-3.5 hemsut 7:07AM up 822 days, 06:32, 2 users, load averages: 1.17, 1.15, 1.10
What are you people complaining about?
and the post is intended to be funny.
The fact that the story didn't make the front page is more incriminating than not posting it at all. Of course, this is their site, they can post whatever the fuck they want to, but they shouldn't pretend to be either unbiased or journalistic in any sense. Even your average leftist US or European mainstream news site is less obviously biased than Slashdot, and both Slashdot's not-so-clever agenda and lack of intelligence show on every article that makes the front page. It isn't very hard to read between the lines on Slashdot.
-- Synopsis Troll, banned for spreading the truth and fighting the evil that is Slashdot
I put a Redhat install disk in the floppy drive, the damn freebsd thing just panic and died.
=)
Please mod the Microsoft Employee troll down a few notches.
No, you can boot fucking retard. A core dump is similar to a blue screen of death in windos. what do you do with windows? reboot. He's just explaining how you can dump your memory to disk, and send the results to the FreeBSD developers so that they can diagnose the error and fix it.
Common sense is not so common.
This got a underrated +1 rating.
Wow. Love to see the justification beyond "I'm a clueless prick"
Windows XP is even easier.
Microsoft knows usability.
Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as further exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 93% of its core developers.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dead
It is now official - *BSD is dying
A crippling bombshell shattered the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as further exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood. FreeBSD is the most endangered of them all, having lost 93% of its core developers.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS hobbyist dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
*SD is dying
You can dump a NT kernel crash, but sending it to Microsoft for analysis costs money. Lots of money.
...it doesnt panic. in camly states that there is some trouble, then it fixes it and makes your system run 10% faster to apologize.
four-oh-four
So MS releases some source (seeing their .NET in serious jeopardy), which could in theory be compiled on different platforms. If someone went through the herculean porting effort, do you think MS would actually let you *run* anything or *distribute* anything, without some serious licensing fees? Don't fool yourself.
-me
Love many, trust a few, do harm to none.
Because if it is then by all means spend time doing this. Else, just spend some money on better hardware - probably memory. The cost of that hardware is probably far less then the cost of your labor.
If you need to build an insto-recovery system for a network of identical machines, that is something different. By all means create an ability to rapid rebuild a blown system and recover the last incremental backup. But otherwise don't try to make a hardware problem into a software solution.
In case you've been living in a cave somewhere: FreeBSD is dead.
As far as I'm best able to determine, there is quite a bit of truth to the phrase FreeBSD is dying. Didn't it go out of business about a year ago? I think so.
Fact: *BSD is dead
Oh? *BSD is dead? Well, didn't you say that it was dying not dead? If you're going to be a troll, at least be a consistent one!
As of Saturday 30 March the cli is in the ports tree at lang/cli
-xenyz
http://www.apple.com/macosx/
Jake and the Fat Man.
Because it was release for FreeBSD and not Linux. Most of the Linux faithful are over in the corner sulking that it wasn't release for their beloved distro/kernel of the week/self congratulatory club. :-p