mdlowman

It depends on what you're using for the resolver. I'm assuming you only care about gethostbyname(3) and friends. With glibc that means nss; generally you're also looking at libnss_dns.so, which uses glibc's resolv (copied from BIND). This doesn't include enough configuration to do what you suggest; it pretty much just points everything towards a server.

So you have two options: use a different NSS module (maybe write your own?) or have a proxy DNS resolver that sends different requests to different places.

systemd-resolved actually handles the first option pretty well (although it would prefer that you use the dbus interface over gai). It can handle multiple interfaces with separate domains and split DNS fairly well! (Not so good with reverse DNS, unfortunately. But I get it, reverse DNS is pretty hacky anyways.)

If you prefer the forwarder route, dnsmasq seems to be fairly popular these days in the embedded world and elsewhere.

If I were you, I think I'd write a short NSS module or use dnsmasq, depending upon your needs.

The better analogy in this case would be to an AmazonBasics USB cable, not to a phone charger.

Are there issues when anyone can provide a product? Yes. But this would certainly not involve Amazon opening the storefront to allow selling any sort of drugs, but rather them sourcing generic product themselves and selling it as private label.

I would have no problems trusting this product to be genuine, just as I have no problems trusting their other private label products. It's a different sort of issue.

I'm deeply saddened to hear that the Seattle Mystery Bookshop is closing. This feels like something easily missed in today's automation-based economy; the ability to go to an expert and get quality recommendations is not to be missed. Seattle Mystery Bookshop was only one of many excellent book stores in the Seattle area, but it seems that their number is diminishing by the day. I can only assume that that trend holds firm in other cities, and we are the poorer for it.

Quite excited by the "high-performance audio API". Could drive a different consumer segment.

This reminded me of In the Reign of Harad IV[1].

[1]: http://www.newyorker.com/magazine/2006/04/10/in-the-reign-of...

If you want to, you can just go visit an FC and get a tour, you know. It's not exactly closed.

http://www.amazon.com/b?node=8947548011

I usually skip the Rite of Spring, but love every other piece. Probably because I was trying to watch the visuals too hard instead of listening.

But the important thing to remember about Fantasia is that it's not a coherent story, it's a set of shorts.

You can watch subsets, skip some, or really do what you want. Just watch Night on Bald Mountain/Ave Maria, or the Dance of the Hours, or whatever you want. And give Fantasia 2000 a shot. Not as good, but still fun. Firebird was great.

There's no problem with that. Assume the key material isn't compromised, since you have to assume that.

You imply that Apple is going to keep using the cert until 2035. I can assure you they won't.

The company I work for is in the process of migrating off of SHA-1 certs, and the amount of due diligince that has to go into this sort of an upgrade is incredible.

It involves analyzing full logs of all supported client enctypes and tracking down the full set of "flavors" of clients that only do SHA-1.

At the end of the day, you're going to break people, and it's all about minimizing how many people that is. Imagine the situation with hardware devices in the field from ten or so years ago. You can't update them and their software rev only supports SHA-1. What do you do?

(You break them.)

If I were trying to drive adoption of a connector that has objectively better performance characteristics (high current draw for fast charging), I too wouldn't provide a legacy cable that doesn't exhibit those benefits.

I know the criteria for selecting my next laptop and monitor will involve USBC.

Reading the reviews, it looks like there's basically one complaint.

Ports/devices with older connectors (USBA, mini-B, micro-B, B) aren't necessarily going to be able to (or supposed to be able to) handle a 3A current draw.

A device that supports USBC should handle current draws this high. But to do so, it must be able to determine if it is safe to draw this much current. That's only doable with a USBC->USBC connection as per spec. So a USBC-USBA cable (or any other USBC->something cable) should use a resistor identifying that the USB3 current draw spec should not be exceeded.

The cables he's reviewing misidentify as being capable of the full current load. This could cause damage to the device your USBC phone or laptop is being plugged into.

Eltana.

You can also move to Seattle, which has classic hand-rolled, boiled, delicious bagels at one local store.

I can confirm that they taste _much_ better. And are more expensive.

You're right, but where I work almost anything can cause a bug that affects users. Pre-review eliminates some of those bugs.

I would not move to this workflow, although it's interesting to hear from somewhere that it works.

DLL hell certainly used to be a big issue in Windows. But I disagree that it remains a major factor; Windows apps are increasingly bundled and Windows system functions that used to be the cause of these issues, like DirectX, are packaged as redistributables that allow side-by-side installs.

I would suspect the point is rather that you have a bunch of megabyte range files, and you rarely update them and don't have to sync. But for most workflows this feature seems targeted at, the free tier seems insufficient.