Posts by Prof. William Waterman Sherman 58 posts • joined 6 May 2010
I could screen calls quite efficiently myself, until the majority of nuisance callers began spoofing local numbers. Now, I'm more suspicious of local calls than out-of-state.
Not sure how spoofing caller-id is done, but putting an end to it would do more than anything else.
Agreed. I always thought Eric Schmidt was creepy (especially showing up at Burning Man to hang out with Tank Girl). I was baffled when he went to Google and was described as the "adult" who would help them run a real company. Everything he uttered to sound cutting-edge and original was, uh, creepy is the best word to describe it.
German counter intelligence was awful because of common Nazi pathologies: overconfidence in their superiority, paranoia and distrust of rival sister organizations, and reluctance to deliver bad news to higher ups. Lots of Nazis and German generals kept informal channels open to the allies through neutral countries. They weren't spies, just serving their own interests, especially when it was clear how things were going to end.
Plus, the allies were very careful to protect Ultra sources. Quite often they arranged for a plausible alternate event explain their apparent luck. Not many operational commanders were privy to the details. Notably, Patton was a big fan of Ultra and couldn't get enough.
That makes sense. A letter never encrypting as itself was one of the enigma device quirks exploited by the geniuses who cracked it.
Of course the heros of Bletchley Park are rightly lauded, but I don't think the Poles who got things rolling are given their due. Without mechanical aids, they replicated enigma's internal workings with string and paper tags. By the time they had a solution, a cat's cradle would fill the room. And they did this all while staying one step ahead of the Wehrmacht until they reached Britain.
Total agreement, here. And this snippet: "Apple's developers deserve to be paid for the hard work..." tells me you have experience in the black arts.
As an exercise in frustration, I tried standing up a Snow Leopard VirtualBox on my MacBook running Yosemite (to keep Rosetta around). Ostensibly legal, I never got it working right. I figured it would be easier running a Hackintosh VM on Windows and gave up the effort.
Da–I mean–right on. The Russian game was to cast democracy as a disorganized, chaotic mess, as much for domestic consumption as its effect on the States. Regardless of who won, it was win-win for Putin. He gets to show Russians how superior it is to be run by a strongman, and cause America to doubt its own institutions.
I hear newscasts on both sides talk of how Russia "hacked" our election. They didn't hack the election, but they did hack our culture. They certainly tried to hack our election computers. They had about as much success as they did hacking our power grid. Not a call for complacence, but certainly a call for computer illiterates to stop overreacting and making policy in a panic.
Personally, I think the old hand ballots scaled well. That was ruined by a small number of Palm Beach morons who couldn't manage to puncture a pre-scored index card. Sorry, for saying, "moron". I'm no better than the trolls. I blame moose and squirrel.
Network latency is a double-edged sword. Sure, relatively high latencies (say, >80ms) can spoil the VDI experience with jittery screens and jerky mice. But even lower latencies (<20ms) can wreck transaction heavy, fat applications and drive them into the data center, so they live closer to their servers.
In standing up our own cloud service, our biggest revelation was the cost of VDI, both in licensing and hardware. MS license terms are confusing (intentionally, in my opinion) and lead to over-provisioning. And those fat apps–in aggregate–had a thirst for SSD storage that shamed our servers.
I'm not a coder, but I read a lot of code to gain insight into problems I'm tasked with fixing. I've learned to identify developers by their peculiar spelling and grammar quirks. For example, "thier" in a comment line indicates Andy wrote that particular routine, while "there" when he means "they're" points to Bob. And, if the code contains proper grammar and missing joins in an SQL query, of course it's Carl!
Bless their hearts. I love them all.
The biggest fiction is that Russian meddling in US politics and media is something new. Russians (then Soviets) routinely planted false stories in third-world press and patiently waited for them to be picked up by the AP, UPI, AFP, Reuters, etc. for an appearance of legitimacy. With RT they simply cut out the middle man. Google and other aggregators then give RT equal play with western news outlets, more even, because sensational stories get more clicks.
Comparing apples and oranges is not futile. It's quite easy. Whilst both are delicious, sweet, round and grow on trees, they taste quite different. Apples can be baked in pies, but oranges cannot. Apples come in a variety of colors, but oranges are almost uniformly the same color (a kind of reddish-yellow).
This article safely reinforces the worst prejudice of storage admins, which is the belief they can do their job and remain ignorant of the applications that run on their systems.
I'm a DBA (Sybase, Intersystems Cache) and a storage admin (ZFS, NetApp) for a cloud company. As a vertical market software vendor, I also deal with our premises customers' myriad other storage systems (EMC, Compellent, Hitachi, etc.). I've seen a lot of good and a lot of bad. The storage system, more than any other component, determines application performance.
There can be a real need for multiple LUNs in a database, even though they ultimately sit astride the same physical disks. Separating data from log I/O in RDBMs is axiomatic. The OS kernel may effectively serialize I/O to a single LUN whereas multiple LUNs have multiple software channels. In other words, you are clearing a software not hardware bottleneck. There could be other considerations in regards cache policies, tiering, etc. that justify multiple LUNs.
The Brits tried to pull a fast one and turn Jerusalem over to the Arabs before they were scheduled to bug out. Didn't work too well. There was considerable animosity between Israelis and Brits at the time. The only reason the latter did anything to benefit the former was Truman twisting their arm.
In high school I discovered I could get two TRS-80s to talk together by cross-connecting their cassette tape drive cables. The first machine thought it was writing a string to tape, but it was really read by the second machine, which thought it was reading a string from tape. I cooked up a BASIC version of Battleship to demo the concept.
There's also fault tolerance (FT) which is a very high level of redundancy, such that software is unaware of any failure. I'm thinking especially of Tandem. And then there's business continuity (BC) which is like DR but focuses less on the disastrous aspects. I'm thinking near line storage or data replication. The lines can blur but you really need prudent amounts of both. You don't want to fail over to the bunker just because one disk goes bad. And your RAID6 array doesn't help when it's under water.
When the data you're protecting is all in an object or relational database, the DBMS usually offers another form of replication. Database replication basically consists of replaying the primary's transaction logs on a secondary system. This is an attractive option because replaying transactions instead of physical device I/O prevents many types of corruption and maintains transactional integrity. The secondary system can be used for report generation as well or other read-only uses.
As a vendor SE, I had the misfortune of attending a meeting of LA Times execs after they all received their Newtons. The meeting was constantly interrupted by, "hold on!...(scribble, scribble)...okay, go ahead...hold on...(scribble, scribble)...". My comment about witnessing the human equivalent to XON/XOFF flow control was not appreciated.
Those in the room with Tandy Model 100s had no problem keeping up. Ah, the Model 100, stalwart of newsrooms everywere, that's a computer you should memorialize.
Tombstone, to represent beloved gear of day gone by.
The Register - Independent news and views for the tech community. Part of Situation Publishing
Join our daily or weekly newsletters, subscribe to a specific section or set News alerts
Subscribe
