At the January 2011 BozemanLUG meeting, David Eder showed us how to get an IPv6 address and then tunnel it through an existing static IPv4 address. During the meeting we discussed Jon Corbet's LWN summary of Geoff Huston's Keynote from linux.conf.au. The video of that talk has become available and is presented below in webm format. If you have any problems watching it in your browser, just right-click on the link below and "Save link target as..." to download. It should play in any newer video player that supports webm.
I subtitle this presentation, The Coming IPocalypse. :)
Right-click download link: LCA2011-Geoff_Huston.webm (54 min, 142 MB)
The Billings LUG is tonight! Thursday Jan 20th. Come on by, the address is 1123 North 11th street.
Tonight's discussion will be on SQL Basics
The OLPC Project announced the OLPC 1.75 based on an ARM CPU some time ago so it is good to finally see some of the fruits of their labor. Enjoy this video:
I noticed the creation of a new Fedora mailing list today when Rahul Sundaram sent out the first post on it... a mailing list for Fedora Remixers.
That made me wonder just how many Linux distributions there are that are Fedora-based. I did a quick search and found a Fedora wiki page that says, "There are roughly over a hundred distributions based on Fedora." Then it links to a distrowatch.com search page that shows 41 distributions that are "Fedora based".
I decided to take a brief look at those 41 distros to see how many were still active and if they were actually based on Fedora. I do not consider CentOS / RHEL derived distributions to be strictly "Fedora-based".
What do I consider active? Given Fedora's rapid release cycle and their somewhat brief support cycle, any distro that hasn't released in a year or more, isn't very active.
I noticed Kir's blog post about the updated vzctl today. Cool! Finally I can create Fedora 14 containers... and the container restart mechanism has been fixed up too.
I downloaded the beta OS Template that the OpenVZ Projects offers for Fedora 14, created a container, did all of the updates, removed the samba* packages, added a few packages I wanted (mc, screen, links), and modified the httpd.conf so it is more like factory. Then I disabled a few services that aren't really needed... after all, who needs xinetd running when it it doesn't have any services configured? Then I stopped the container, cleaned up the container filesystem some, and tar.gz'ed it up and uploaded it as a contrib OS Template.
I did this for both the 32-bit and 64-bit OS Templates. Enjoy!
While investigating a bug in TigerVNC and noticing it was fixed in a recentupdate I discovered that there was a
tigervnc-license package. Just what is that? ...I wondered. When I found out I felt compelled to submit a bug report that I thought I'd share.
I'm not familiar enough with Ubuntu Development to know just how far this might go but at the very least it appears that some Ubuntu developers have identified as a goal to make LXC usable for production stuff and to put it on par with KVM.
The linux container tools (http://lxc.sourceforge.net) raised some interest for the community but there are crucial functionalities which are missing. The purpose of the session is to identify these missing functionalities and prioritize them in order to have a ready for production component for the Natty server delivery.
Make the use of containers for service segregation on par with KVM in terms of functionality and transparancy.
Joe is a system administrator who wants to start a temporary image to run postfix. To save on resources he runs it using a container. He wants to be able to update the image without fear of updates un-doing hacks needed for containers.
Jane is a system administrator who wants to be able to mix containers with KVM VMs through libvirt. She wants libvirt to auto-start containers, and virt-manager to cleanly shut down the containers.
So far I see identification of problems and need for various features... and a LOT of "todo" lists. I hope they get a significant chunk of that accomplished... so that it can filter back upstream and be used by other distros too.
There have been a few occasions where I have wanted to install CentOS on a remote machine that already had a working flavor of Linux on it. Luckily RHEL / CentOS has a way to do this.
- Download the PXE CentOS kernel and initrd image
- Configure the bootloader to boot the CentOS kernel by default
- Configure the bootloader with extra parameters for networking and remote VNC
- Reboot the machine
- Run the vncviewer in listen mode with port 5500 accessible
What is SPICE? - It stands for "Simple Protocol for Independent Computing Environments". What does that mean exactly? SPICE is a remote display protocol designed specifically for use with the Linux kernel's built-in virtualization hypervisor KVM. SPICE is similar to terminal services but rather than multiple users sharing a single, remote physical machine, SPICE allows you to graphically connect to and use a local or a remote KVM virtual machine.
For those who want to just watch a video, here it is. Please note that I kept bumping the tripod by accident and autofocus can be annoying in some spots... and it isn't the highest quality... BUT it does give you a good idea of how well SPICE works.
If you can't see it, your browser probably doesn't support the WEBM video format yet. Right-click on any of the links below (webm and ogv) and download. Then play the file you downloaded in a recent version of VLC.