Tagged With wos1
Having already spoken at several locations around the country during his Australian tour, Sir Tim Berners-Lee gave the final keynote at Linux.conf.au this morning. What are his thoughts on open platforms, operating systems choice, HTML5 DRM and the <blink> tag?
A footnote to our earlier discussion on why IPv6 hasn't been widely adopted: the numbering of the newer version is clearly designed to suggest that it's an improved successor to IPv4. But is that name actually logical and helpful?
Earlier this week I wrote about open source pragmatism and how even at an event like Linux.conf.au, there's less evidence of one-sided tech zealotry than you might expect. Now I'm wondering: how does that actually play out in the workplaces of Lifehacker readers?
We've known for decades that the available pool of IPv4 address was eventually going to dry up, but despite numerous warnings usage of its successor IPv6 is still minimal. Why haven't we migrated yet? Geoff Huston, chief scientist for regional internet registry APNIC, suggests that the answer is that carriers are too cheap to make the switch and are happy to rely on network address translation (NAT) systems instead.
Last year's court decision that ruled Optus' TV Now catchup service effectively illegal clearly dealt a blow to any plans to develop similar cloud-based TV recording services. But did it also cast a broader shadow over the prospects for other cloud-based developers?
If you are already running servers in a virtualised environment, then shifting into a cloud environment might seem like a relatively trivial step. However, there are some simple principles worth remembering to ensure the process happens with minimal hassle and that you can justify the costs involved.
IP is now the de facto standard for any kind of networking — so much so that many sites blindly implement it without any understanding of what went before. However, even if your business is running happily on IPv4 and you have a migration plan for IPv6 in place, understanding the history of how we arrived at using those standards can help you manage your own network better.
Simple Network Management Protocol (SNMP) is one of those standards that is implemented almost everywhere but ignored by almost everybody. While there are more sophisticated methods available for monitoring and managing network performance, SNMP survives partly because it remains the main option supported in many pieces of specialised networking hardware.
If you want to train large groups of students on how to use and deploy networking equipment, you'll need to rapidly redeploy fresh system images as each new class comes in. That sounds like an obvious case for using virtualisation, but there are some traps to be aware of before pumping out those virtual machine images.