Automatic doors were invented by Dee Horton and Lew Hewitt in 1954, and lifting body aerodynamics (like the shape of Farscape-1) were invented by Dr. Alfred J. Eggers Jr. at NASA Dryden in 1957.
Really makes you think just how vunerable you are to these.
Actually...it really makes me wonder why in the world one would go unpatched these days. It's not like Welicha was the first warning that that's a pretty st00pid way to do business.
Dr. Geer is (ok, was) the Chief Technical Officer of @Stake. This is a position of authority in a particular field and stating that one has that authority gives one's opinion in that field certain standing. It is a factual statement and does not imply endorsement by his employer. It only imlies that one has recognized special skills.
CTO is also a specific position in a company, almost always an "officer of the company". Being an officer of the company entails responsabilities that cannot be set down simply by going "off the record" or as "personal opinion". Geer got fired (quite legally) because as an officer of the company he did something that knowingly had the potential to damage an important business relationship, apparently did it without consulting other executives, and that's in conflict with his responsabilities as an officer of the company.
At many companies (including the one that I currently work for), there is even a specific oversight process that must vet any public statement by an officer of the company. Not following this process will get one fired no matter what the statement was.
That's not to say what he said was wrong, or that this situation is "right"...we're talking law here, after all.
It's actually more complicated than that. As a former CTO, our lawyers had a chat with me about this topic.
A regular employee of a company can go "off the record", at least in theory. Any "officer of the company" (C-level executive (CEO, CIO, CTO), VP-level, sometimes Director level) has to play by different rules and really can't, especially if what they are say would potentially hurt the company in some meaningful way. At that level of management, they have implied authority and representation in all contexts and a fiduciary responsibility to the company that transcends personal views.
Right or wrong, from a legal standpoint the execs at @Stake are on very solid ground in firing Mr. Geer if they see his paper as damaging their (probably lucrative) relationship with M$.
Nice troll. You know...all I ever hear is Stallman and associated syncophants telling people not to use *BSD because it's not "free", at least by their definition. Which is, of course, the only valid one. Hypocracy indeed.
I think the point is that ignoring the problem will not make it better.
If you've been a victim of identity theft, you need to know that right now and start fixing it. If it's a mistake, then correct it. If you have an outstanding debt, then you need to pay it.
When I was at Georgia Tech, AT&T carpet bombed the place with their equipment (3b20s, 3b2s, AT&T 5620s, etc). Was this "just making sure that they secure themselves another generation of coders/admins/users"? Of course it was. Did anyone complain? Not a one. Well...other than the fact that the 3b stuff was slow and unreliable...but that's a different issue. Did it have an effect? You bet...other than a few CDC Cyber holdouts, we were all Unix bigots.
Some time later, Sun did about the same thing, with the same result.
Microsoft would be pretty foolish not to take the example. It's good buisiness.
Sun already lost the desktop with Solaris on SPARC so they have nothing to lose.
Not sure if I agree with that.
I have several thousand SPARC/Solaris desktops in my company, mostly late-model Ultras and Blades. Sun might have conceeded the non-technical or business desktop, but there are still large numbers of technical desktops still on Solaris (as witnessed by the sales numbers for the Blades). Loosing that to Intel/Linux would be bad for Sun.
I wounder if that desktop expansion will be more at the expense of Microsoft or Sun (and to a lesser extent SGI, I suppose). Replacing relatively expensive Solairs desktops with Linux is straightforward; replacing M$ generally requires a shift in how applications are delivered (e.g. a move to web-based or Java applications).
i thought it was C4 clearance, and that took years to get.
It's C2; there's no such thing as C4. C2 isn't terribly hard to get (lot's of auditing and doco requirements). However, since C2 isn't a particularly interesting or useful security classification except for marketing (DAC systems are strictly for unclassified environments), most vendors don't bother with it until they start selling lots of stuff into the gov/mil/intel areas.
B-level secure systems are another story entirely.
A google for motorola 68015 sure does point to a lot of pages about a chip that never existed.
No.
If you actually look at the entries, Google shows a small number of hits none of which are for a 68015 processor (although the first one sorta implies one but a "VME 68015" doesn't imply a 68015 processor; it's probably a typo anyway).
There was the ubiquitous 68000, a somewhat common 68010, an exceedingly rare if ever produced in quantity 68012, never a 68015, then a 68020. That and the rest is well documented history.
We are a Cisco shop at work (with the 350-series AP). The hardware has been reliable, though the software has had teething pains. A tad expensive for the home user.
At home I have a Linksys WAP51AB dual band AP. I've had one or two times where the box has frozen and one time where the A radio froze, but the B didn't. Overall, it's a reasonably good product other than the A radio having disappointing performance and the fact that it seems to have marginal support since the intoduction of the B+G products.
FWIW...the 2-3 years before I got the Linksys, I had a Nokia 11b AP (only 1MB, though, and no WEP...not exactly featureful) that ran flawlessly.
Reasonably usable fast ethernet chip. Interface suited for embedded processors (e.g. it's non-PCI). Source code for Linux driver on the web site (though it's for 2.0). You should be able to look at other drivers for other FEAST-based cards for newer drivers.
As another poster pointed out, magnetics are external for nearly all ethernet chips.
Did you try to get escalated to a higher support tier or to a supervisor? I've found that generally works as long as you are persistent.
Level 1 support at most ISPs don't have any technical skills. They walk through a series of scripted interactions and weed out the 99% of calls that are simple to solve. Good for the ISP, but bad for the 1% highly technical callers.
It's also possible that there is a specific security group that you could contact. You might have to be persistent to find them, however.
Having spent lots of money with lawyers over this sort of thing...
First let me say that there is a distinction between "what is right" and "what is legal". Many things that are not legal are right, and vice versa. I'm not interested in getting into a lot of "but that's not right!" arguments; I'm simply relating what the legal realities are as I understand them.
The only way to really be safe is to write down exactly what it is that you intend to contribute and get an officer of your company (or other superior who clearly has the authority to commit the company) to sign off acknowledging that the company will make no claims against your contribution. Stick to what has been agreed to, and get written addendums if there is "scope creep" on your open source project.
If they won't sign off in writing, you can assume that they will take action of some kind against you if you decide to do it anyway. As my lawyer used to say "contracts aren't for when people are happy with one another". Might be a good idea to look at other options (of employment, if you're committed is to your OSS project).
I would also note that unlike some wildly misguided people I've heard recently, you cannot simply take something you don't own (in the legal sense), release it with a GPL notice on top, and be free and clear legally. Sure, that code can't be "called back", but you (and people who use your code assuming you had the right to apply the GPL to that work) might very well find yourself in court. Ownership of the code (and thus who has the right to determine the license) is determined by the contract you entered into, and the courts will decide your fate based on that.
Be aware that some employment contracts state things to the effect that anything you do "in the field" can be claimed by your employer. Thus, just because your contribution is done on your own time with your own equipment, you still could be liable for action. Know exactly what your employment contract says (hopefully you did that before you signed it). Have a laywer (your own laywer) explain it to you if you aren't very familiar with contract language.
Also note that simply not signing an IP agreement does not automatically absolve you of its terms. Look for other employment paperwork that says things like "by accepting employment you implicitly agree to all our required employment contracts". I've definately seen people bit hard by this. If your employer has an IP agreement, then negotiate the terms you want and sign that so that all is tidy and legal. Again, consult your own lawyer to know exactly where you stand.
Know your rights under state law. Different states have wildly different interpretations of the strength of employment agreements. Contract language which would bind you up in one state might very well be tossed out as onerous in another. Consult a lawyer.
You do not want to litigate over this; you want to avoid putting yourself in that position. Even if you win, it's generally very expensive, annoying, frustrating and you'll often as not loose the job as a result. Don't sue "on principle" unless you know you have enough money, time, etc., to survive the process (including the possibility of loosing...no matter how strong you think your case is, the legal world is bizzarro world, and outcomes are not always deterministic). Special Fact - generally, if you sue your company (e.g. to claim ownership), and they decide to countersue you (say, for breach of contract), you won't be able to drop your suit (even if you run out of money), unless the other party agrees to it. Hint - they won't unless you back down.
Lastly...do not simply take your managers verbal word that there will be no problems. Get it in writing. There is a doctrine of "verbal contracts" (I suppose "implied authority" also plays here) under the law, but they are difficult to make stick, especially if the other side is determined to invalidate it. OTOH, "Paper has a perfect memory", as one of my old biz partners used to say.
N.B. - I can speak only for the U.S. There are different subtleties elsewhere...
It's very, very common for wealthy senior execs to sell of substantial (
The SEC requires such sales to be publicised as part of proper corporate disclosure. While the numbers involved are titilating, there's likely nothing more interesting involved.
Slashdot Mirror
DS3 is 45MBps (well...44.736 for you anal retents).
http://www.dfrc.nasa.gov/Newsroom/FactSheets/FS-01 1-DFRC.html
Automatic doors were invented by Dee Horton and Lew Hewitt in 1954, and lifting body aerodynamics (like the shape of Farscape-1) were invented by Dr. Alfred J. Eggers Jr. at NASA Dryden in 1957.
Actually...it really makes me wonder why in the world one would go unpatched these days. It's not like Welicha was the first warning that that's a pretty st00pid way to do business.
CTO is also a specific position in a company, almost always an "officer of the company". Being an officer of the company entails responsabilities that cannot be set down simply by going "off the record" or as "personal opinion". Geer got fired (quite legally) because as an officer of the company he did something that knowingly had the potential to damage an important business relationship, apparently did it without consulting other executives, and that's in conflict with his responsabilities as an officer of the company.
At many companies (including the one that I currently work for), there is even a specific oversight process that must vet any public statement by an officer of the company. Not following this process will get one fired no matter what the statement was.
That's not to say what he said was wrong, or that this situation is "right"...we're talking law here, after all.
A regular employee of a company can go "off the record", at least in theory. Any "officer of the company" (C-level executive (CEO, CIO, CTO), VP-level, sometimes Director level) has to play by different rules and really can't, especially if what they are say would potentially hurt the company in some meaningful way. At that level of management, they have implied authority and representation in all contexts and a fiduciary responsibility to the company that transcends personal views.
Right or wrong, from a legal standpoint the execs at @Stake are on very solid ground in firing Mr. Geer if they see his paper as damaging their (probably lucrative) relationship with M$.
Nice troll. You know...all I ever hear is Stallman and associated syncophants telling people not to use *BSD because it's not "free", at least by their definition. Which is, of course, the only valid one. Hypocracy indeed.
That's what you get for running Windows...
If you've been a victim of identity theft, you need to know that right now and start fixing it. If it's a mistake, then correct it. If you have an outstanding debt, then you need to pay it.
Some time later, Sun did about the same thing, with the same result.
Microsoft would be pretty foolish not to take the example. It's good buisiness.
Not sure if I agree with that.
I have several thousand SPARC/Solaris desktops in my company, mostly late-model Ultras and Blades. Sun might have conceeded the non-technical or business desktop, but there are still large numbers of technical desktops still on Solaris (as witnessed by the sales numbers for the Blades). Loosing that to Intel/Linux would be bad for Sun.
I wounder if that desktop expansion will be more at the expense of Microsoft or Sun (and to a lesser extent SGI, I suppose). Replacing relatively expensive Solairs desktops with Linux is straightforward; replacing M$ generally requires a shift in how applications are delivered (e.g. a move to web-based or Java applications).
It's C2; there's no such thing as C4. C2 isn't terribly hard to get (lot's of auditing and doco requirements). However, since C2 isn't a particularly interesting or useful security classification except for marketing (DAC systems are strictly for unclassified environments), most vendors don't bother with it until they start selling lots of stuff into the gov/mil/intel areas.
B-level secure systems are another story entirely.
This is correct, and it must be the correct JVM. This has been an issue in our testing.
No.
If you actually look at the entries, Google shows a small number of hits none of which are for a 68015 processor (although the first one sorta implies one but a "VME 68015" doesn't imply a 68015 processor; it's probably a typo anyway).
There was the ubiquitous 68000, a somewhat common 68010, an exceedingly rare if ever produced in quantity 68012, never a 68015, then a 68020. That and the rest is well documented history.
At home I have a Linksys WAP51AB dual band AP. I've had one or two times where the box has frozen and one time where the A radio froze, but the B didn't. Overall, it's a reasonably good product other than the A radio having disappointing performance and the fact that it seems to have marginal support since the intoduction of the B+G products.
FWIW...the 2-3 years before I got the Linksys, I had a Nokia 11b AP (only 1MB, though, and no WEP...not exactly featureful) that ran flawlessly.
Reasonably usable fast ethernet chip. Interface suited for embedded processors (e.g. it's non-PCI). Source code for Linux driver on the web site (though it's for 2.0). You should be able to look at other drivers for other FEAST-based cards for newer drivers.
As another poster pointed out, magnetics are external for nearly all ethernet chips.
Level 1 support at most ISPs don't have any technical skills. They walk through a series of scripted interactions and weed out the 99% of calls that are simple to solve. Good for the ISP, but bad for the 1% highly technical callers.
It's also possible that there is a specific security group that you could contact. You might have to be persistent to find them, however.
Once you dig that, start at the beginning of the Blue Note Records collection and let us know when you are done...:-)
First let me say that there is a distinction between "what is right" and "what is legal". Many things that are not legal are right, and vice versa. I'm not interested in getting into a lot of "but that's not right!" arguments; I'm simply relating what the legal realities are as I understand them.
The only way to really be safe is to write down exactly what it is that you intend to contribute and get an officer of your company (or other superior who clearly has the authority to commit the company) to sign off acknowledging that the company will make no claims against your contribution. Stick to what has been agreed to, and get written addendums if there is "scope creep" on your open source project.
If they won't sign off in writing, you can assume that they will take action of some kind against you if you decide to do it anyway. As my lawyer used to say "contracts aren't for when people are happy with one another". Might be a good idea to look at other options (of employment, if you're committed is to your OSS project).
I would also note that unlike some wildly misguided people I've heard recently, you cannot simply take something you don't own (in the legal sense), release it with a GPL notice on top, and be free and clear legally. Sure, that code can't be "called back", but you (and people who use your code assuming you had the right to apply the GPL to that work) might very well find yourself in court. Ownership of the code (and thus who has the right to determine the license) is determined by the contract you entered into, and the courts will decide your fate based on that.
Be aware that some employment contracts state things to the effect that anything you do "in the field" can be claimed by your employer. Thus, just because your contribution is done on your own time with your own equipment, you still could be liable for action. Know exactly what your employment contract says (hopefully you did that before you signed it). Have a laywer (your own laywer) explain it to you if you aren't very familiar with contract language.
Also note that simply not signing an IP agreement does not automatically absolve you of its terms. Look for other employment paperwork that says things like "by accepting employment you implicitly agree to all our required employment contracts". I've definately seen people bit hard by this. If your employer has an IP agreement, then negotiate the terms you want and sign that so that all is tidy and legal. Again, consult your own lawyer to know exactly where you stand.
Know your rights under state law. Different states have wildly different interpretations of the strength of employment agreements. Contract language which would bind you up in one state might very well be tossed out as onerous in another. Consult a lawyer.
You do not want to litigate over this; you want to avoid putting yourself in that position. Even if you win, it's generally very expensive, annoying, frustrating and you'll often as not loose the job as a result. Don't sue "on principle" unless you know you have enough money, time, etc., to survive the process (including the possibility of loosing...no matter how strong you think your case is, the legal world is bizzarro world, and outcomes are not always deterministic). Special Fact - generally, if you sue your company (e.g. to claim ownership), and they decide to countersue you (say, for breach of contract), you won't be able to drop your suit (even if you run out of money), unless the other party agrees to it. Hint - they won't unless you back down.
Lastly...do not simply take your managers verbal word that there will be no problems. Get it in writing. There is a doctrine of "verbal contracts" (I suppose "implied authority" also plays here) under the law, but they are difficult to make stick, especially if the other side is determined to invalidate it. OTOH, "Paper has a perfect memory", as one of my old biz partners used to say.
N.B. - I can speak only for the U.S. There are different subtleties elsewhere...
N.N.B. - IANAL, nor do I want to be...
It's very, very common for wealthy senior execs to sell of substantial ( The SEC requires such sales to be publicised as part of proper corporate disclosure. While the numbers involved are titilating, there's likely nothing more interesting involved.
Why do I still use Windows? Visio, and especially the VNE libraries. No...there is nothing even remotely equivalent in Linux.