devonnulled

Already been done. Meet KiTTY:

http://www.9bis.net/kitty/?page=Welcome&zone=en

Hey there. I gave a talk at PGConfNYC '14 earlier this year about our solution to HA using open source solutions. The animations and stuff don't really work too well on Slideshare, but it should point you in the right direction:

http://www.slideshare.net/TeamARIN/building-a-high-availabil...

pgSQL doesn't have anything built in for fencing, failing-over, etc. by default, but by using stuff like Pacemaker, you can get the job done with a little elbow grease.

Ah, that's a use case I didn't even think of. Makes sense in that situation then. I rarely deal with things that require USB license dongles, but I can see that as being a pain this may alleviate.

Since this needs to be enabled in the kernel at compile time, it really depends on what your favorite distribution chooses to include.

If it does end up being in the Big Two (Debian-flavored, RH-flavored) it really doesn't make sense for servers. If it was enabled by default this seems like something that you would need to do some sort of 'handshake' between to prevent someone from just mounting a USB device willy-nilly as they see fit. Complete speculation on my part though.

Thunderbolt hotplug is supposed to be handled by the firmware. But Apple decided to implement thunderbolt at the operating system level. The firmare only initializes thunderbolt devices that are present at boot time. This driver enables hotplug of thunderbolt of non-chained thunderbolt devices on Apple systems with a cactus ridge controller. This first patch adds the Kconfig file as well the parts of the driver which talk directly to the hardware (that is pci device setup, interrupt handling and RX/TX ring management).

Finally. Been waiting a while for this. The fact that Apple designed the hotplugging at the OS-level infuriated me for the longest time.

Disclaimer: I've never used Lyft and the following is purely hearsay:

In the area I live in (where we've got Uber(x), Hailo, and Lyft) there was word that cars that had the pink mustache were being targeted by taxi drivers for harassment, so I think they pulled them off for safety.

Good luck finding a simple package. We met failover and cross-site replication requirements by using Pacemaker controlling pgsql.

So back in the day, IANA was the sole controlling body for IP address allocations. When the internet began to grow, they redelegated certain blocks (with the largest being /8 in CIDR notation) to organizations in geographical communities. This is called the RIR (Regional Internet Registry) system. In order to get IP addresses from a certain RIR, you have to be a business or customer within that region. The region of North America and some of Latin America is under the American Registry for Internet Numbers, also known as ARIN.

Please see this page for more information. https://en.wikipedia.org/wiki/Regional_Internet_registry

What about using alternative frameworks for HTTP servers for Python? Pointing at only Bottle and going "hey! Python is slower!" is like pointing at WeBRICK and going "Hey! Ruby is slower!" when you haven't even touched Passenger or Unicorn.

What about:

* Flask? http://flask.pocoo.org/

* Tornado? http://www.tornadoweb.org/en/stable/

* Django? https://www.djangoproject.com/

* CherryPy? http://www.cherrypy.org/

What about using PyPy ( http://pypy.org/ ), Jython ( http://www.jython.org/ ) or even IronPython ( http://ironpython.net/ ) instead of plain CPython?

As someone who used to work in the web hosting industry, this article completely ignores the technical side of things of handling _THAT_ much attention.

I've seen startups be hosted on shared hosting plans, get a boat load of traffic, the site gets suspended, and they are dumbfounded as to why it happened!

If you spend the amount of money to launch a start up, get a beefy server, load balance it with at least Varnish, and do some load testing before going on mainstream media. Nothing is more embarrassing as when your site tanks after being advertised on National television.

The SSL errors could freak a few people out who don't know what's going on:

  status.newrelic.com uses an invalid security certificate.

  The certificate is only valid for the following names:
    *.statuspage.io , statuspage.io

Hey there. I work at ARIN. An explanation of why IPv4 won't scale any further: (Please note that any opinions expressed here are my own and not of my employer)

Of course, we have a currently limited amount of IP addresses that can be given out. When IANA/RIRs were formed, IANA gave allocations of /8's (the largest groups of IPv4 addresses) out to all of the RIRs, who then assigned them to organizations within their respective areas. (For example, APNIC - Asia Pacific, AFRINIC - Africa, ARIN - North America) The problem now is that we are simply running out of addresses with the current number of internet connected devices.

Now, we resolve this within our own homes by using routers that support NAT (Network Address Translation) which is fine for our own local sites. However, a large amount of ISPs want to enable something called CGN (Carrier-grade NAT) which will take what happens on your own local router and blanket it over their entire network. This is where a large group of customers (including you) would have one single (or a handful) of IPv4 addresses that represent you on the public internet, but each site/home/office would have its own internal IP address to that ISP's network. Most cell phone providers actually already do this (although I'm not sure if we can call it CGN) where your phone has a Class C IP address assigned to it when you connect to the network, but all traffic goes through a single IP address.

Now there are problems to this:

1. It is hard to track who is doing what. If a customer of an ISP performs some sort of illegal action (bomb threats, hacking, etc use your imagination here. ;) ) It is hard to track down who is exactly doing what without your ISP simply logging all requests that you make. Instead in the current form, your ISP can be simply asked "Hey, who had this IPv4 address at this time?" instead of "Hey, what sites was this person looking at?"

2. Let's say that you were a member of some sort of forum or new site (take HN or reddit for example) and someone sharing your IPv4 address did something that caused that IP address to be banned. Now, you cannot access the site. This allows your access to the internet to be dependent upon whoever else is using that same address. Of course, this can (and has happened) already by sites blocking entire subnets (a lot of IRC networks do this for overseas networks that usually harbor abuse.)

3. It simply becomes confusing security-wise. Take into consideration that you had a VPS or server with a provider like Digital Ocean or Linode. You set up a firewall on that server to allow only your IP address in. Now, you've allowed everyone else sharing that same IP address to access your server if they knew the credentials.

With IPv6, we have more addresses than there are grains of sand on Earth (as the saying goes.) We also said that we'd never run out of IP addresses with IPv4, but the growth of the Internet was seriously underestimated!

Some ISPs will run dual-stack (I believe Comcast does now) where all users now have IPv4 and IPv6 addresses!

This is actually my first public 'project' I've submitted in quite some time. It's nothing big, but I'm posting it in here in hopes that someone interested in making the jump to zsh and vim will find it useful.