Tech media speculates on Microsoft acquiring AMD and Docker. And here's why drones and people don't always mix.
The post Microsoft Acquisition Rumors & Drones Vs. People appeared first on Packet Pushers Podcast and was written by Drew Conry-Murray.
INE’s CCIE Service Provider v4 Advanced Technologies Class continues today at 08:00 PDT (15:00 UTC) with Inter-AS MPLS L3VPN. All Access Pass subscribers can attend at http://live.INE.com. Recordings of some of the previous class sessions up to this point are now available via AAP library here.
Additionally, INE’s CCIE SPv4 Workbook is now available in beta format here.
Hope to see you in class!
CloudFlare's DNS server, RRDNS, is written in Go and the DNS team used to generate a file called version.go in our Makefile. version.go looked something like this:
// THIS FILE IS AUTOGENERATED BY THE MAKEFILE. DO NOT EDIT.
// +build make
package version
var (
Version = "2015.6.2-6-gfd7e2d1-dev"
BuildTime = "2015-06-16-0431 UTC"
)
and was used to embed version information in RRDNS. It was built inside the Makefile using sed and git describe from a template file. It worked, but was pretty ugly.
Today we noticed that another Go team at CloudFlare, the Data team, had a much smarter way to bake version numbers into binaries using the -X linker option.
The -X Go linker option, which you can set with -ldflags, sets the value of a string variable in the Go program being linked. You use it like this: -X main.version 1.0.0.
A simple example: let's say you have this source file saved as hello.go.
package main
import "fmt"
var who = "World"
func main() {
fmt.Printf("Hello, %s.n", who)
}
Then you can use go run (or other build commands like go build or go install Continue reading
Is it just me, or did we used to call this a mainframe?
The post Rule 11 Redux appeared first on 'net work.
Imagine you’ve just woken up and found yourself in a small kingdom someplace in Europe around 1200 AD. You wander outside, interested in your surroundings, and find yourself in the middle of a fair. Taking stock, you see a man standing in a tent across the way who appears to be tapping on something with a small hammer. Working your way to the tent, you find he is actually tapping out intricate patterns on a small silver disc. While you’re not certain what the disc is for, you take a moment to ask — as any geek would — “are you in the information technology business?”
The tinker, living in 1200 AD, probably doesn’t even understand the question. “What’s information technology?,” he might ask. But let’s consider the tinker’s business. What does a tinker really do?
He takes some material, combines it with technical knowhow, including the development and use of tools, to create a product he knows customers will want. He can’t just use any old tool, or any old technique — he must know something about the correct technology to apply to the problem at hand. And he can’t just hammer anything out on the little Continue reading
DockerCon, Cisco Live, and ONS dominated June's coverage -- as did P4.
Gabi Gerber (the wonderful mastermind behind the Data Center Day event) is helping me bring my Designing Infrastructure for Private Clouds workshop (one of the best Interop 2015 workshops) to Switzerland.
This is the only cloud design workshop I’m running in Europe in 2015. If you’d like to attend it, this is your only chance – register NOW.
Read more ...I had the pleasure of attending the CCIE Wireless tectorial at Cisco Live in San Diego this year. One of the topics discussed was the new diagnostic section of the lab. Jerome Henry gave us insights into what the section would look like as well as some examples of the types of things that we can expect in the section. I wanted to pass on some of that information along with a few insights about how you should prepare for this section since it’s quite different than what we’ve seen before in the lab.
What is the Diagnostic section?
Starting in v3 of the wireless lab, each lab will begin with a 1-hour diagnostic section. This section has no configuration task associated with it. Instead, you will be playing the role of TAC, or a senior level engineer. Your job is to look at information gathered from a client by a first-level engineer and analyze it so that you can answer questions related to troubleshooting an issue.
It sounds like you can expect maybe 3-4 separate troubleshooting scenarios with approximately 10 questions to answer across those 3-4 scenarios. So that means there will probably be 2-4 questions per scenario. All Continue reading