Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Re:Israel has been doing this (Score 1) 553

When I was working for Intel, I went to Israel for training on a new VoIP product developed by a research lab there. On leaving, Israeli customs dude opened one of my training manuals, pointed to a block diagram and asked me to explain what it was. Now, I knew right away that he was completely ignorant of the stuff, but was looking to see if I would do the "hamina-hamina-hamina" thing. Also, they asked a lot of circular questions: what hotel did you stay at? what did you have for dinner on your first night? etc. Very thorough, I must say...

Comment Re:Automatically fired (Score 4, Insightful) 106

Sadly, a typical reaction today... Fire/LockUp/Execute Everyone Even Remotely Connected to Scandal-De-Jure...FFS, most of these same commenters also want to "shrink government", "cut taxes", etc. NONE of which is going to: improve training and testing; expand, fund and enforce standards across municipalities; enhance LEO capabilities to track and prosecute attackers. But - Hey! - we get to sound awful tough!!

Comment Corporate Stupidity (Score 5, Interesting) 225

I used to work at Dialogic, which was then bought by Intel. In all my time there, new prospects/customers would invariably say: "This is really hard to configure (we had line resource cards, DSP resource cards, and various ways to map these resources together.) don't you guys have a card configuration utility?" Well, for Windows, yes. For Linux, no. "Too hard and no demand" says Engineering. So, taking the bull by the horns, I found the PCI ID codes for the various cards, wrote a utility to configure them, got approval from my manager to release it as open-source and all was well. Until...The head of Engineering at our division found out about it and lodged a formal internal complaint that I had "released Intel proprietary information" and was summoned to Parsippany to face legal. Fortunately, my manager's support and basic common sense prevailed, the Eng manager was sent packing with his tail between his legs and I flew home drunk as a skunk. The legal guy basically said: "when you expose a PCI ID to the OS, it's no longer proprietary - dumbass!". Point is that when information is documented and exposed in any way, it is not "proprietary" in the sense that it cannot be used, just not stolen and used inappropriately.

Slashdot Top Deals

panic: kernel trap (ignored)