One way to make containers network: BGP

Linux containers are really cool these days. I hear people talking about Docker and Kubernetes and Rocket and all these things all the time. And if you have containers, you have to network them together!
A lot of computer topics are explained in an unnecessarily confusing way, but I think networking can be especially hard for developers to read about — I’m reading a page right now that talks about virtual networking layers, overlay networks, payload encapsulation, BGP, control planes, packet fragmentation, TAP, veth, Neutron, data center fabric, anycast, vRouters, tunneling, VRF tables, VXLANs… ugh.
A lot of this stuff is not that hard though! I know that packets have IP addresses and ports on them and it turns out that takes you a pretty long way. So let’s talk about a way that containers could talk to each other.
I’m not going to talk too much about what a container is in

Original URL:

Original article

Drupal 8.x core release on Monday — PSA-2016-002

Advisory ID: DRUPAL-PSA-2016-002
Project: Drupal
Version: 8.x
Date: 2016-July-17
Security risk: TBD
Vulnerability: TBD

We will be doing a Drupal 8 core patch release on Monday, July 18th. This will occur between 14:15 UTC and 19:00 UTC.

There will not be a Drupal 7 release during this window.
Why is this release being issued?

The Drupal security team has learned that a third-party Drupal 8 dependency will be making a security release on Monday, July 18th and in accordance we will be making a Drupal 8 release soon after. We will not disclose details of the third-party update in advance of that release and cannot respond to requests for further information. This security release is for the dependency only and does not affect Drupal 7 sites. Other mitigating factors will be included with our published SA.
What about the regularly scheduled release window on Wednesday, July 20?

We are moving the regularly scheduled window two days earlier to provide

Original URL:

Original article

How (And Why) FreeDOS Keeps DOS Alive

FreeDOS was originally created in response to Microsoft’s announcement that after Windows 95, DOS would no longer be developed as a standalone operating system, according to a new interview about how (and why) Jim Hall keeps FreeDOS alive. For its newest version, Hall originally imagined “what ‘DOS’ would be like in 2015 or 2016 if Microsoft hadn’t stopped working on MS-DOS in favor of Windows” — before he decided there’s just no such thing as “modern DOS”. An anonymous Slashdot reader writes:

No major changes are planned in the next version. “The next version of FreeDOS won’t be multitasking, it won’t be 32-bit, it won’t run on ARM,” Hall said. “FreeDOS is still intended for Intel and Intel-compatible computers. You should still be able to run FreeDOS on your old 486 or old Pentium PC to play classic DOS games, run legacy business programs, and support embedded development.”

By day, Hall is

Original URL:

Original article

Kubernetes the Hard Way

This tutorial will walk you through setting up Kubernetes the hard way. This guide is not for people looking for a fully automated command to bring up a Kubernetes cluster. If that’s you then check out Google Container Engine, or the Getting Started Guides.

This tutorial is optimized for learning, which means taking the long route to help people understand each task required to bootstrap a Kubernetes cluster.

Target Audience

The target audience for this tutorial is someone planning to support a production Kubernetes cluster and wants to understand how everything fits together. After completing this tutorial I encourage you to automate away the manual steps presented in this guide.

Cluster Details

Kubernetes 1.3.0
Docker 1.11.2
CNI Based Networking
Secure communication between all components (etcd, control plane, workers)
Default Service Account and Secrets
What’s Missing

The resulting cluster will be missing the following items:


The following labs assume you have a working Google Cloud Platform account and

Original URL:

Original article

#ethereum fork: Mist browser now available with hardfork choice

This release contains geth 1.4.10 with the Hard Fork choice!

You will be asked at start which chain you want to be on. After selecting your choice, you will run either the Hard Fork chain, or stay on the old one.

Until block 1 920 000 you can simply switch to the other chain, by selecting the main in Menu “Develop” -> “The DAO fork” -> “support/don’t support DAO fork”.

If you want to switch chains after block 1920000 you need to resync Mist!You can do this by following these instructions:

Click on “Accounts” -> “Backup” -> “Accounts”. This will open the file explorer with the “Ethereum” folder opened.
Click on “Accounts” -> “Backup” -> “Application Data”. This will open a system folder, go there into the “Mist” folder.
Close Mist.
Delete the “chaindata” folder inside the “Ethereum” folder.
Change the content of the file called “daoFork” to true or false (“true” means going with the dao fork,

Original URL:

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: