Remy started to crawl about a month ago, and every parent knows what happens when children start to crawl....they get into everything. Everything. So this meant changing up our existing entertainment area and optimizing for fewer emergency room visits. I'll admit, the old setup just had too much stuff on it in general, and especially too much stuff for him to get into. Here's what it looked like before:

So, out with the old and in with the new right? Sort of. The old TV was a 37" Westinghouse LCD that I bought over a decade ago. I tend to buy TV's the same way that I buy computers -- I get something better than decent and hold on to it for a while. A 37" LCD might not seem great today, but it wasn't too shabby in 2004. At least it did 1080p and had HDMI (baller!). The new TV panels are all super slim for fashion's sake (more on that later), and while they look really beautiful, they're seriously lacking in the audio department. The old speaker and amp setup (Parasound HCA-1200 mkII and KEF iQ3) also had to go. You can see that a child could easily knock over the stands and hurt themselves in the process. So goodbye amp and speakers, and time to get a soundbar.

I recently upgraded my Sony Z3 Compact to Android Marshmallow and noticed something really odd. When not on WiFi, I wasn't getting any push notifications or any updates. I'd come home or get to work and then my phone would light up and beep like mad. Later, I discovered that there was no network connection on the mobile network. I could make calls and receive texts, but the data connections just wouldn't work. Luckily, it's an easy problem to fix.

EDIT: It looks like RedHat pushed a new build that fixes the issue -> 
https://rhn.redhat.com/errata/RHBA-2015-1129.html

If all of your MYSQL SSL clients and replication just broke, I'm guessing that you're running RedHat, CentOS, or something derived from RedHat. In short, RH modified OpenSSL to reject Diffie Hellman (DH) keysizes less than 768 bits. Note that this is not the length of your private key. This is the DH key which is used in Perfect Forward Secrecy.

I recently had a project at work where the project's requirements forced me to think outside the box. They were:

• Spin up hundreds or thousands of VM's dynamically without much intervention from netops. These VM's would exist across many hypervisors and be provisioned dynamically.
• Allow inbound traffic to the guest VM's from networks outside the hypervisor.

The built-in VirtualBox networking options really wouldn't fit the bill. Here's why:

• Bridged networking would require a lot of prior planning and work from netops. Would all the hypervisors be in the right VLAN to get the various subnets required? Some of the hypervisors might reside in smaller existing networks that would be /22-/24. Nope, too much work to support that across all of our locations.
• Internal networks can only communicate with VM's residing on the same hypervisor. External access is a must.
• Host-only networks only allow the VM to communicate with the hypervisor and other VM's. Similar to internal but not the outside world.
• NAT networking would be a huge pain to map all of the inbound ports to VM ports. Reducing work was a goal here.

We're still going through our CentOS 7 kickstart/build process here at Weebly, and we're uncovering new twists every day. There are the obvious ones like systemd, random packages renamed, and things like that. Luckily, the process for enabling LDAP UNIX users and groups (and authentication) is the same process in CentOS 7 as it is CentOS 6. Looks like they're sticking with sssd. It had a few issues once included in CentOS 6, but it seems stable and reliable. That's about the most you can ask for in an authentication provider.

Here's a link to my post about enabling LDAP auth in CentOS 6. It should work in CentOS 7 -- at least it did for us.