I think you should know that you're engaging in the same kind of ideological wordmongering you accuse the other side of.
Look, I'm a pragmatic open source user. I understand the ideology.I generally agree to it. But not because of its perceived social Rightness, but because it's a reliable source of Good Bits. Its ideology supports methodology which supports good stuff like working kernels.
Upthread, I chastised a Free Software hyperbolist for being unrealistic and ignoring the practical side. Now I'm going to do the same in the other direction here.
The taint flag is a disclaimer of warranty.
What it comes down to is:
If you use only this open source software, we the developers can troubleshoot it with you, because no matter where the bug lies, we can find it. But if you inject a piece of kernel code which is only known as a black box... all bets are off. At best, we might conceivably help you chase the problem down into this black box, at which point we can only shrug and walk away. But the very real worst-case scenario is that the closed-source module does things to unrelated parts of the kernel which simply cannot be traced because of their origin. The kernel is, after all, a single shared memory space running at a single common privilege level, so you're giving carte blanche to a piece of driver you can neither inspect or verify. And trying to debug that quagmire would be massively unproductive. Really, we'd rather not waste time which would be better spent working on the real open source code and solving problems we actually can solve. So, rather than make any promises in this situation, my NDISWrapping friend, we the kernel developers can only tell you "Y'all on your own, dog!"
(BTW, that's not a real quote from any kernel developer I know of. It's just intended to express one good functional reason for kernel taintedness.)
See, no hysteria, no missionary fervor, no revolutionary speeches or dialectical materialism or any of that. Just practical reasons based on a balance of costs and benefits.
How do I run this "GPL" solution on my Sparc-based Linux system? The card is PCI but the binary that gets loaded runs on Intel-only. So it's compatible hardware, and software that claims to be GPL, but the system is a doorstop.
So, you're hosed. That has nothing to do with me. NDISWrapper works for me. You solve your own problem, in ways that don't try to deny me my workaround.
NDISwrapper is not a bandage, it is a Typhoid Mary allowing proprietary software to infect the kernel.
Oh, get over yourself. It's a workaround. It solves nothing but a user's immediate problem: using hardware with no native support.
"Buy supported hardware" is not always an answer. Yes, it's the best solution, but sometimes you have no choice except either use what you've got the best you can (including ugly kluges like NDISWrapper), or use nothing at all... and that's never a solution.
Yeah, there are numerous pragmatic limitations to crap like NDISWrapper. Non-GPL taint warnings are there for a reason: to remind you that you may chase a problem into the dank impenetrable thicket of the proprietary driver... at which point you're SOL. Likewise if you need features the NDIS driver doesn't support.
But in a few cases, the choice is between doing something distasteful and doing nothing at all. And that is neither a valid choice or an absolutely necessary one as long as everyone involved is honest and aware of the limitations and compromises involved.
And calling NDISWrapper "Happy happy GPL joy" isn't either honest or mindful of the very real issues. But hyperbolizing it as a disease vector isn't either.
The Cyclons on the other hand are unswervingly devoted to their God.
That's a generalization, and still wrong when there are only 12 personality basetypes to compare.
Specifically, the "Brother Cavil" model seems to be persistently atheist in all incarnations shown.
I believe there's an intentional parallel with western secular 'Christians' and extremist Muslims.
That's an easy assumption, but there's a practical inconsistency there: the Cylons are a functional nation-state complete with a high-tech standing army which the Colonials are in active war with. Extremist Islam has no such state. At least, not one which is actively at war with any nation of the West. So the comparison to any current situation is seriously flawed. If you focus on just the differences in religion and want to see a connection to behavior and interactions between the factions, you can certainly see it, but it's not cut and dried.
E1.2.2.1. To be eligible for enlistment in the Regular Army or Air Force, an individual must be an American citizen, or lawfully admitted to the United States for permanent residence (10 U.S.C., 3253 and 8253, reference (a)). There is no equivalent statute limiting enlistment in the Regular Navy and Marine Corps, but they usually apply the same citizenship requirements as those required for the Army and Air Force.
E1.2.2.2. To be eligible for enlistment in the Reserve components, an individual must be a citizen of the United States or lawfully admitted to the United States for permanent residence (10 U.S.C., 510, reference (a)).
E1.2.2.3. To be eligible for appointment as a commissioned or warrant officer, U.S. citizenship is required except for Reserve appointment where an individual must be lawfully admitted to the United States for permanent residence (Sections 532 and 591 of reference (a)). For regular appointment, when tendered, U.S. citizenship is required. Law requires National Guard officers to be U.S. citizens (32 U.S.C., 313, reference (c)).
E1.2.2.4. Citizens of the Federated States of Micronesia or the Republic of the Marshall Islands also are eligible for enlistment in the Active and Reserve components. (See the Compact of Free Association (reference (d)).)
Note the phrase "lawfully admitted to the United States for permanent residence". That's a Green Card.
Now, don't expect to get any kind of clearance unless you're a citizen, so expect some real limits to the specialties you can be assigned to. But "join"? Absolutely.
Some say the world will end in fire,
Some say in ice.
From what I've tasted of desire
I hold with those who favor fire.
But if it had to perish twice,
I think I know enough of hate
To say that for destruction ice
Is also great
And would suffice.
So what you're saying is... you can run BIND and still have this problem. You know, running a caching server.
And you said you weren't running a caching server... when?
But yes, in the standard config, going to the root server as your first hop bypasses the ISP DNS's tendency to lie. Unless your invalid address falls into your lying ISP's DNS zone. Then you'll get lies. So, if you're asking for asdffasdf.com, you're OK, you'll get the root saying "not found". And if you ask for "asdffasf.notsuckingisp.com", you'll get an honest "not found" from notsuckingisp.com's DNS. But if you ask for asdffasdf.rr.com, you wind up asking Road Runner. Which we know will lie. So the problem's not eliminated, just reduced.
Now the other problem, your tendency to not mention the most important part of your argument and then yell "FAIL" at anyone who fails to read your mind... sorry, a local BIND installation can't help you there.
And what's your upstream DNS provider? If it's Road Runner, I bet you'll get bogus A records returned, no matter what protocol you intend to use the resulting IP address with. Similarly with OpenDNS, as far as I can tell.
And I hope for your sake you're running a recent version of BIND. That thing is epic in terms of ancient (but now closed) remote exploit opportunities.
I mean, after "Never get involved in a land war in Asia" and "Never go in against a Sicilian when death is on the line", the most famous rule is "Never back Sony in a format war." And here they are, winning one!
So yeah, throwing flagrant amounts of money at potential customers kinda changes the calculus a bit. Sony media format marketing without bribery* is like the getting the dog to play with the ugly kid without the steak tied around his neck.
*Well, to be perfectly fair, Sony's 3.5" floppy diskette format did win. Maybe there was some bribery involved there too?
They were, extensively, until the IBM 5150 started making serious market share inroads. (Of course, it's true that more "serious businesses" ran CP/M systems, and that's the market the IBM system ate up. But there were business TRS-80s as well as "home PC" TRS-80s used in businesses.
And let's face it, it's a bit disingenuous to say had "IBM had 100% of the PC-compatible market" when there was only one system compatible with the 5150 in the world at the time and it was the 5150. That stage lasted only about a year.
What kind of anarcho-retard are you? Laws exist precisely to prevent you from doing what "you" think "you should be doing yourself." You know, "take the law into your own hands"? Which, in case you didn't now this, is bad. Not good. Bad. If someone breaks into your house and steals your stuff, you don't hunt them down and take the stuff back (or kill them for the crime). Sticking up for yourself is fine in principle, but you shouldn't have to stick up for yourself very often. The law should remind people that attacking anyone else is not acceptable whether or not they can defend themselves.
Well, teens have been exposed to illnesses and predatory animals and life-threatening accidental injuries since the beginning of time, and most survive those just fine too. Society still makes a point of trying to mitigate those risks, because civilization acts to protect its weakest and most vulnerable members.
Emotional abuse in certain settings can be construed legally as assault. (Consider domestic violence.) This case avoids that status because the perpetrator, though occupying an emotional role and carrying emotional force comparable to an abusive spouse, had no such legal standing.
The "tough it out, it's just words" argument is just a "blame the victim" cop-out.
To my mind, the more amazing thing is how fast the Navy got the systems involved modified to track and kill a target the weapons weren't originally designed for. Talk about agile development!
And you have to consider how much time thawing out the frozen hydrazine will buy you in terms of re-entry survival (before boiling and pressure increase and all that catastrophic stuff). Yes, frozen. It was a 1/2 ton hydrazine ice cube. It would have to thaw before it could boil.
It seems that the likelihood of a semi-intact landing of the tank isn't a complete fairy tale.
Slashdot Mirror
Actually, he'd detect the wink accurately.
The gender of the winker, though...
Every get the feeling that the summary was written by someone who doesn't quite grasp all the relevant details of the topic?
You mean, edited by a typical /. editor? Yeah, it felt just like that.
Vinge thought that "Programmer-archaeologist" might be a growth career area.
"Tim Couch sets the value of pi to 3.2 in the state of Kentucky"
Well, it almost worked for Indiana.
Think of it as an avian spoofed RESET packet.
I'm sure Comcast is evaluating it even as we speak...
If so, then many slashdotters are no longer virgins.
I think you should know that you're engaging in the same kind of ideological wordmongering you accuse the other side of.
Look, I'm a pragmatic open source user. I understand the ideology.I generally agree to it. But not because of its perceived social Rightness, but because it's a reliable source of Good Bits. Its ideology supports methodology which supports good stuff like working kernels.
Upthread, I chastised a Free Software hyperbolist for being unrealistic and ignoring the practical side. Now I'm going to do the same in the other direction here.
The taint flag is a disclaimer of warranty.
What it comes down to is:
(BTW, that's not a real quote from any kernel developer I know of. It's just intended to express one good functional reason for kernel taintedness.)
See, no hysteria, no missionary fervor, no revolutionary speeches or dialectical materialism or any of that. Just practical reasons based on a balance of costs and benefits.
How do I run this "GPL" solution on my Sparc-based Linux system? The card is PCI but the binary that gets loaded runs on Intel-only. So it's compatible hardware, and software that claims to be GPL, but the system is a doorstop.
So, you're hosed. That has nothing to do with me. NDISWrapper works for me. You solve your own problem, in ways that don't try to deny me my workaround.
NDISwrapper is not a bandage, it is a Typhoid Mary allowing proprietary software to infect the kernel.
Oh, get over yourself. It's a workaround. It solves nothing but a user's immediate problem: using hardware with no native support.
"Buy supported hardware" is not always an answer. Yes, it's the best solution, but sometimes you have no choice except either use what you've got the best you can (including ugly kluges like NDISWrapper), or use nothing at all... and that's never a solution.
Yeah, there are numerous pragmatic limitations to crap like NDISWrapper. Non-GPL taint warnings are there for a reason: to remind you that you may chase a problem into the dank impenetrable thicket of the proprietary driver... at which point you're SOL. Likewise if you need features the NDIS driver doesn't support.
But in a few cases, the choice is between doing something distasteful and doing nothing at all. And that is neither a valid choice or an absolutely necessary one as long as everyone involved is honest and aware of the limitations and compromises involved.
And calling NDISWrapper "Happy happy GPL joy" isn't either honest or mindful of the very real issues. But hyperbolizing it as a disease vector isn't either.
The Cyclons on the other hand are unswervingly devoted to their God.
That's a generalization, and still wrong when there are only 12 personality basetypes to compare.
Specifically, the "Brother Cavil" model seems to be persistently atheist in all incarnations shown.
I believe there's an intentional parallel with western secular 'Christians' and extremist Muslims.
That's an easy assumption, but there's a practical inconsistency there: the Cylons are a functional nation-state complete with a high-tech standing army which the Colonials are in active war with. Extremist Islam has no such state. At least, not one which is actively at war with any nation of the West. So the comparison to any current situation is seriously flawed. If you focus on just the differences in religion and want to see a connection to behavior and interactions between the factions, you can certainly see it, but it's not cut and dried.
Whose military?
The U. S. military?
Wrong. Since you use the phrase "join" you mean "enlist". (The officer equivalent of join is "be commissioned" or "be appointed".)
Quoting DoD Directive 1304.26, "Qualification Standards for Enlistment, Appointment,and Induction":
Note the phrase "lawfully admitted to the United States for permanent residence". That's a Green Card.
Now, don't expect to get any kind of clearance unless you're a citizen, so expect some real limits to the specialties you can be assigned to. But "join"? Absolutely.
I think our GIs have better things to spend their time on than trying to distill truth from the "facts" vomited by malcontents and partisan hacks.
I agree wholeheartedly! That's why I wonder why those "malcontents" and "partisan hacks" aren't being blocked, just honest bloggers.
--- Robert Frost
So what you're saying is... you can run BIND and still have this problem. You know, running a caching server.
And you said you weren't running a caching server... when?
But yes, in the standard config, going to the root server as your first hop bypasses the ISP DNS's tendency to lie. Unless your invalid address falls into your lying ISP's DNS zone. Then you'll get lies. So, if you're asking for asdffasdf.com, you're OK, you'll get the root saying "not found". And if you ask for "asdffasf.notsuckingisp.com", you'll get an honest "not found" from notsuckingisp.com's DNS. But if you ask for asdffasdf.rr.com, you wind up asking Road Runner. Which we know will lie. So the problem's not eliminated, just reduced.
Now the other problem, your tendency to not mention the most important part of your argument and then yell "FAIL" at anyone who fails to read your mind... sorry, a local BIND installation can't help you there.
And what's your upstream DNS provider? If it's Road Runner, I bet you'll get bogus A records returned, no matter what protocol you intend to use the resulting IP address with. Similarly with OpenDNS, as far as I can tell.
And I hope for your sake you're running a recent version of BIND. That thing is epic in terms of ancient (but now closed) remote exploit opportunities.
I bet your vanity plate "DIE PIG" attracted lots of law enforcement interest.
I mean, after "Never get involved in a land war in Asia" and "Never go in against a Sicilian when death is on the line", the most famous rule is "Never back Sony in a format war." And here they are, winning one!
So yeah, throwing flagrant amounts of money at potential customers kinda changes the calculus a bit. Sony media format marketing without bribery* is like the getting the dog to play with the ugly kid without the steak tied around his neck.
*Well, to be perfectly fair, Sony's 3.5" floppy diskette format did win. Maybe there was some bribery involved there too?
No wireless. More keyforce than an IBM Model M. Lame.
Of course he has the receipt; it's filed with his $699 SCO Linux license receipt.
(I'm gonna refrain from paraphrasing the rest of the troll quote, something about smoking roosters and making tea.)
They were, extensively, until the IBM 5150 started making serious market share inroads. (Of course, it's true that more "serious businesses" ran CP/M systems, and that's the market the IBM system ate up. But there were business TRS-80s as well as "home PC" TRS-80s used in businesses.
And let's face it, it's a bit disingenuous to say had "IBM had 100% of the PC-compatible market" when there was only one system compatible with the 5150 in the world at the time and it was the 5150. That stage lasted only about a year.
Not a murder, probably. But quite possibly a manslaughterer and a reckless endangerer.
What kind of anarcho-retard are you? Laws exist precisely to prevent you from doing what "you" think "you should be doing yourself." You know, "take the law into your own hands"? Which, in case you didn't now this, is bad. Not good. Bad. If someone breaks into your house and steals your stuff, you don't hunt them down and take the stuff back (or kill them for the crime). Sticking up for yourself is fine in principle, but you shouldn't have to stick up for yourself very often. The law should remind people that attacking anyone else is not acceptable whether or not they can defend themselves.
Well, teens have been exposed to illnesses and predatory animals and life-threatening accidental injuries since the beginning of time, and most survive those just fine too. Society still makes a point of trying to mitigate those risks, because civilization acts to protect its weakest and most vulnerable members.
Emotional abuse in certain settings can be construed legally as assault. (Consider domestic violence.) This case avoids that status because the perpetrator, though occupying an emotional role and carrying emotional force comparable to an abusive spouse, had no such legal standing.
The "tough it out, it's just words" argument is just a "blame the victim" cop-out.
Well, cost is a valid argument.
Public sources put the cost of the shot at $40-$60 million. In DoD funding terms, that's pocket change.
To my mind, the more amazing thing is how fast the Navy got the systems involved modified to track and kill a target the weapons weren't originally designed for. Talk about agile development!
It seems that the likelihood of a semi-intact landing of the tank isn't a complete fairy tale.
Where else do they grow bananas?