You are currently browsing the category archive for the 'VMWare Server' category.
This list is subjective, and you’ve been warned!
All of these virtual appliances have been tested with ESX server, and may have issues elsewhere.
For appliances that needed it, I used VMware Converter, the version that ships with Virtual Infrastructure 3.5 (VI3.5).
Please note that both ESX 3.5 and Virtual Center 2.5 are available as trials from VMware currently, and I would highly recommend trying them out as it really is night and day compared to VMware Workstation, Server and Player.
That said, for the most part you’ll be fine working with VMware Server 2.0 - it’s free and has a special version of VMware Infrastructure Client to boot.
The list:
- Astaro Security Gateway - This is a must in any build for me. I use this to bridge between my LAN/WAN and the virtual networks that I create. There is a 10-device, 1000 connection “home user” license available from My Astaro that should be more than sufficient to get you up and running with a clean, secure virtual network.
- Ubuntu 7.10 JeOS Mini-image - this image weighs in at only 70MB or so, expands to roughly 200MB, has apt-get installed, and is a perfect candidate for building virtual appliances with. VMware tools is installed, so you don’t need to worry about things like date and time sync.
- OpenBSD 4.2 - The OpenBSD image is great for getting started in the OpenBSD world: learning the shell, commands, networking, and in my case, firewalling. The verison I use comes from Chrysaor.info, but feel free to use your own.
- OpenSuSE 10.3 - I can’t live without this virtual appliance - I use it for just about everything, and is the first appliance installed in any environment. Note that it is a bit bloated, containing USB, sound and other components typically not needed in a virtual environment. On the other hand, since it’s tried and tested on my end, it’s a lifer.
- Trac - I use Trac as a wiki and VM staging log. I consider all VMs, hosts and Virtual Center as software projects, and monitor changes closely. If ever I need to pull up quick info about a virtual machine, host, network, router or firewall, it’s all in Trac.
- Wordpress - I use my Wordpress virtual machine to stage different versions of blandname, to test updates, upgrades, and plugins. This also allows me to change themes, move Adsense blocks around, and generally to play without fear of losing revenue or breaking something.
- VMware Releases VI3 Perl Toolkit Virtual Machine
- Virtual Desktop Infrastructure 2.0 Download
- VMware Announces VMSafe Hypervisor Security Platform
- Running Virtual Machines on Windows Vista
- Virtual Server VM Disk Usage via WMI
Related Articles:
From the VMware blog:
“Workstation 6.0.1, ACE 2.0.1, and Player 2.0.1 have all been released. These updates address security issues, introduce new functionality, and broaden guest OS support, including experimental support for 32-bit and 64-bit Windows Server 2008 (code name Longhorn).In addition, Workstation 5.5.5, ACE 1.0.4, Player 1.0.5, and Server 1.0.4 have also been released. These updates address security and functionality issues.”
This is interesting because there are new versions of products to talk about, along with new features.
What really made US happy, was seeing that security is still a concern on older releases - specifically VMware Workstation 5.5 (now 5.5.5), which many developpers use to this day for many reasons.
Related Articles:
Since installing bbPress on the forum.blandname.com subdomain, I’ve become addicted to the rapid posting workflow: add topic, title, description and post! It’s 4 steps and is over so quick I’ve been thinking about making a bookmarklet that will automate the task for me. Here’s the latest smaller posts I sent there, but should some day expand upon here (I’ll use blandname for longer posts from now on):
- vTiger CRM Virtual Machine
- RDP Manager for your Windows System Tray
- HOWTO TrixBox - VoIP Virtual Machine
- Online Virtual Machine Builder
- Microsoft Distributes Demo Software via VHD
- FREE Terminal Server Monitoring Tool
- VMware Workstation 6 Feature List
- Multi monitor support for RDP 6
- Add Reflections to bbPress Images
- Google PageRank and Alexa in Your Firefox 2
- Display Digg in WordPress - Digg Dugg Plugin
- Google Analytics Plugn for bbPress
Related Articles:
Currently the only way to get Vista on Vista virtualization running is to either use Virtual Server 2005 with some tweaks, or if you are part of the Virtual PC 2007 beta you can install Virtual PC 2007 (VPC 2K7) on Vista with no tweaks or hacks needed whatsoever. Unfortunately neither of these solutions can virtualize a 64bit operating system, but VMware Server should be Vista compliant soon - so I’m holding me breath until then.
Following my friend’s guide to setting up Virtual PC 2007 on Windows Vista found over at WebandRaptors, I was able to get VPC 2k7 set up quickly and without pain.
Next came the Windows Vista install, which was pretty straightforward. Something to note: you don’t actually need to use a CD key during installation, you can simply click the “next” button and the installer will inform you that a CD key will be needed later, I think it’s about 30days before it becomes necessary.
Once Vista is installed and configured for remote access from within VPC, all you need to do to get Aero Glass running is to connect to the virtual machine using the Remote Desktop Connection (RDP 6) client. If your host, or physical, machine supports Aero Glass, the virtual machine will allow you to take advantage of it, giving you transparent blurred windows, mouse-over taskbar previews, and cool windows+tab animation!
Related Articles:
Up until a few years ago I was getting fed up trying to show Japanese friends that linux was a viable option to Windows XP SP2, because the input method that Linux used at the time quite truthfully stank. The conclusion was that with an English keyboard, Windows was the way to go because of the (then) fancy Japanese input method applet.
Later on, I found out about Berry Linux, a Japanese LiveCD distro based on RedHat/Fedora that can easily show off Linux and allow users to do things like compose email that Japanese people can actually read (common problem on Windows), and surf the web in Japanese by default, instead of having to manually choose codepages and the like, which frustrates must computer users (if they haven’t already given up).
Berry Linux got an update today (to version 0.75), and now supports fancy-pants XGL - which I’m sure you’ll agree kicks Aero’s behind quite handily (footily?). If you’re trying to run Berry Linux Mini as a virtual machine you’ll get a console instead of X and you’ll lose the XGL capabilities, so I’d recommend testing it on a physical machine instead of a virtual machine - it’s a LiveCD so it’s quite safe to do so.
Here’s a feature rundown taken from the Berry Linux site’s English page (corrected a few typos):
- Common Features:
- Support for Kernel-2.6. ALSA, ACPI, selinux.
- Overlay Filesystem Support.
- XGL, 3D Desktop, support.
- Berry Linux is not necessary to install. (Root partition is in the RAMdisk using initrd, all commands are operated by being transfered from CD-ROM)
- It can install on Windows without parting partitions to use Setup.exe or install.bat. (Using squashfs/cloop/loopback device)
- It can install to your hard disk on Linux. (Use Berry Linux Installer or Copy under /BERRY/, and set up LILO or grub)
- Berry Linux can boot from USB-HDD/memory.
- Berry Linux uses WHIZ, a very sharp Kana-Kanji conversion system. (WHIZ Project)
- If you push the windows key, and show the K-Menu.
- Automatically recognizes USB storage, and show icons.
- Berry Linux uses free Japanese True Type Fonts.
- Berry Linux uses bootsplash when booting.
- Berry Linux uses DHCP to connect the Network. (If you’d like to use PPPoE, you should setting up it on the Terminal)
- It’s possible to save personal setting.
- Red Hat Fedora compatible.
- Using new technologies.
- Berry Linux’s Features:
- You can listen to mp3 using BMP/XMMS, and play DVD/DivX using MPlayer, XINE and Kaffeine.
- You can edit files of Microsoft Word, Excel by OpenOffice(TM).
- Berry Linux Mini’s Features:
- Minimum Linux environment is available by using Berry Linux Mini.
- Its file size is very small. (148.0MB)
- It’s light. Because of the Window Manager is Fluxbox.
- You can enjoy comfortable Linux environment.
- Berry Linux Server’s Features: (Published Berry Linux Mini as alpha version)
- Build the Linux Server easily.
- Minimum Server Linux enviroment is available by using Berry Linux Server.
- Its file size is very small. (161.3MB)
- It’s light. Because of the Window Manager is WindowMaker.
- You can enjoy comfortable Linux enviroment.
- To do:
- Support Software Suspend.
- Support Captive NTFS.
- Known Bugs: (Please help me!)
- Kernel panic on boot after realtek RTL-8139 ethernet intialization. (Kernel Bugs)
- Using cloop with kernel-2.4.22-pre7 to 2.4.23-pre2 sometimes stops in boot. (pre5 is OK)
- Sometimes gcc 3.3 is not good ! (Berry Linux 0.19 only)
- krb5.h isn’t in krb5-devel-1.2.8-4. (Berry Linux 0.19, 0.20 only)
You can grab Berry Linux from the SourceForge page or the Berry Linux main page - but I’d recomend using SourceForge if you are in North America as it is much faster.
Related Articles:
In the coming weeks I will be working more on Microsoft’s Windows Vista as it ramps up to release to manufacture (RTM) status.
Although you can currently run Microsoft Virtual Server 2005 in 32 bit mode on a Windows Vista physical machine, I’ve learned that I was recently accepted into the Virtual PC 2007 beta tester program, and that Virtual PC 2007 can run on 64bit Vista.
If you are interested in joining the Virtual PC 2007 beta program, I highly suggest you sign up, then play some fantastic Rod Stewart albums until you are accepted.
By the way, this does in fact mean you can run Vista on Vista reliably now. VMWare Workstation and Server still don’t work at this point, but it’s on the way, just stay tuned.
Related Articles:
From the VMWare Converter 3 beta refresh release notes (found at virtualization.info):
VMware Converter provides an easy-to-use, scalable solution for migrations of machines, both physical to virtual and virtual to virtual. Optimized for mass migration, VMware Converter is equally effective for single-machine conversions. With its comprehensive and comprehensible wizards and task manager, VMware Converter imports virtual machines faster, with fewer manual steps required, and fewer source hardware limitations than other methods. Converter can, with its ability to hot clone, import with no downtime on the source physical machine.
VMware Converter combines and expands the functionality available in P2V Assistant and Virtual Machine Importer. It eases interoperability among VMware hosted products (Workstation, VMware Server, and VMware Player), VirtualCenter-managed ESX Server 3.x and 2.5.x, and unmanaged ESX Server 3.x.
Import from Physical Machines
(Source)
- VMware Converter can hot clone and reconfigure any local or remote physical machine running an operating system noted in Platforms
- VMware Converter Boot CD can be started from, and clone, local machines outfitted with storage controllers and network adapters that Microsoft lists as supported in Windows 2003
Import from Various Third-Party Formats and VMware Products
(Source)
- Microsoft Virtual PC (version 7 and higher)
- Microsoft Virtual Server (any version)
- Symantec Backup Exec System Recovery images1
- VMware Workstation 4.x virtual machine (compatible with VMware GSX Server 3.x)
- VMware Workstation 5.x virtual machine (compatible with VMware Player and VMware Server 1.x)
- VMware ESX Server 3.x
- VMware ESX Server 3.x (when managed by VirtualCenter 2.x)
- VMware ESX Server 2.5.x (when managed by VirtualCenter 2.x)
Export to a Virtual Machine for
VMware Workstation and Datacenter Products
(Destination)
- VMware Workstation 4.x virtual machine (compatible with VMware GSX Server 3.x, ESX Server 2.5.x)2
- VMware Workstation 5.x virtual machine (compatible with VMware Player and VMware Server 1.x)3
- VMware ESX Server 2.5.x (when managed by VirtualCenter 2.x)
- VMware ESX Server 3.x (when managed by VirtualCenter 2.x)
- VMware ESX Server 3.x
Not Supported:
- VMware ESX Server 2.5.x when managed by VirtualCenter 1.x
- VMware ESX Server 2.5.x unmanaged
1. The Symantec family of products includes the Backup Exec System Recovery (formerly LiveState Recovery) products and the Norton Ghost 9 (and higher) products. Only images from the Backup Exec System Recovery products are fully supported, but images from Norton Ghost 9 (and higher) are likely to work.
2. For ESX Server 2.5.x the .vmdk files must be imported using the vmkfstools utility.
3. Only Workstation 5.5 can power on linked imports of .sv2i images.
For more info please visit VMWare’s Converter 3 Beta Refresh page.
Related Articles:
SSH is one powerful tool. You can do just about everything under the sun using an SSH login to a remote computer. SSH works very well in low-bandwidth situations like dialup, or satlinks.
But wakeup, we’re no longer in the 80s - people want GUIs, let’s give them fancy-pants graphics, bouncing cursors and silly linux wizards. Remotely.
Enter Xming, what I would name as top of my favorite applications. Xming is just like X over SSH, for dummies (or people who would rather spend more time working).
Xming allows you to connect to remote or local Linux workstations and servers and run full graphical applications on those remote machines on your local Windows computer.
Here’s how it works: all of the applications are run remotely, but when it comes to the graphics, the information that would invoke the graphics is sent to your local computer, not a bitmap or a sequence of bitmaps like VNC. Xming uses a local X server on your Windows computer in order to display your remote applications. This local X server is 2D accelerated, and it’s sometimes difficult to even notice that you are working remotely.
Since Xming can run in windowed or full-screen modes, you can establish thin client connections in this fashion, or you can publish applications Citrix-style.
Xming is completely free to install and setup. It is a great way to manage virtual machines, and in fact is often faster than Microsoft’s Virtual Server ActiveX control (surprised?), VMWare’s Virtual Machine view (even with VMWare tools!), and even Parallels speedy virtual machine view.
To set the whole thing up, you’ll need a computer running Microsoft Windows, one Linux box, a network connection between the two, but you won’t need much effort.
First install the Windows Xming server on your Windows computer. We’ll use Windows XP SP2 in this example, but it could easily be other varieties. Xming can be found on Sourceforge quite easily, download it, run the install (use defaults), and start XLauncher.
On the Linux computer this are slighlty more complicated, but not by much. For Gnome or KDE on Ubuntu Edgy, go to the System>Administration menu in your menu bar. In Administration, we’ll select login preferences as we’ll be setting up a new logon method (we’re using XDMCP). Select the Remote tab, and enable remote logon (same as local) to your Edgy Eft machine.
Now on your Windows machine, set up XLaunch to logon to your Linux machine using it’s IP address. Save the setting if you want, and connect. You will be presented with a logon screen to your Linux desktop!
Related Articles:
Sometimes, I send articles from blogs or sites that I post to in order to have them published as white papers with business sites to see how well my content will fare. I typically don’t check up on them, and normally forget the logins shortly after submitting. However, I was just crawling through my Mint stats referer information, and noticed that one of the blandname articles got accepted to be published as a whitepaper at Silicon.com.
While this isn’t extremely exciting news, I was impressed nontheless that they didn’t edit the artcile at all - the whitepaper is wholly taken from my article on installing Ubuntu Edgy Eft Knot 3 on VMWare Server (if you haven’t read it yet check it out).
Alright back to work!
Related Articles:
Here is my collection of all of the Windows XP commands that you can start from the Start -> Run dialog box in order to manage a Windows XP (SP2) workstation.
- Accessibility Controls - access.cpl
- Accessibility Wizard - accwiz
- Add Hardware Wizard - hdwwiz.cpl
- Add/Remove Programs - appwiz.cpl
- Administrative Tools - control admintools
- Automatic Updates - wuaucpl.cpl
- Bluetooth Transfer Wizard - fsquirt
- Certificate Manager - certmgr.msc
- Character Map - charmap
- Check Disk Utility - chkdsk
- Clipboard Viewer - clipbrd
- Command Prompt - cmd
- Component Services - dcomcnfg
- Computer Management - compmgmt.msc
- Control Panel - control
- Date and Time Properties - timedate.cpl
- DDE Shares - ddeshare
- Device Manager - devmgmt.msc
- Direct X Troubleshooter - dxdiag
- Disk Cleanup Utility - cleanmgr
- Disk Defragment - dfrg.msc
- Disk Management - diskmgmt.msc
- Disk Partition Manager - diskpart
- Display Properties - desk.cpl
- Dr. Watson System Troubleshooting Utility - drwtsn32
- Driver Verifier Utility - verifier
- Event Viewer - eventvwr.msc
- Files and Settings Transfer Tool - migwiz
- File Signature Verification Tool - sigverif
- Findfast - findfast.cpl
- Folders Properties - control folders
- Fonts - control fonts
- Game Controllers - joy.cpl
- Group Policy Editor - gpedit.msc
- Help and Support - helpctr
- HyperTerminal - hypertrm
- Iexpress Wizard - iexpress
- Indexing Service - ciadv.msc
- Internet Connection Wizard - icwconn1
- Internet Explorer - iexplore
- Internet Properties - inetcpl.cpl
- Keyboard Properties - control keyboard
- Local Security Settings - secpol.msc
- Local Users and Groups - lusrmgr.msc
- Logoff Windows - logoff
- Malicious Software Removal Tool - mrt
- Microsoft Chat - winchat
- Microsoft Syncronization Tool - mobsync
- Mouse Properties - control mouse
- Netmeeting - conf
- Network Connections - control netconnections
- Network Connections - ncpa.cpl
- Network Setup Wizard - netsetup.cpl
- Object Packager - packager
- ODBC Data Source Administrator - odbccp32.cpl
- On Screen Keyboard - osk
- Outlook Express - msimn
- Password Properties - password.cpl
- Performance Monitor - perfmon
- Phone and Modem Options - telephon.cpl
- Power Configuration - powercfg.cpl
- Printers and Faxes - control printers
- Regional Settings - intl.cpl
- Registry Editor - regedit32
- Remote Access Phonebook - rasphone
- Remote Desktop - mstsc
- Removable Storage - ntmsmgr.msc
- Removable Storage Operator Requests - ntmsoprq.msc
- Resultant Set of Policy - rsop.msc
- Scanners and Cameras - sticpl.cpl
- Scheduled Tasks - control schedtasks
- Security Center - wscui.cpl
- Services - services.msc
- Shared Folders - fsmgmt.msc
- Shutdown Windows - shutdown
- Sounds and Audio - mmsys.cpl
- SQL Client Configuration - cliconfg
- System Configuration Editor - sysedit
- System Configuration Utility - msconfig
- System Information - msinfo32
- System Properties - sysdm.cpl
- Task Manager - taskmgr
- TCP Tester - tcptest
- Telnet Client - telnet
- User Account Management - nusrmgr.cpl
- Utility Manager - utilman
- Windows Address Book - wab
- Windows Address Book Import Utility - wabmig
- Windows Explorer - explorer
- Windows Firewall - firewall.cpl
- Windows Management Infrastructure - wmimgmt.msc
- Windows System Security Tool - syskey
- Windows Update - wupdmgr
- Windows Version - winver
Also to note: any executables found in PATH folders, for example “Program Files” can also be run from the Start -> Run dialog as well. This means to start VMWare Sever, you can type in “vmware” and it will start for you!
Related Articles:
UPDATE! The newest client found in the release candidate of Vista does not require MUI files at all. There is some speculation that this may in fact end up as the Windows XP RDP 6 client. Download RDP 6 Client for Windows XP using this link.
I’ve been trying to get the Remote Desktop Connection v6.0 client from Vista to run on Windows XP for months now. Microsoft has announced many times that it’s available tobeta testers through the Connect site, but try as I may I still can’t find it (I’m not alone). So I went ahead and popped the new RDP 6 client from Vista onto Windows XP and tried everything from dependency walking to regsitry hacks to get it going but to no avail. So i kept testing, and set up a Google alert to let me know if anyone had found a method or any information that I could use to get this done.
I got results from the hook today, and what a big fish it was. It seems that I had probably fixed it early on, but hadn’t followed the proper procedure of changing one setting, testing, then moving to the next. I had simply set up all the hacks I thought were needed and plowed ahead. This is what happens when you test with a bottle in hand.
So here is what I found out today: originally from a thread by Caelum over at AtomicPC, this quick hack allows you to install the Microsoft Vista RDP v6 client on a Windows XP computer. Caelum was trying to get widescreen working in RDP on XP, and most of you know that works fine already. But Caelum, you’ve solved another problem in the process!
The 6th iteration of the MSTSC binary has a bunch of outstanding feautures. The biggest one for me is better support for sound and video over terminal services, but also includes ClearType support for those with LCD monitors so fonts look much nicer now.
Let’s get cracking.
1. Download this MSTSC zip(1.3MB)
2. Unpack the ZIP file to a folder
3. Run the “Install.cmd” file
4. Once the installation has completed, press any key to close the window
5. The script does everything but copy the MUI files to SYSTEM32, so we’ll do that now: open your Windows folder, then SYSTEM32, and then en-US. Copy the *.MUI files from your unzipped folder to the en-US folder
6. Run your remote desktop connection application the same way you normally would
Note: If you use Windows XP 64bit Edition you’ll want to grab the 64bit bit files from a 64bit version of Vista.
Now we can connect to Vista and Longhorn Terminal Server using the most up to date client and test the new features offered by Remote Desktop Client 6. I’ve tested this out on both using my VMWare Server virtual machines and the results are very favorable so far - it’s faster than before!
Related Articles:
More and more people are turning to virtualization these days. One of the main reasons is in order to test pre-release, beta, or alpha software. When it comes to Linux, the operating systems are in a state of constant flux so there’s always something new to test. People routinely want to test beta versions of KDE and Gnome and other desktops before comitting, or simply want to see what features are in development.
We’d previously written an article about installing Ubuntu 6.10 Edgy Eft Knot 2 (it IS a long name) on a Mac Mini, so to do the same would be batty. Instead, this guide covers testing the newest Ubuntu 6.10 Edgy Eft Knot 3 on Windows XP using free (as in beer) virtualization. This guide would also apply to anyone testing on various flavours as well, as long as they can run our free virtualization software: VMWare Server 1.01.
Setting up the Ubuntu virtual machine in VMWare server is very easy (click the pictures for larger versions):
Connect to your local VMWare Server installation if you run it locally, or connect to your remote VMWare Server.
We’ll select “typical” for this virtual machine as VMWare Server includes a configuration for Ubuntu already.
And, speaking of which, here it is! Make sure to select the plain “Ubuntu” option, unless you are running a 64bit host, and downloaded the 64bit version of Edgy Eft knot 3.
Name your virtual machine and select the location. The defaults should be fine here but feel free to tinker.
I typically use bridged networking, but for added obfuscation you can use NAT (which creates a virtual network based on your host’s network connection). You could also select host-only if you only want to be able to contact the host operating system. In fact, if you really wanted to make sure the machine is isolated from the wiki wikid web, don it with a nice tinfoil hat and disable networking completely. Ubuntu won’t be happy, but it looks pretty nice in a tinfoil hat.
8 GB of diskspace is fine for testing.You’re not going to be leeching full seasons of Lost… at least we hope so.
Since we opted to allocate diskspace now, VMWare Server will start creating the 8GB file. This can take some time depending on your computer’s hardware. In my case this took a few minutes - I use SATA2 NCQ hard drives and have 2GB of RAM. Your mileage may vary.
You now have a default virtual machine set up, but it will need some slight tweaking in order to install Edgy Eft Knot 3 as fast as possible. Click on “edit virtual machine settings” and remove the floppy drive - we don’t need it. Set the memory to at least 512MB, but it really depends on your total amount. Since I have 2GB total RAM on my host I select 1GB normally. Edit the CDROM settings and point it at your Ubuntu Edgy Eft Knot 3 CD image. Click “OK” - we’re set for lift off.
Press start and drool over the new llivecd boot screen. Note the reflection on the logo. How original.
Now we’re at another original boot screen - the progress loader. Note the gradient progressbar, and the Crystal-esque Ubuntu logo. Reminds us of 3 years ago, doesn’t it precious? Yes, yes it does.
We’ve landed at the desktop. You may stop here if all you wanted was a secure browsing solution with no cookies and passwords to worry about. Should we wish to continue, our mission involves double-clicking that obvious “install” icon. Let’s go for it.
This is an easy 6 step process. Step 1 - select your language.
Step 2 - Select your location or timezone.
Step 3 - Select your keyboard layout. I normally recommend you test the layout just in case. We’ve typed in “blandname” here for demonstration purposes. You may wish to try typing “Ubuntu”, but nothing else lest ye be stricken down.
Step 4 - Identify yourself. This information will be used later in life to incriminate you. Be choosy with naming and passwords. Harry MacDonald that means you! Try typing in something other than your real name here - it works, I promise.
Step 5 - We’ve pre-allocated our diskpace, so no need to worry about this one. Just click the “forward” button.
Step 6 - There really isn’t a step 6. The Ubuntu team has decided to waste our time by confirming the already tedious and easy task. Onward, ho!
Installing - took me 30 minutes. It may take you an eternity, but with hardware prices where thet are, I seriously doubt it will take you long to be rolling with a virtual Edgy Eft install.
The eternity has passed, and we’re going to reboot. Don’t forget to disable or otherwise change the CDROM settings so you don’t end up installing again - that would be embarassing, right?
There you have it - the pretty login screen. Note those options. XDMCP looks very intriguing doesn’t it? We’ll get to that later…
And presto! What have we got here? Firefox 2.0b1 - Bon Echo Beta 1! Try it out and see what you think, I’m impressed so far to be honest.
So that’s it, you now have a working Ubuntu 6.10 Edgy Eft Knot 3 test virtual machine (edit: let’s make the name longer). And it weren’t hard neither! When Knot 4 comes out you’ll be able to do it in your sleep. If not, well we’ll see you searching for it again.
Related Articles: