knorrie

You need the non-ADHD people to fly the the regular boring things from A to B, and you need the ADHD people to be able to take the right decisions about what to do in a split second while being under extreme duress in a war zone.

Hi justasidenote2, I'm at 60% scrolling down this whole hacker news crap thing, and I finally found a post that I think makes any sense at all.

First of all, make sure you get that diagnosis. Don't go wild with the medication thing, because the first thing that the medication should do is bring you from the "giving up in advance" level to the "ooh, I can learn about and try some things that might help me to take control of my own life" level.

And for now, start ignoring "anyone who doesn't have our experience" and what they think and shout, because I think you won't start to feel any better after reading all of that.

Hans

P.S. my un-scientific explanation for the overload of stress reactions (and anxiety and panic attacks) is that in absence of 'neurotypical' ways to get us going, the body goes into an emergency stress loop, producing stress hormones and adrenaline all the time, to try get us going to do anything at all.

This website is an initiative of Rop Gonggrijp, one of the founders of the Dutch ISP XS4ALL.

I suspect that the way the information is structured and the writing style that is used is a useful match for what people in our community need.

Thanks for the article. Your writing style is fun and easy to read. Learning more about tracepoints and bpf is also on my TODO list, and I'll certainly re-read this later.

The 4.15.0-33 output from uname -r does not mean that your kernel version is 4.15.0, it's probably based on a later 4.15. The ubuntu package version is 4.15.0-33.36. I'm not sure what the 36 means here. There are no upstream 4.15 releases any more, the last was 4.15.18, in April 2018.

I know how it works in Debian, which is similar. E.g.:

-$ uname -a Linux mekker 4.17.0-3-amd64 #1 SMP Debian 4.17.17-1 (2018-08-18) x86_64 GNU/Linux

uname -r says 4.17.0-3, but that's the package name (linux-image-4.17.0-3-amd64). The actual version is 4.17.17-1, which means it's 4.17.17 with Debian patches.

The number 3 is the an ABI compatibility number. So, as long as the kernel ABI keeps the same, newer versions (e.g. 4.17.18) can use the same package name (4.17.0-3). However, if the ABI changes, the -3 is bumped to -4, it causes a new package in the repository and when installing it, the user has to recompile self-made modules.

The only reason for the .0 in the package version name is because there might be something expecting three numbers in that place (like it was with 2.6.x kernels).

https://www.debian.org/doc//manuals/debian-kernel-handbook/c...

Well done, very well written!

Be aware that the approach this book takes has its own type of target audience. I guess the audience that will like this book/tutorial are the kind of people that will usually just read the entire reference manual of anything to see what's in their toolbox before actually starting to build something. So by reading it, you help them as a guide to work through it, choosing the parts of the language that are best learned first. After following the exercises, the reader can already build some programs using those concepts, whatever it might be, leaving it to their own imagination.

The other type of audience, which this book might be less suited for, is people who get bored after chapter 1, thinking "I want to build something fun now already!". Those might be better served by a tutorial like "we're building a XYZ game", explaining concepts along the way.

Both are good, both are needed.

I'm one of the first type of people, so I'm really happy to see this kind of book. The second type of tutorials only give me fragments of information if I follow it building that XYZ game, while I have my own idea of what to build, and just want to learn how those lists and dictionaries work when I discover I need them. ;-]

I stopped using office chairs years ago. Instead I have a Togu Powerball ABS (both in the office and at home).

I helped me to get rid of neck and lower back pain, because I had to start building strength in muscles that you need to sit properly.

I wrote a routing protocols tutorial a while ago, that tries not to be overly complex and not "dry".

https://github.com/knorrie/network-examples/blob/master/READ...

It uses the bird routing daemon on linux to build some networks on the go and see OSPF and BGP happening.

Maybe it can help you a bit. :-)

An instance might want to reach anything on the internet that's using an IPv6 address is a use case.

Also, having instances connect to IPv6 parts of the internet while you can see which subnet of your vpc the traffic originates from, and maybe filter on that fact.

Having routable addresses is a different thing than them being public or private, which is determined by the fact if you accept traffic to them or not when it arrives at the last hop before entering your vpc.

The opposite direction is more interesting.

It might be finally possible to reach things floating out there on the internet which have an IPv6 address.

Shaming an ISP is one thing. Like pommi said, the end user might not be very interested in the fact that its connection to a web site is using IPv4 or IPv6. The end user just wants to see the content instead of an error.

The maintainer of the web site that the end user is visiting must make sure his website is reachable over either IPv4 and IPv6, so the content can be viewed by users who have an IPv4 only connection, a dual stack connection, or even an IPv6 only connection.

Doing so just requires to enable IPv4 and IPv6 on the entry point (loadbalancer / front facing web server) of the place where the web site is hosted.

What I'd like to get shamed, is the poor adoption of IPv6 in all major "cloud" systems. Where's the IPv6 address on the VM I can start at amazon[1], where's proper IPv6 support in OpenStack [2], CloudStack [3], CloudFoundry [4] etc. etc...

[1] http://blog.iphoting.com/blog/2012/06/02/ipv6-on-amazon-aws-... [2] https://wiki.openstack.org/wiki/Neutron/IPv6 [3] http://docs.cloudstack.apache.org/en/latest/networking/ipv6.... [4] cannot even find a sensible page to quote here when I google it

IPv6 is not only about the fact that you can put some address on an external facing loadbalancer. The applications I want to run on my IaaS, PaaS or WhateverAas are also clients who connect to the internet, just like a web browser.