Slashdot Mirror
OpenBSD Books On The Way
*no comment* writes "Well with all the advancements in PF and secure code wouldn't it be nice if someone would write a book on OpenBSD??? Oh wait, someone is. A guy named Jacek Artymiak is doing just that. The OpenBSD Gazetteer is scheduled for release shortly after the release of what may be the best release ever of OpenBSD (IMHO). Vastly improved PF, ALTQ, and BIND 9 is now default, not to mention procop stack protection. Out of the box it's ready to go as a firewalling packet-filtering bandwidth-throttling machine. A thread had started to pick up over at deadly.org."
The mirror is here.
This is fantastic news! I've been an avid fan of OpenBSD for quite sometime now and this type of concise reference guide has been needed for sometime now. Granted the OpenBSD documentation available on the Internet is extremely well done, but I think it'll be great to have it consolidated in book form especially when Jacek will update the book with each full version upgrade of OpenBSD.
Co-founder and designer at Music Nearby: http://musicnearby.com
to that, add kick ass vpn. obsd's ipsec implementation is very clean.
i'm hoping to send in some diff's in a few days that adds bsdauth support to isakmpd. that way, we won't have any need for the $2k/year fw-1 license.
It's easy. Just take a book about FreeBSD and use a thick, black permanent marker to cross out all the features that Theo couldn't figure out to steal from FreeBSD or NetBSD. Things like SMP. Oh, that's just silly, SMP, who needs that? And a whole host of other things.
I got an idea, cross out features that aren't in OpenBSD, so the FreeBSD book is now half as thick. Then, use a highlighter and an highlight all features ripped off verbatim from FreeBSD. That leaves a few pages explaining OpenSSH (which is in the base install of FreeBSD) and some crap about PF.
Oh, and few paragraphs on how the leader of OpenBSD is an arrogant asshole who cant even get SMP working because he is too stupid to read the projects he habitually takes "ideas" from.
You are a fucking avid idiot. You fucking know shit about shinola, asswipe. OBSD is all fuckig hype for losers with low end hardware. What OS is made into the glorius JUNOS for the glorious Juniper M routers? FreeBSD. Thats right! You know nothing puke. No one cares about OBSD because its not a serious projects. Its a kiddie asswipe project for losers with low end PUKE fucking hardware.
Posted so long ago, yet so few comments, oh wait BSD.. Nvrmind
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent 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 fittingly 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. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
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 dilettante 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 dying
I got an idea, cross out features that aren't in OpenBSD, so the FreeBSD book is now half as thick. Then, use a highlighter and an highlight all features ripped off verbatim from FreeBSD. That leaves a few pages explaining OpenSSH (which is in the base install of FreeBSD) and some crap about PF.
Oh, and few paragraphs on how the leader of OpenBSD is an arrogant asshole who cant even get SMP working because he is too stupid to read the projects he habitually takes "ideas" from.
A: We don't know, it's never been done before.
Q: France has a long storied history. It's had many other names in the past. What are some of these?
A: England, Germany, etc..
Q: How did the Germans invade France so easily?
A: They walked in backwards and said they were leaving.
Q: What does the French flag look like?
A: It's a white flag.
Q: What's the fastest way to make a French city surrender?
A: Fly over the city and drop in deodorant.
I think this is great. Just like in software, the proof will be in the book and how well it is written. You can search man pages but sometimes finding a good explanation makes the man pages clear. Survival of the fittest is what makes for advances in the industry, if you can call it industry.
I'm going to get one of both books when they come out. Lucas and this one.
[as an aside, if you think slashdot is dying, because every informative article that gets posted will then get flooded with comments about spelling, jokes, "in russia", counter attacks, etc, take a look at some of the apple articles. there the posts are relevant, the idiot index is way low. wow, maybe there is something about using a Mac that puts you in harmony with the universe...]
And this book will be out Summer 2003.
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.
I would hope that there is better artwork for the cover, in the spirit of the interesting artwork that comes out with each release of OpenBSD. Looks low budget now. Theo, on the other hand, is not dying, but keeps coming up with a different look for each release. He hates having to spend time and $ on artwork, but it sets OpenBSD apart fromn the other *BSDs. I know because I have all the CDs, and they are just fun to look at.
Well, I trust.
The testicles are physically removed via an incision in the scrotum. To simpify, an incision is made, the testicle is pulled out, the cord is tied off, and the testicle is removed.
The testicles are tightly tied-off at the base of the scrotum and allowed to die from lack of blood (this can take up to six or more hours, but irreversible damage may occur within the hour in some people). For the first twelve hours the pain is agonizing, but after that feeling dulls until the testicles are entirely dead. At this point they can be cut off without any pain or bleeding. The band is left on until the area is healed enough to hold together. This method of castration is commonly done on farms and is also the method favored by home and SM practitioners due to its relative simplicity and safety. An added benefit is that it also removes the scrotum.
Because of the intense degree of pain, few people successfully use a Burdizzo on themselves. The Burdizzo is a farm tool that quickly crushes and destroys the vessels supplying the testicles. After it is used the testicles shrink in size and are eventually absorbed by the body. If the Burdizzo is not closed quickly enough, the vessels will swell and problems will arise. Those that have successfully used the Burdizzo have generally had a friend close it for them.
Long term electrical testicular abuse can in some cases lead to castration. Other eunuchs have taped up and shot off their testicles with guns. Others have crushed their testicles. Anything that kills the testicles or their blood supply will work. Other people have had complications from CBT play lead to medical castration.
I'm not in the book business or anything, but just curious about folks who have enough good sense to publish an OpenBSD text.
Back in the 2.5ish days, I submitted a detailed proposal to O'Reilly to write an OpenBSD book. Their answer was "not interested, no market". I knew they were wrong...
Advice: on VPS providers
I'm guessing "PF" is "Post, First" but what do the others mean?
I feel fantastic, and I'm still alive.
It smells like something's dead.
and that is saying something.
Stop fucking the dead, people.
[note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It's wh
*BSD solutions only please. I do NOT want a Linux solution thank you very much.
and you're using OpenSSH? i didn't think so, huh?
I can't wait! I've been following a series of articles that he wrote for O'Reilly OnLamp.com. (Like this one) Very well written, and they address practical stuff.
no/yes (in base), yes (in ports)
... you could try MLPPP. however, the 'no' part is that you'll need your upstream to support MLPPP
... check out ospf, ala zebra and gated
... if they're split, it's almost guaranteed to not be feasible as there will be a mess with bgp filtering by your uplinks
no/yes in base
yes in ports
what you're looking for is called equal cost routing. it's not in the kernel though. you could find a router that supports it though
that's all assuming both lines are going to the same provider
Yes I do. Only thing the OpenBSD project is worthwhile for is SSH. And I really know how to use, unlike a pussy bitch fag such as you.
Another Theo trick, though. He stole the idea from SSH.COM Tatu, after Tatu acted like a cunt and fucked with his license.
As usual, Fuckface cunt Theo DOES NOTHING fucking original.
You are like Theo, but gayer. You are a fucking loser unimaginative assfuck, in addition to being a copycat fuck.
I love prick fucks like you. Know nothing cunt losers who come out of left field with a sexless small dick talking fucking trash while foaming at the mouth with dog cum.
But it still can't do policy routing.
Michael Lucas is a fantastic author, and we hope to have published this book by at least June, 2003.
We hope you like it.
-John Mark
Marketing Manager
No Starch Press
Hyperic Community Manager