Supposed to be a joke, for you see whenever there is a post about any BSD there are dozens of "BSD is dying" posts.
I thought I would mock the people that post them by making one of my own.
The part that should have made it relatively obviously a joke was my David Hasselhoff and piss in the snow parts, not to mention there being a couple of the BSD trolls already made.
You know it's a shame they used a Motorcycle. You see, it's official now; Motortrend confirms it, Motorcycles are dying.
One more crippling bombshell hit the already beleaguered cyclist community when Kawasaki Motors Corp confirmed the motorcycle marketshare has dropped yet again, now down to less than 18 percent of Americans owning a motorcycle. Coming on the heels of a recent Motortrend survey which plainly states that motorcycles have lost marketshare, this news serves to confirm what we've known all along. Cycling is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent frontal impact test.
You don't need to be David Hasselhoff to talk about motocycling's future. The piss is on the snow: cycling faces a dark future. There won't infact be any future at all for cyclists because the industry is dying. Things are looking very bad for cycling. As many of us are already aware, motorcycles continue to lose market share. Red ink flows like a moon cycle.
Harley-Davidson is the most endangered of them all, having lost 93% of the Easy Rider generation. The sudden and unpleasent departures of long time
Harley users Ricky L. Phillips and Gerald Smith only serve to underscore the point more clearly. There can no longer be any doubt: Motorcycling is dying.
That was what Microsoft's letters suggested to MCSEs, just go by MCSE and not refer to the Engineer part until it was sorted out. However I do not recall it being 'sorted out' at all.
The title Engineer is something that Microsoft got in trouble over in Canada.
You see, in Canada the term Engineer means something. I don't recall hearing of any resolution to the situation, but some time back Microsoft was officially made to stop using the term Engineer in regards to their Mouseclickeers.
So, is there some mitigating factor here that would convince anyone who was paying attention to deploy a mission-critical system on SMP OpenBSD in 2004?
If you see it in the 3.6 release, consider it ready. If you don't then it wasn't ready yet.
Four other points, what are you referring to? I simply replied to you telling you that your comment about GPL people being hypocritical was stupid and had no relation to the OpenBSD people not liking the newest Apache license.
And what was being discussed? You were a reply to the story, therefore nothing was being discussed, you started a discussion by making a post that had no relevence to the article.
What does the Free Software Foundation have to do with OpenBSD not liking stupid licenses?
OpenBSD doesn't like the GPL, it is infact replacing all the GPL code in the base system with BSD varients (diff, gzip, awk and others).
Your comment is out of place here, Apache being GPL incompatible had nothing to do with OpenBSD rejecting it, it was that the license is OpenBSD incompatible. Free as in free.
One thing; the BSDs have already gone through it all. They can be pushed for those accusations of code theft any more.
Though I will agree that Sun does make an interesting bidder, one that claims to be good and "open" yet it goes against that by requiring an NDA to get documentation of it's hardware and seems spend half of it's time saying making anything open would be a poor choice for the company.
True enough, but it would be nice for there to be a good guide of X tips and tricks.
Like making sure your qt is setup with all the plugins for kde, that you have switch and switch2 for changing gtk/gtk2 themes, that you use xset -b to turn off beeps in your terminals.
Stuff like that is nice, though it is not an OpenBSD thing, I would like it more to read one OpenBSD centric document over a bunch of random guides to X that make Linux-centred assumptions.
I find it unfortunate that the BBC did not recognise as the Xiph.org team did that Open Source and the Free Software Foundation's GPL are not the same thing and that to truly be open to everyone it needs to be outside of the GPL. As it stands, they gave little to the Open Source community and more to the Free Software community.
If they had given this an MIT-like license, then I would be glad. As it stands, I am more indifferent then pleased with this particular event.
I also find it odd that people are comparing this to the Ogg work by Xiph, because it is not the same at all. This means that one can use this code as a guide to creating something more broadly open using this new codec.
They're clearly doing something right (any and all arguments about abusing their monopoly must realize they had to earn their monopoly before they could abuse it).
Forgive me if incorrect, but I thought they were handed the monopoly by IBM, were they not?
If you don't need to tell the system a lie, do you?
I don't emulate Linux when I can run something from OpenBSD, sure I could tell the programme that it's running on Linux but it is not needed and would be of no benefit.
Re:Lindows? I thought it was not Linspire
on
OpenIPO and Lindows
·
· Score: 2, Funny
Tonkat (The OS Now Known As Tonkat) actually sounds much better than Linspire. Though the Tomcat people may disagree.
Exactly. How's the gas supposed to wind the mechanism? I suppose if it's a watermill design it may get some crummy milage out of it, but that's the only benefit I can see out of gassing it.
I understand you are trolling, but incase someone takes an anonymous coward's words seriously I'll bite.
Because of the way ports and packages are designed this complation issue of yours does not happen.
You do not need to configure anything to compile a port, you need to run "make install" after enabling root permissions or getting sudo setup.
Packages are not the norm by any stretch of the imagination for anyone I know that uses a BSD. Installing a pkg works fine as long as you also have the dependancies it will just install the same as if you made from a port and I have never found a port in the 3.3 release that installs broken not bad for the 193 I use for my desktop.
The only messed up compile I've ever seen is xmame+xmess, which my machine could not handle cause it doesn't have enough resources to compile it.
OpenBSD is equally able to use the ports and pkgs in it's system because the system was designed for Open.
Slashdot Mirror
I thought I would mock the people that post them by making one of my own.
The part that should have made it relatively obviously a joke was my David Hasselhoff and piss in the snow parts, not to mention there being a couple of the BSD trolls already made.
One more crippling bombshell hit the already beleaguered cyclist community when Kawasaki Motors Corp confirmed the motorcycle marketshare has dropped yet again, now down to less than 18 percent of Americans owning a motorcycle. Coming on the heels of a recent Motortrend survey which plainly states that motorcycles have lost marketshare, this news serves to confirm what we've known all along. Cycling is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent frontal impact test.
You don't need to be David Hasselhoff to talk about motocycling's future. The piss is on the snow: cycling faces a dark future. There won't infact be any future at all for cyclists because the industry is dying. Things are looking very bad for cycling. As many of us are already aware, motorcycles continue to lose market share. Red ink flows like a moon cycle.
Harley-Davidson is the most endangered of them all, having lost 93% of the Easy Rider generation. The sudden and unpleasent departures of long time Harley users Ricky L. Phillips and Gerald Smith only serve to underscore the point more clearly. There can no longer be any doubt: Motorcycling is dying.
That was what Microsoft's letters suggested to MCSEs, just go by MCSE and not refer to the Engineer part until it was sorted out. However I do not recall it being 'sorted out' at all.
You see, in Canada the term Engineer means something. I don't recall hearing of any resolution to the situation, but some time back Microsoft was officially made to stop using the term Engineer in regards to their Mouseclickeers.
Indeed, I thought you may mean that in a later moment of clarity, however, one cannot moderate and post on the same article.
So, is there some mitigating factor here that would convince anyone who was paying attention to deploy a mission-critical system on SMP OpenBSD in 2004? If you see it in the 3.6 release, consider it ready. If you don't then it wasn't ready yet.
And what was being discussed? You were a reply to the story, therefore nothing was being discussed, you started a discussion by making a post that had no relevence to the article.
OpenBSD is definately more hardcore for keeping code free, that's why they don't accept the GPL, it's not free enough for them.
OpenBSD doesn't like the GPL, it is infact replacing all the GPL code in the base system with BSD varients (diff, gzip, awk and others).
Your comment is out of place here, Apache being GPL incompatible had nothing to do with OpenBSD rejecting it, it was that the license is OpenBSD incompatible. Free as in free.
I'd say being called, "the good Professor," would be preferrable to others, say for example, "the Nutty Professor."
Though I will agree that Sun does make an interesting bidder, one that claims to be good and "open" yet it goes against that by requiring an NDA to get documentation of it's hardware and seems spend half of it's time saying making anything open would be a poor choice for the company.
You say SCO as an option as if it were not under the control of Microsoft and was infact a seperate entity.
Like with the Authour Mode/User Mode, just adding in Bork Mode would be nice and probably not so hard that it would be any trouble.
True enough, but it would be nice for there to be a good guide of X tips and tricks. Like making sure your qt is setup with all the plugins for kde, that you have switch and switch2 for changing gtk/gtk2 themes, that you use xset -b to turn off beeps in your terminals. Stuff like that is nice, though it is not an OpenBSD thing, I would like it more to read one OpenBSD centric document over a bunch of random guides to X that make Linux-centred assumptions.
Whoever modded that offtopic isn't really paying attention to the topic. That was a suggestion of a filesystem.
Oh, right, like we saw happen with Vorbis, X and BSD. Wait, no, that didn't happen.
If they had given this an MIT-like license, then I would be glad. As it stands, I am more indifferent then pleased with this particular event.
I also find it odd that people are comparing this to the Ogg work by Xiph, because it is not the same at all. This means that one can use this code as a guide to creating something more broadly open using this new codec.
Forgive me if incorrect, but I thought they were handed the monopoly by IBM, were they not?
I don't emulate Linux when I can run something from OpenBSD, sure I could tell the programme that it's running on Linux but it is not needed and would be of no benefit.
Tonkat (The OS Now Known As Tonkat) actually sounds much better than Linspire. Though the Tomcat people may disagree.
Exactly. How's the gas supposed to wind the mechanism? I suppose if it's a watermill design it may get some crummy milage out of it, but that's the only benefit I can see out of gassing it.
My machine is only a P2 450 with 192 MB of (broken) RAM. Setting my limits to unlimited and running nothing but the make, it cannot do it.
The song's been covered like 4 times, but Wayne wrote it and performed it first.
Read the following for more information: http://www.tsimon.com/lastkiss.htm
Considering the work required to make a relyricing, I would have at least thought you'd do a little reading up on the song.
I am pretty sure the result would be sphere and cube's across the galaxy turning blue and dying about once every month.
Because of the way ports and packages are designed this complation issue of yours does not happen.
You do not need to configure anything to compile a port, you need to run "make install" after enabling root permissions or getting sudo setup.
Packages are not the norm by any stretch of the imagination for anyone I know that uses a BSD. Installing a pkg works fine as long as you also have the dependancies it will just install the same as if you made from a port and I have never found a port in the 3.3 release that installs broken not bad for the 193 I use for my desktop.
The only messed up compile I've ever seen is xmame+xmess, which my machine could not handle cause it doesn't have enough resources to compile it.
OpenBSD is equally able to use the ports and pkgs in it's system because the system was designed for Open.