dice

Hell, CentOS 5 is still pretty widely deployed (and supported by RH until 2017).

>So you don't tell your current salary or requirement or any number, fly to the interview and get an offer that is half of what you are making.

He said to go ahead and ask what their budget is, or to say what your requirement is:

>When asked this question I would suggest you ask the recruiter for his budget in return, or to simply state your salary requirement (rather than your current salary) instead.

If you've drunk the pets-vs-cattle koolaid to the point where your instances are all (or mostly) ephermal then you're probably also using auto-scaling groups and don't care if a particular single instance falls over.

I don't know about "brutally quick". Anyone who's driven an M3, S4, or any similar performance sedan isn't going to be blown away by the speed of the Model S. It's fast, but it isn't mind-blowing.

In the final solution at the end of the article there are only two pipes:

1. A pipe to feed the file names into xargs for starting up parallel `mawk` processes.

2. A pipe to a final `mawk` process which aggregates the data from the parallel processes.

There's still some performance that could be gained by using a single processes with threads and shared memory, but this is pretty good for something that can be whipped together quickly.

Keep reading, he removes the cat and grep in the final solution.

I didn't say it's a non-problem. I said it's not a problem with all Nexus 4 devices.

If there is one device which is not impacted then it is not a problem with all devices. The problem is therefore isolated to a subset of all devices. Perhaps that subset is the majority of all N4s, perhaps it is a small fraction. We don't have enough data to say one way or another.

My wife has an N4 running 5.0.1 with no issues re calling, so if there is an issue for these users it's an isolated one and not a systemic problem with all N4s.

Most of the Android phones on the page you linked are not Google phones. Whether or not they get updated is up to the manufacturers and carriers, not Google. You'll note that the Nexus phones have more update support in general.

Whether providing major updates to a phone is a good thing is debatable. My wife hated getting the 5.0 update. She saw it as a major inconvience that changed how her phone worked for no good reason. She would prefer to have the phone work the same way for the entire time she owns it.

PS: 'Sup, fury?

That intro was responsible for introducing me to Orbital as well: http://en.wikipedia.org/wiki/Orbital_(band)

Google's tool is new to me as well, but it doesn't seem to be very good for comparing card rewards programs. I like the nerdwallet site for that: http://www.nerdwallet.com/

Triangle is back, circle is home, square is list/switch apps. They're in the same places and have the same functionality as Android 4.x.

No Nexus 6?

The AWS status page not showing anything isn't unusual. They'll probably update in half an hour to describe it as a partial failure then revise it to an "all OK" 10 minutes before it's actually fixed then retroactively downgrade it to a minor quality of service disruption.

Not that I've noticed they tend to lie through their teeth on the status page or anything....

It's flapping in some locations. Seems to be hard down in others. From a service monitoring Cloudfront on various geographically distributed Nagios monitors (times are PST):

  Columbus:

  [11-26-2014 16:46:24] SERVICE ALERT: public-www;CDN - Logo;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 2960 bytes in 0.165 second response time
  [11-26-2014 16:45:34] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;SOFT;1;Name or service not known
  [11-26-2014 16:39:24] SERVICE ALERT: public-www;CDN - Logo;OK;SOFT;3;HTTP OK: HTTP/1.1 200 OK - 2960 bytes in 0.030 second response time
  [11-26-2014 16:38:34] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;SOFT;2;Name or service not known
  [11-26-2014 16:37:34] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;SOFT;1;Name or service not known
  [11-26-2014 16:25:24] SERVICE ALERT: public-www;CDN - Logo;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 2960 bytes in 0.030 second response time
  [11-26-2014 16:24:34] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;SOFT;1;Name or service not known
  [11-26-2014 16:21:24] SERVICE ALERT: public-www;CDN - Logo;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 2960 bytes in 0.066 second response time
  [11-26-2014 16:20:24] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;SOFT;1;Name or service not known

  Portland:

  [11-26-2014 16:49:40] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;SOFT;1;Name or service not known
  [11-26-2014 16:43:40] SERVICE ALERT: public-www;CDN - Logo;OK;SOFT;2;HTTP OK: HTTP/1.1 200 OK - 2960 bytes in 0.148 second response time
  [11-26-2014 16:42:40] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;SOFT;1;Name or service not known
  [11-26-2014 16:39:40] SERVICE ALERT: public-www;CDN - Logo;OK;HARD;3;HTTP OK: HTTP/1.1 200 OK - 2960 bytes in 0.186 second response time
  [11-26-2014 16:21:40] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;HARD;3;Name or service not known
  [11-26-2014 16:20:40] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;SOFT;2;Name or service not known
  [11-26-2014 16:19:41] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;SOFT;1;Name or service not known

  Santa Clara:

  [11-26-2014 16:24:26] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;HARD;3;Name or service not known
  [11-26-2014 16:23:25] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;SOFT;2;Name or service not known
  [11-26-2014 16:22:25] SERVICE ALERT: public-www;CDN - Logo;CRITICAL;SOFT;1;Name or service not known

It seems like the current methodology is, to use wine analogies, to compare grapes instead of harvests. Charles Shaw has a Cabernet, but it's a very different beast from Joseph Phelps', and they will both have variations from harvest to harvest.

Perhaps in the future we'll see the marijuana landscape settle down into a few widely recognized and harvested strains, with different growers touting their harvests and growing techniques over those of others.

Better yet, add an SSL check to your monitoring system: open a ticket when it's going to expire in 30 days.

Great. According to this I should be living in Bolinas, CA where the cheapest house currently for sale is $1,249,000. I'll get right on that.

Many ISPs hijack DNS NXDOMAIN results to serve ads to their customers.

https://en.wikipedia.org/wiki/DNS_hijacking#Manipulation_by_...

Their comparison sizes for instances versus physical machines is laughable. For a 12 core physical machine with 64GB of RAM they list the r3.2xlarge instance size as unit-for-unit comparable (10 instances versus 10 machines I had configured).

Yeah... no. 8 vCPUs are nowhere near as fast as a pair of 6 core Xeons. My rule of thumb in AWS is that you get about half of what they say you do: so an 8 vCPU instance has about as much power as a 4 core physical server.

And don't even get me started on what they have for hardware costs. I think they must have pulled list price from Dell or something. I can get prices about 2/3 to 1/2 of what they're listing from my VAR.

I think it would be fine for a single fancy beginning-of-article letter. Whole titles or sentences is too much.

QEMU/KVM are the default virtualization used in OpenStack [1], for one. I also use it on my laptop to host guests because of how much Virtual Box sucks under Linux [2], as others have mentioned.

[1] https://www.openstack.org/

[2] https://lkml.org/lkml/2011/10/6/317

>Mind you I don't think I ever used "Stop A" on a Sun for anything constructive...

Back at the dot-com I worked at, we used to have a SPARCstation 5 that we used for SPARC-II arch builds. It was a nice machine, but it had a dead NVRAM battery so it would lose its configuration every time we lost power in the building (which was a lot, because rolling blackouts used to be a thing in California).

Anyway, an interesting quirk about the SPARCstation machines is that the MAC address for the NIC is stored in NVRAM, and when you lose the NVRAM settings it defaults to ff:ff:ff:ff:ff:ff AKA the broadcast address. So by default, on boot, this machine would start sending out DHCP requests and other network traffic with a source address of the broadcast address. The switches we were using did not like that, and would start flooding all of their ports with traffic. The only way we found to fix it was to reboot the switches.

So, there is at least one constructive use for "Stop A": you can use it to configure a MAC address on your SS5 so that it doesn't inadvertently bring down the whole network in a massive broadcast storm.

The size is 1876 bytes, DNS servers which support EDNS will do up to 4096 byte replies in UDP.

My brother did 1.2 GB of tethering in a couple hours on my T-Mobile phone while I was driving down I-75 from Detroit to the middle of Ohio. No coverage problems, no overage fees (I'm on the unlimited data plan), and we had a movie to watch by the time we got to the hotel.

>The AWS Console is perfectly usable for 99% of what you'll need to do. Most users won't need anything beyond it.

I believe the author was referring to navigating the filesystem and running commands via CLI (e.g. `cd` and `ls`, not `ec2-describe-instances`).

>Also note that Iron Maiden has never had a song on the radio

What do you mean by "never had a song on the radio"? They get played all the time on Local Radio Station's metal section.

Here's an example from two days ago: http://bonemetalzone.tumblr.com/post/70661430266/now-playing...

What do the numbers and colors of the hospital symbols mean? They do not seem to be correlated with price of procedure.

If the comments are outsourced then why have a backend at all? Just pop all of the posts into an S3 bucket and update the index when creating a new one. No server needed.

Yikes! Hopefully not on production systems. I've had fileservers which needed 60+GB of dentry cache to serve up files in a reasonable time, something like that could bring the site to a crawl for 10 minutes or more.