Re: That does seem kind of shady...
"... the Dash buttons that I need are for Coffee beans, Printer ink and Talisker Whisky!"
Sounds like a cocktail for bitter journalists.
78 posts • joined 11 Dec 2007
"GNU Emacs began life in the 1970s and is currently at version 25, which means it averages two releases to Vim's one, but still definitely on the slow side."
Actually, GNU Emacs is technically still at version 1 -- the 25 is the minor version number. It is said that RMS will release version 2 when the first stable version of GNU Hurd comes out.
"The main limitation of NAT is 16 bit ports. If port addresses were expanded to 32 bits, we'd probably be fine with IPv4 pretty much forever."
For larger networks you can set up source NAT pools, so that connections are spread over a number of IP addresses instead of a single NAT address (e.g., the NAT router), thus avoiding the 16-bit port number limit. Cisco has supported this since when NAT became a thing.
"Most Spaniards I'm guesing they will pronounce WhatsApp either "WASAP" or "WARSAP""
I can tell you that when speaking Spanish anything that introduces pauses into the syllable timing will get summarily dropped. Hence, "wasap" instead of "watsap". Spanish makes little use of syllable final consonants outside of "m", "n" and "s", and even then has a preference for ending syllables with vowels -- e.g., notice the aspirated final "r"s and "s"s in Caribbean Spanish.
Third-party software vendors have something to do with it, I'm afraid. Where I work we have a big "enterprise application suite" -- ERP stuff. It's a big nasty hodgepodge of PL/SQL, Pro*C, Pro*COBOL, Java, Forms, and other things that should be declared Not Safe For Work, very tightly integrated with the database and associated Oracle stack products. Unsurprisingly, the vendor certifies it compatible only with Oracle, and will not support its use with anything else -- I think they might even consider the use of another database product a violation of the contract or some other equally ludicrous claim. Fortunately, I'm not a DBA, nor do I want to be one.
Cray did something like that at least twice already. The XD1 uses ASICs to extend HyperTransport into a switched fabric to link 144 processors together into a single system image. The XT3 and successors connect the CPUs to the SeaStar interconnect via HyperTransport.
The processors can connect to each other without any glue logic but that consumes HT links quickly. One can only add so much to the die and packaging before it gets too expensive.
At last Google is at least acknowledging the search spam problem. Now, will they do something about the keyword search spam sites and the shopping spam sites that I keep getting in my search results? Take care of that, Google, and you'll have gotten rid of most of the spam results that I've faced.
So the requirements say that a method to asymmetrically authenticate a message is needed. There are several digital signature algorithms available, many within reach of a Google search. What do we do? We'll ignore decades of crypto research and invent our own signing algorithm, of course.
Thing is, the odds of encountering a South African anywhere between the Rockies and the Appalachians are so low that most people won't be able to tell a real SA accent from a fake one. Those same people wouldn't be able to distinguish between English, Scottish, Welsh, Irish, or Australian accents either, for that matter.
Real SCSI, as the Lord intended it to be, uses the target (i.e., the peripheral device) to drive the transaction. Apple's SCSI as implemented in the Mac Plus, on the other hand, uses the initiator (i.e., the controller) for that function. Granted, the SCSI standard was still in development, but IIRC the roles of initiator and target were well understood back then.
"What small or medium company is going to set up a greenfield Fibre Channel SAN these days, when iSCSI is rampaging around?"
Given that it is cheaper and easier to buy a pair of Qlogic SANbox switches and set up zoning, than to buy a pair of decent wire-speed Ethernet switches and dick around with STP/QoS/trunking/VLANs/etc. to obtain equivalent performance, I'd say that any company that can crunch numbers without developing haemorrhoids would see the benefits of going the FC way.
I see this more as a competitor to LifeSize's Passport, which does only $720p and currently goes for $2k, but can do Skype video calls as well as H.323/SIP, is smaller, and doesn't require you to pay a pizzo. Either way, people aren't going to pay for HD video calls when free webcam video calls are "good enough," same as how MP3s, pirated DVDs, fast food, and Coors Light are "good enough."
-- "We might see an importation of the EVA software environment onto the 3PAR platform, giving it an EVA personality."
Given that the SOP for upgrading an EVA is to use Continuous Access to migrate LUNs, I'd hope that HP would only add the minimum amount of logic necessary to make a 3PAR system participate in CA, instead of porting that pile of cobwebs and dust that is XCS.
-- "But the 3PAR architecture can be, and probably will be, pushed up-scale and down-scale, overlapping the mid-range EVA's capabilities more and more."
What would that make of the Dot Hill-sourced MSAs then? Those always looked like a temporary solution while HP could find something else that they could maintain in-house.
Biting the hand that feeds IT © 1998–2019