\documentclass[a4paper,12pt]{article} \usepackage[margin=25cm]{geometry} \begin{document} \begin{enumerate} \item Geoff asked about Plone: it's heavy, uses lots of RAM. Get it running first before accepting the \$100. \item Question about firefox with III, crashing with particular URLs. New gecko in Mozilla, will be in new Firefox 1.5 next month or so. \item Opera has all caps problem. Poor plugin interface. \item Traffic controller: TC to speed up some network packets; has no documentation. Wonder shaper: a script that uses tc; depracated on a 2.6 kernel. Bad connection simulator. Can randomly duplicate, throw away packets. \item Ealry-bird registration for Linux NZ closes tonight? Opens tonight? Duneden: NZ \end{enumerate} \section*{Breezy applications:} \begin{enumerate} \item XFCE shown at last: ocopus with too much love to give: who wantsw four hugs? \item New file manager: not really working properly. Don't use it yet. Thuna. Replaces xffm. \item xffm is a tree-view file manager. \item Geoff says I should try Roxx. \item Jeff says that nautilus manages files. \begin{enumerate} \item uses the same thumbnails for totem, other files, jpegs, \ldots. These go into files in your home directory. Put in extended attributes? \item dpkg-reconfigure --priority=high xserver-org \end{enumerate} \item F-spot photo management app: Jeff Waugh says: like iphoto on Mac, but intended audience have v high res cameras, shows graph of how many photos taken at particular periods, so can find holidays as spikes in frequency; can have tags for people or places. Can assign images to tags also. Can drag photos into these tags on left. Understands Exif. Exports to Flikr and other photo online tools. Talks to gallery version 1, and can make photo CDs as well. A nice presentation mode. \item Larry Ewing wrote F-spot as well as Tux. \item Gimp; can draw capsicum eyes, Can't do CMYK, or with great depth of more than 32 bits: can't do great bit depths. Has support for pressure sensitive writing pads. \item Inkscape: svg editor: Can do cursive handwriting with a tablet. Can export from dia. Sodipodi: inkscape is a fork of sodipodi. \item dia: has Cisco diagram stuff, but cannot rotate. Also does not have a default text size. Not true: you can \item gstreamer and xine are the backends for totem. Only use totem with xine backend. People seem to like totem with xine as a backend rather than xine itself. \item 15 HPs at Craig's work: see Craig's phone number, ring him. \item Rhythmbox: for playing music. \item apache had problems until started lo. Needed to start the loopback interface. \item Tea break. \end{enumerate} \end{document} \section{Mainframe virtualisation} \begin{enumerate} \item Played with UML, other things \item Various technologies: good, bad, uglies \item Vitualisation in Wikipedia \item Xen; good for? \begin{enumerate} \item realistic testing environments: run other distributions \item Keep php separate \item playgounds \item upgrade testing \item jails for insecure services \item a simple way of limiting reource hogging \item lots of servers for less hardware, less power and space \item disaster recovery, migration from host to host \item simplify hardware support: all same network card driver, video card driver. \item clean build and test environments \end{enumerate} \end{enumerate} \begin{enumerate} \item chroot \item Linux Vserver \item XEN \item VMware \item \item \item \end{enumerate} \section{chroot} \begin{enumerate} \item simple to setup \item can easily break out \item all processes run on same kernel \end{enumerate} \section{Linux Vservers} \begin{enumerate} \item chroot on steriods \item ALso process list \item kernel memory \item network interfaces \item filesystem \item very little overhead \item patch the kernel \item all servers use the same kernel \item no loopback interface \item Linux only \item Solaris zones are a bit like this. \end{enumerate} \section{VMware} \begin{enumerate} \item virtualises whole hardware \item emulates at BIOS level \item easiy to set up \item no kernel patching \item need install drivers for VMware hardware \item expensive \item only supports some Linux distributions (not Ubuntu yet) \item emulation overhead \item \end{enumerate} \section{qemu} \begin{enumerate} \item free \item supports differnt architectures \item no kernel patching required \item can emulate any OS that supports a standard netowrk card and vide \item support for emulating one architecture on another (m68k on x86) \item not very stable \item emulation overhead, more than VMware \end{enumerate} \section{UML} \begin{enumerate} \item A linux kernel and all of its associated processes run as a single process group under a regular patched kernel \item Need a patched kernel both for guest and host \item Patch host kernel to provide some more system calls \item guest is a kernel built for a new architecture (uml) \item Can have different kernels on same machine \item Linux only \item x86 only \item \end{enumerate} \section{Xen} \begin{enumerate} \item Like full hardware virtualisation \item like UML \item the hypervisor is a little shim that OS has to talk to \item need port OS to this \item had Microsoft ported to it. \item can implement hypervisor in hardware, so no need to port OS \item hardware support is coming in new CPUs possibly \item there is BSD support \item multple kernel versions and distros at once \item VM can get direct access to the hardware if permitted \item Efficient sharing of resources \item VMware and qemu have to be more rugged; but here the OS is cooperating with the hypervisor, and so things run faster. \item Simple demo CD (Xknoppix?) \item Annoying: need preallocate RAM to virtual machines \item New OS must be ported \item need patch the kernel \item build scripts \end{enumerate} \section{Q\&A after technical intro} \begin{enumerate} \item FOr Power PC, there's Mac on Linux. \item run Mac OSX, maconlinux.org \item pear PC for MAC os, Linux \item runs on Windows to \item All are free software except for VMware \item UMLs allow providers to give root access to their clients \item Fast enough to be usable \item qemu: slow as a dog with software that accesses hardware \item UML accessing disk: slow \item Accessing CPU a lot: may be quite fast \item \end{enumerate} \section{Demos: qemu} \begin{enumerate} \item A file is a file system \item dd if=/dev/zero of=/uml/qemu-deo bs=1megabuyte count=0 seek=5000 \item ls -lsh /uml/qemu-demo \item It uses no disk space until it is needed, but has 4.9G \item qemu -hda /uml/quemu-demo -cdrom /dev/cdrom -boot d -m 512 \item Installed Windows 2000 onto this. \item No need to run a full system image \item Can run \item copy on write file system \item the only disk space using is the stuff that has changed \item to each system, seems have a lot of disk space \item guml: demos UML: he has written a python GTK application \item can have virtual firewalls, and route between them. \item uml\_mkcow /uml/sid\_new /uml \item Like Xen more, but Xen and ACPI has problems \item UML is solid \item Xen is better if don't mind a little oddness every now and then \item UML is no infinitly recursive. Can run UML inside UML though. \item Can recover with Xen: can take a snapshot of a system every hour. Can take snapshots very quickly. \item Can have basic Xen images and roll them out quickly \item Can allocate memory and take or add memory on the fly to Xen. \item Use LVMs instead of a loopback file system. \item hypervisor is quite small. \item Live Xen disk: can start new instances very quickly \item Can run them on SAN systems to have a rapid restarting of the system. \end{enumerate} \section{} \begin{enumerate} \item \end{enumerate} \section{} \begin{enumerate} \item \end{enumerate} \section{} \begin{enumerate} \item \end{enumerate} \end{enumerate}