Yeah, especially after that minor incident that happened in the 60s where we blockaded Cuba. You know, the one that caused DEFCON to be raised to 2 and the creation of the "nuclear football" shortly thereafter.
As somebody who is not an American citizen, he likely cannot get security clearance to work for the American miliatary aerospace industry...
Well, first of all, you don't always need a security clearance to work in the military aerospace industry. Different services of the U.S. military have different security requirements for contractors. Since everything is done on a, "need to know basis", sometimes even people with clearance aren't working with anything considered, "secret". It's also quite common to have people with no security clearance working on projects with others that require security clearance. The people without clearance, simply don't work on and don't know about the secret aspects of the system.
In fact, I remember a code review where the guy who wrote the code didn't have a security clearance, but the code reviewers did. Every time they had to discuss the secret aspects of the system, they would send him out of the room. That may seem weird, as he was the code's author, but it was his code's integration to the rest of the system they were discussing, not specific portions of his code.
Secondly, I worked with one guy who had a secret clearance even though his parents were Vietnamese nationals. Under strict interprtation of the law at that time, I think it would have been considered illegal for him to have any sort of contact with his parents. In other words, even in situations where it seems unlikely that a person would get a security clearance, they are still able to get one if the person's expertise is necessary for the contract.
and that's the only one that still exists, everyone else buys from the USA.
In this case, depending on the requirements of the contract with the foreign government, he might not need clearance.
The bill has powerful backers. Among the bill's co-sponsors are Senate Majority Leader Bill Frist, a Tennessee Republican, Senate Minority Leader Tom Daschle, a South Dakota Democrat and Judiciary Committee ranking Democrat Patrick Leahy from Vermont.
The later one was done by The Washington Post (yahoo news link) and shows another view of those 3 distributions, from someone that seems to dislike Linux and don't know a enough about it.
This article submission was written by someone that seems to dislike English and doesn't know enough about it.
If they are like me, they may want to carry that DVD around. They may want to watch in in the office, at home, in a notebook, in a weekend place, in a boat, you name it. No matter how "transparent" you want to make it, DRM is always a bother.
Academy members don't watch the movies for entertainment purposes.
Analog. Plug a VCR into the analog out and a $30 'video stabelizer' and you got a copy.
The movie has embedded watermarks. If you attempt to do this, copies can be tracked to the academy member who gave you the disk, and ultimately to you.
In that case, why does the page I posted a link to list SAX as a deprecated API of Java 1.4.2, and SAX2 as its replacement?
You're kidding right? This change happened more than 4 years ago, and since SAX is a cross-platform API, other languages were affected too.
The SAX API evolved to include Namespace support for version 2. At the same time, some classes were deprecated in favor of newer classes. IIRC, the community asked for this, so it wasn't like it suddenly changed overnight. In this case, only the following classes from the entire SAX API were deprecated:
org.xml.sax.Parser
org.xml.sax.DocumentHandler
org.xml.sax.AttributeList
org.xml.sax.HandlerBase
org.xml.sax.helpers.ParserFactory
org.xml.sax.helpers.AttributeListImpl
The deprecated classes are still packaged with the JDK. If you're really intent on using obsolete classes, go ahead. Personally, I like being able to parse namespaces.
Again, SAX is not a Sun API. Sun updated their implementation to match the SAX specification, as did other implementors (like Microsoft). If you have issues with SAX1 deprecation, please contact the author.
Father:
Is this your graph?
Son:
No... I mean I...
Father:
Answer me! Who taught you how to do this?
Son (tearful):
You, OK? I learned it by watching you!
Slashdot Mirror
Yeah, especially after that minor incident that happened in the 60s where we blockaded Cuba. You know, the one that caused DEFCON to be raised to 2 and the creation of the "nuclear football" shortly thereafter.
Well, first of all, you don't always need a security clearance to work in the military aerospace industry. Different services of the U.S. military have different security requirements for contractors. Since everything is done on a, "need to know basis", sometimes even people with clearance aren't working with anything considered, "secret". It's also quite common to have people with no security clearance working on projects with others that require security clearance. The people without clearance, simply don't work on and don't know about the secret aspects of the system.
In fact, I remember a code review where the guy who wrote the code didn't have a security clearance, but the code reviewers did. Every time they had to discuss the secret aspects of the system, they would send him out of the room. That may seem weird, as he was the code's author, but it was his code's integration to the rest of the system they were discussing, not specific portions of his code.
Secondly, I worked with one guy who had a secret clearance even though his parents were Vietnamese nationals. Under strict interprtation of the law at that time, I think it would have been considered illegal for him to have any sort of contact with his parents. In other words, even in situations where it seems unlikely that a person would get a security clearance, they are still able to get one if the person's expertise is necessary for the contract.
and that's the only one that still exists, everyone else buys from the USA.
In this case, depending on the requirements of the contract with the foreign government, he might not need clearance.
That's why I switched to the WASDDaemon.
Does this count as a frist psot?
IBM Microdrives are hard disks in a CompactFlash type II form factor, not memory drives. You can pick up a 360MB for about 50 bucks now. Pretty sweet.
Installing Debian never made anyone look like a dork.
What? Installing off the camera!?!
Oh, I get it. Nevermind.
Ahhhh, yes. Broadcom has never been very friendly towards driver developers.
The good news is, your card works under Linux with NdisWrapper.
Which Linksys 802.11g card has either a Prism or Atheros chip?
The WUSB54G has a Prism Chipset.
The WPC55AG and WMP55AG have Atheros chipsets.
Bullshit!
There are Linux drivers for both Prism and Atheros chipsets, which are used in Linksys and Netgear cards.
This article submission was written by someone that seems to dislike English and doesn't know enough about it.
You'll never be allowed on a military base with one of those in your head.
This will be in Michael Moore's next film. </satire>
That's way too unstable for me. Don't they support a UPS? Sheesh.
</satire>
(setq make-backup-files nil) is your friend.
Academy members don't watch the movies for entertainment purposes.
The movie has embedded watermarks. If you attempt to do this, copies can be tracked to the academy member who gave you the disk, and ultimately to you.
Hence the "funny" moderation. :)
Now if only I could think of something nasty to say about Macedonia.
Clickable link for above
Oh, cool. I'll try that next time. Thanx.
Wait... How were you able to keep yourself from touching the person taking your virginity? You sir, are blessed with Budda-like self control.
You're kidding right? This change happened more than 4 years ago, and since SAX is a cross-platform API, other languages were affected too.
The SAX API evolved to include Namespace support for version 2. At the same time, some classes were deprecated in favor of newer classes. IIRC, the community asked for this, so it wasn't like it suddenly changed overnight. In this case, only the following classes from the entire SAX API were deprecated:
- org.xml.sax.Parser
- org.xml.sax.DocumentHandler
- org.xml.sax.AttributeList
- org.xml.sax.HandlerBase
- org.xml.sax.helpers.ParserFactory
- org.xml.sax.helpers.AttributeListImpl
The deprecated classes are still packaged with the JDK. If you're really intent on using obsolete classes, go ahead. Personally, I like being able to parse namespaces.Again, SAX is not a Sun API. Sun updated their implementation to match the SAX specification, as did other implementors (like Microsoft). If you have issues with SAX1 deprecation, please contact the author.
That's easy! Exactly four.
Here's the list:
No, no, no. You've got it all wrong. Sex is like air. You never realize how bad you need it until you aren't getting any.
How I learned it:
Parents who use graphs have kids who use graphs.