Set up your email account

1. Log in to your email and click the gear on the top-right.  Choose “Mail Settings”.
2. Click “Forwarding and POP/IMAP”.
3. In the ‘IMAP Access’ section (third one down) choose ‘Enable IMAP’ and click ‘Save Changes’ on the bottom of the page.

Set up your phone

1. On your Android phone, click ‘Settings’ (it’s listed alphabetically when you’re viewing the ‘All apps’ screen).
2. Tap ‘Accounts’, and tap ‘Add Account’.
3. Choose ‘Google’.
4. Tap ‘Next’, then tap ‘I already have a Google account – Sign In’.
5. Enter your full email address and password then press Next.
6. Check the options you want to sync – I suggest ‘contacts’, ‘Gmail’ and ‘Calendar’.
7. Click ‘Finish’, then ‘Finish Setup’.
8. You will now be able to see this account in the ‘Gmail’ app on your phone.  Tap and hold the gmail app to add it to your home screen.

Although the MyBook World’s interface offers the ability to join a domain, and use domain users and groups to controll access, this is not supported.

Basically, the MyBook “advanced” interface allows for you join the device to the domain and to specify AD users and groups for folder permission, but they won’t help you troubleshoot when it doesn’t work.  And it doesn’t work by default on a Windows 7 or OSX machine.  Thanks WD, and yes, this post is my ‘screw you’ answer to that policy.

So here’s the 2 issues most people run into when you do a Google search for ‘MyBook domain’, and how to fix them.

Machine can’t be added to the domain

• In the advanced web interface on the MyBook, click ‘System’ – ‘General Setup’.  Check out the time – it’s probably wrong.
• The MyBook is getting the time by default from a global time server by default, pool.ntp.org.  For whatever reason, the MyBook seems to get the correct time from the NTP server, then screw it up when applying it to itself, making the time be off anywhere from 30 minutes to 4 hours.
• When you try to add the MyBook to the domain, the MyBook sends the time along with that request.  The domain sees this incorrect time and assumes something is wrong and won’t let the MyBook join the domain.
• Change the ‘NTP Time Server’ field from pool.ntp.org to the IP address of whatever domain controller you’re going to send the request to.  At least then they’ll agree on the time, even if it’s not perfectly accurate.
• In some domains, the MyBook needs to also be able to reference itself by name, which means you need to make an A record and its corresponding Reverse Lookup record on your DNS server.  You probably don’t want to have to refer to a folder share as “\\10.10.1.1\sharename” anyway when you can have something more memorable like “\\WD-MyBook\sharename”, so you might as well go ahead and make this record on your network’s DNS server (usually the domain controller) to keep you and the MyBook happy.

You should be able to now join the MyBook to the domain at this point.

• Click ‘Network’ – ‘Workgroup’, and enter
• ‘Domain Name’ is the Fully Qualified Domain Name, or FQDN. If you don’t know what this is, right-click ‘My Computer’ on your machine and click ‘Properties.  In Windows 7, the FQDN is listed in the ‘Computer name, domain, and workgroup settings’ next to ‘Domain:’.  It’ll say something like domain.com or domain.local.
• Leave NetBIOS blank.  If this works, it’ll fill that in automatically. If this doesn’t work, filling that field in probably isn’t your problem.
• Domain controller IP address: this is the IP address of the domain controller that the MyBook should get its time from.  It’s also hopefully the same machine that you entered the A record into.
• The last 2 fields are for a username and password of someone authorized to add computers to the domain.  You just enter in the username and password, you don’t need to enter the username as ‘DOMAIN\username’ or anything.

After the device is on the domain:

1. Create a shared folder. (‘Storage’ – ‘Folder Shares’ – click the page icon with a “plus” on it)  Fill in the share name, be sure to leave ‘Setup access control after creating this share’ is checked and click ‘Submit’. The MyBook will take forever to think about this, just let it be – it can take 30 seconds or so.
2. Now you’re asked who gets access to this new shared folder on a horribly-laid-out page.
3. On the left you’ll see 2 windows: the top one has all of your domain users, and the bottom one has all of your domain groups.  It only shows the first 18 characters or so until the scroll bar cuts off the names of the users, so hopefully your domain name is short enough so you can tell who is who.  (What’s up with that, WD?)
4. On the right are 6 boxes.  They’re labeled stupidly, so just so you know, the first 3 boxes are for full, read only or no access for AD users, and the last 3 are exactly the same thing, but for AD groups.  I can’t think of how to make this interface more confusing, but it seems to function, so…whatever.
5. Click ‘Submit’ and you’re done.

but wait!

Windows 7 machines can’t access shares controlled by AD permissions

And you thought you were done.  As it turns out, Windows XP handles passing your AD credentials to the MyBook just fine.  Windows 7, not so much.  Windows 7 is passing your username and password to the MyBook incorrectly, and when it breaks, it’ll ask you for a domain username and password that has permissions to access the folder.  You probably have access to this folder, it’s just asking because it knows something went wrong and is assuming you don’t have access.  You can type valid usernames and passwords into this window all day long and it won’t work, whether you have access or not.

Before the Windows XP holdouts in the office snicker too loudly, this is an easy-ish fix.

1. The problem here is that Windows 7 is trying to work with the SAMBA protocol of the MyBook.  Except someone at Microsoft decided that it would be a good idea to ship Windows 7 and (at least on my 64-bit edition) not specify the way in which Windows 7 should respond to SAMBA requests.  SAMBA is a protocol used by non-Microsoft file servers, so…intentional?  Who knows.
2. Tell Windows 7 how to talk to non-Microsoft file servers by clicking ‘Start’ -> ‘run’ -> type “secpol.msc” and hit enter.  Hopefully you have the permissions to do this.  If not, show your IT department this section and they’ll see you’re not trying to do anything too ridiculous, just trying to make Windows 7 play nice with SAMBA. (Hey IT folks – maybe you want to include this as a GPO setting for any folks that use non-MS fileservers)
3. Click ‘Local Policies’ -> ‘Security Options’ -> ‘Network Security: LAN Manager Authentication’
4. If you’re anything like me, the drop-down was blank.  You actually can’t make this drop-down be blank through this interface, so obviously something is wrong.  According to Microsoft’s documentation,  ’NTVLM2 responses only’ is supposed to be selected by default, but this won’t help you.   To talk to the MyBook correctly, you need to use ‘LM and NTLM – use NTLMV2 session security if negotiated’.  Change to this setting and click ‘OK’.

Now, when you access the share at \\MyBook\share, your computer will automatically pass the domain username and password you used to log on to your computer.  If you have permissions to this folder, it’ll just open.  If you don’t have access, it’ll ask for a username and password of someone in your domain that does.

If you have problems beyond this, post in the comments – this should cover 99% of the problems people are having in the first few pages of results when you search for ‘MyBook domain’, but I’ll be interested what other issues are out there.

This procedure will set up your Macbook Pro in such a way that a menu will appear on boot that will require the selection of Mac OS (tested with 10.5.3), Windows (tested with Vista 64-bit), or Linux (tested with Ubuntu 8.04 64-bit – Alternate Install CD). This procedure assumes that you want the drive divided evenly between all operating systems, and can take up to 5 hours to complete, not including burning OS install disks. Most of this time will be spent waiting for progress bars, and the laptop will be unusable for work.  (So you can plan accordingly)

Install Mac OS X

(Assumes Mac OS X 10.5.3)

1. Back up all documents, including Notes files, browser bookmarks, etc. to the network or USB thumbdrive.
2. Install OS X to the Macbook Pro, using the entire hard drive.
3. Use the Boot Camp Assistant to partition the drive.
   1. Start the Boot Camp Assistant, located at /Macintosh HD/Applications/Utilities/Boot Camp Assistant
   2. The “Windows” partition shown will eventually become both the Windows and Linux partitions. Therefore, if you wish for the drive to be divided equally across all operating systems, slide the divider until the Windows partition takes up two-thirds of the disk.
   3. Click ‘Partition’ and wait for the process to complete.
   4. When the partitioning process completes, click ‘Quit and Install Later’. Do not use the Bootcamp installer.

Install Windows

(Assumes Windows Vista 64-bit)

1. Insert the Windows install CD or DVD and reboot the machine. Hold down the ‘c’ key to boot from the CD. (note: at this time, the Windows XP 64-bit install DVD does not recognize the keyboard or USB keyboards when booting from DVD)
2. Once the Windows installer loads, proceed as normal through the installation. When asked where to install Windows, select the partition that is approximately two-thirds of the disk. In testing, this was ‘Disk 0 Partition 3 BOOTCAMP 126.1GB’.
3. Highlight the partition and click ‘Drive Options (advanced)’.
4. Click ‘Format’ and ‘OK’.
5. Now that the drive is formatted, click ‘Next’. Windows will install.
   1. During the Windows install process, the machine may reboot on its own several times.
   2. Windows is rebooting and expecting to boot back into the installation process. You need to help it do so by holding down the ‘Option (Alt)’ key when the machine reboots, and manually selecting the ‘Windows’ hard drive. (not the ‘Windows’ CD)
   3. If you miss the chance to reboot into the Windows install process, the machine will boot into OS X. Just reboot the machine, hold down the option key, select the ‘Windows’ hard drive (not the CD) and continue from there.
6. Once installation is complete, the machine will boot into Vista and have the user complete the setup procedure.
7. Eject the CD from within Vista by clicking the drive once in ‘Computer’ and selecting ‘Eject’ on the title bar. Vista now needs drivers for the Macbook Pro hardware.
   1. If you want to be able to have greater control over the fans in the Macbook Pro cooling system, you need to install the ‘inputremapper’ application (tested version 1.0.04) first. This is recommended, as the Macbook Pro can run quite hot at times, dependent on the ambient air temperature.
      1. Download and install inputremapper. You will need to use a USB key, as the networking drivers for the Macbook Pro have not yet been installed.
      2. Reboot the machine, holding down the ‘option’ key and choosing the Windows drive.
   2. Install the Windows drivers for the Macbook pro hardware by inserting the ‘Macbook Pro Install CD 1′ in the drive. If the Bootcamp Drivers application doesn’t start automatically, double-click on the CD in ‘Computer’ and run WindowsSupport/setup.exe.
   3. Once the drivers are installed, eject the CD and reboot the machine into the Mac OS partition.

Install rEFIt

1. Boot into the Mac OS partition and install rEFIt. This is our boot menu application.
   1. Download and install rEFIt (tested version 0.11)
2. To set rEFIt to always be the boot menu, open a terminal window and give the command:

   /efi/refit/enable-always.sh

3. rEFIt has a default timeout of 20 seconds, then will boot into OS X. If you would like to disable the timeout:
   1. Open /efi/refit/refit.conf in Text Editor
   2. Change ‘timeout 20′ to ‘timeout 0′.
   3. Save and close.

Install Linux

1. Enter the Linux install CD (tested Ubuntu Linux 8.04 Desktop 64-bit Alternate Install) and reboot the machine. Hold down the ‘c’ key to boot from the CD. You might need to use an external USB keyboard, as sometimes the Linux install CD doesn’t recognize the built-in keyboard correctly.
2. Install as usual, until you get to the partitioning section.
   1. When Linux installs, it will corrupt the portion of the Master Boot Record on the current Windows partition. In order for Windows to be usable, the MBR installed on this partition must be backed up.
   2. When the installation procedure asks about partitioning disks, exit to a command line and make a backup of the MBR of the Windows partition.
      1. In Ubuntu, this is done by pressing Alt-F2 to get a command line.
      2. Enter

         dd if=/dev/sda of=/tmp/sda.mbr bs=512 count=1

         and hit the ‘Enter’ key.

      3. Press Alt-F1 to return to the Ubuntu installation.
   3. Choose the ‘Guided – Resize…’ option. (in testing, this was ‘Guided – Resize SCSI3 (0,0,0), partition #3 (sda) and use freed s’)
   4. Make the Linux partition 50% of the resized space (one-third of the overall drive, if the Windows partition was two-thirds…)
   5. Continue the installation process.
   6. After the base Linux OS files are installed, but before installing a Linux bootloader, the MBR must be restored from the backup that was created earlier.
      1. In Ubuntu, this is done by pressing Alt-F2 to get a command line.
      2. Enter

         dd if=/tmp/sda.mbr of=/dev/sda

         and hit the ‘Enter’ key.

      3. Press Alt-F1 to return to the Ubuntu installation.
3. Continue the installation process until reaching the bootloader installation screen. (in testing, this was the ‘GRUB installation’ page.)
   1. In Ubuntu, do not install GRUB to the MBR. Windows needs the MBR as it is.
   2. When asked where to install GRUB, choose the Linux installation partition (not the swap). In testing, this was /dev/sda4. (Note that this partition is one greater than the partition specified on the ‘Guided – Resize…’ line of the ‘Partition disks’ screen.
4. When the installation is complete, eject the CD (if it is not done for you) and reboot the machine.

Update rEFIt

At this point, rEFIt will see all three operating systems and can load Mac OS and Windows, but needs to have its own partition records updated to be able to properly allow Linux to load.

1. Once the machine is rebooted and on the rEFIt screen, press the arrow keys until you reach the ‘Partitioning Tool’ icon. Press the ‘Enter’ key.
2. When it asks “May I update the MBR as printed above?” press the ‘y’ key. rEFIt’s partiton records will update.
3. You should now be able to boot into any Operating System.

Notes and Observations

General

• To disable the Apple ‘bong’ noise when the machine starts, install and configure StartupSound.prefPane.

Windows

• Windows will check (CHKDSK) its partition the first time it boots. It notices the difference in partition size. This is fine, let it check it. Windows still loads afterwards.
• The right-click behavior in Mac OS (Control-click) can be replicated in Windows by using inputremapper.

Linux

• To reduce the amount of time the GRUB menu appears when booting Linux (tested Ubuntu), edit the file /boot/grub/menu.lst where it says ‘timeout 10′ to say ‘timeout 3′ or whatever your preference is.
• To replicate the right-click (and middle-click) functionality in Mac OS by using Control-click,
  • Go to System > Preferences > Keyboard > Accessibility tab > General – and enable “Allow to turn accessibility features on and off from the keyboard”
  • Go to System > Preferences > Keyboard > Mouse Keys tab > and enable “Allow to control the pointer using the keyboard”
  • From the terminal, type

    gedit ~/.xmodmap

  • Type:

keycode 116 = Pointer_Button3

keycode 108 = ISO_Level3_Shift

• • Save and close the file.
  • Go to System > Preferences > Sessions and click ‘Add’.
    • Name: xmodmap
    • Command: xmodmap /home/fuz2y/.xmodmap
    • Comment: Add middle- and right-click functionality
    • Click ‘OK’.
  • Restart X to use the changes (Ctrl-Alt-Backspace).

After applying an image of Ubuntu Linux to a target machine, GRUB may need to be repaired before the machine will boot properly. To repair GRUB, do the following:

1. Load the Live CD, boot from it until you reach the desktop.
2. Open a terminal window.
3. Type “sudo grub”
4. Type “root (hd0,0)”, or whatever your harddisk + boot partition numbers are.
5. You can easily look up the boot partition for the version of Ubuntu on the hard drive by browsing to the hard disk from the LiveCD desktop.
6. Open /boot/grub/menu.lst in a text editor.Scroll to the bottom and look up which partition the menu choice for Ubuntu points to. (hd0,0 by default)
7. Type “setup (hd0)”, or whatever your harddisk number is.
8. Quit grub by typing “quit”.
9. Reboot the machine.

(tested with 64-bit Ubuntu Linux 8.04)

“Anything behind walls” sounds too invasive…

[The scientists] coated micron-size magnetite spheres with oleic acid and dispersed them through a ferrofluid, which is a suspension of much smaller magnetic nanoparticles (in this case held in kerosene). When an external magnetic field was applied to the fluid, which was held in a glass cell, laser light passing through the medium was trapped inside. Photons escaped when the field was switched off.

Could this be a solution for an optical storage medium, to complement an optical processor?

“SCiB” touted to be safer than today’s Lithium Ion, lasts 10 years, charges in minutes (@ up to 50 amps).

1/3 pound (150 gram) cell is
- the size of a mobile phone
- provides 4.2 aH @ 2.4 volts. (devices)

4.4 pound (2 kg) cell is
- the size of a small paperback novel
- provides 42 aH @ 24 volts. (vehicles)

If they are able to deliver in mass production at a profit, this could be a major new development in both transportation and electronic devices.

Toshiba Press Release

So how do I restore my pretty GRUB menu, and give myself the option to boot into either WinXP or Ubuntu 7.10? Every once in a while, I have to write an install script for a Windows app, so I do need to set this up…

First of all, let’s have a look at the grub menu file. I click on ‘Places’ in my menu, and go to:

Filesystem/boot/grub/menu.lst

I see the file that gives me my menu when I boot! Now there are a lot of helpful comments here, but if I strip the comments out, I essentially see these basic options:

default 2
timeout 5
color cyan/blue white/blue
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=d403f712-7e72-4bc4-af12-0549fbc1624f ro

## Setup crashdump menu entries
## e.g. crashdump=1
# crashdump=0

## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,2)

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single

## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all

## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true

## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false

## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false

## ## End Default Options ##

title Ubuntu 7.10, kernel 2.6.22-14-generic
root (hd0,2)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=d403f712-7e72-4bc4-af12-0549fbc1624f ro quiet splash
initrd /boot/initrd.img-2.6.22-14-generic
quiet

title Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.22-14-generic root=UUID=d403f712-7e72-4bc4-af12-0549fbc1624f ro single
initrd /boot/initrd.img-2.6.22-14-generic

title Ubuntu 7.10, kernel 2.6.20-15-generic
root (hd0,2)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=d403f712-7e72-4bc4-af12-0549fbc1624f ro quiet splash
initrd /boot/initrd.img-2.6.20-15-generic
quiet

title Ubuntu 7.10, kernel 2.6.20-15-generic (recovery mode)
root (hd0,2)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=d403f712-7e72-4bc4-af12-0549fbc1624f ro single
initrd /boot/initrd.img-2.6.20-15-generic

title Ubuntu 7.10, memtest86+
root (hd0,2)
kernel /boot/memtest86+.bin
quiet

### END DEBIAN AUTOMAGIC KERNELS LIST

Now that your eyes are glazed over, the important parts are at the top and the bottom. On the bottom of this list, we see the 5 entries that I’m seeing now when my machine boots.

On the top of the list, ‘Default’ says which of the 5 entries will be selected automatically. The entries are always numbered 0, 1, 2, 3, 4… etc. It starts with zero. So the defualt of 2 means that the third choice will be my default. I know, confusing, but that’s how it is.

So no entry here for Windows XP! You can see that the entries have a fairly standard layout though, so let’s put it back in. the grub file already has a helpful guide listed:

# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro

You can look up more info on GRUB works here, but what I’m most interested in is the ‘root (hd0,0)’ line. What this line says is that the root of whatever entry I’m doing is located on (drivenumber/partition). Since I only have one hard drive, I know my entry has to be something like this:

title Windows XP Professional SP2

root (myharddrive,somenumber)

makeactive

chainloader +1

(That last entry lets GRUB pass off the boot process to Windows’ native booter.)

So if I want to list all the partitions on my hard drive, I can give the console a: sudo fdisk -l

And I get this:

Device Boot Start End Blocks Id System
/dev/sda1 * 1 3823 30708216 7 HPFS/NTFS
/dev/sda2 3824 4119 2377620 f W95 Ext’d (LBA)
/dev/sda3 4120 4864 5984212+ 83 Linux
/dev/sda5 3824 4078 2048256 b W95 FAT32
/dev/sda6 4079 4119 329301 82 Linux swap / Solaris

Well this makes sense… I have my first partition as NTFS, that’s Windows XP. I can see I have a few other partitions, mainly a 2GB FAT32 partition that I use as a play area, and my Linux partitions. I only have one hard drive, so my ‘root’ listing has to be (hd0,xxx). Since I want the first partition, I’ll make it root (hd0,0)

So my entry will be:

title Windows XP Professional SP2

root (hd0,0)

makeactive

chainloader +1

I’ll add that entry in, as well as partition out some of the other entries I don’t use. I’ll also name the Ubuntu menu choice something nicer than ‘Ubuntu 7.10, kernel 2.6.22-14-generic’. Now my choices read:

title        Please choose an Operating System
makeactive

title        ———————————
makeactive

title        Windows XP Professional SP2
root        (hd0,0)
makeactive
chainloader     +1

title        Ubuntu 7.10 Gutsy Gibbon
root        (hd0,2)
kernel        /boot/vmlinuz-2.6.22-14-generic root=UUID=d403f712-7e72-4bc4-af12-0549fbc1624f ro quiet splash
initrd        /boot/initrd.img-2.6.22-14-generic
quiet

Now one very important thing: my default is still set to ’2′, which means the title = 0, dotted line = 1, WinXP = 2, and Ubuntu = 3.  I changed my default to 3, so Ubuntu automatically boots up.  You might want to have WinXP boot, it’s your choice, just get the number right.
Also, if you want a shorter boot time, you can change ‘timeout’ to 5 like me, or leave it on 15 seconds or whatever grub’s default time is.

…and that’s it!  When I boot my machine, I get a nice, clean menu that looks like this (except the dotted line is exactly the same width as the ‘Please choose…’ line:

Please choose an Operating System
———————————
Windows XP Professional SP2
Ubuntu 7.10 Gutsy Gibbon

Ubuntu is selected by default, and if I don’t do anything for five seconds, Ubuntu boots.

Whoa, whoa! I said average-user. Yes, I still have a WinXP gaming machine at my house for Team Fortress 2, Portal and Battlefield 2. However, reports are already coming out that Steam (Portal and Team Fortress 2) successfully runs under WINE. With the eye candy like Compiz Fusion, 7.10 now looks as good, or better than, Windows Vista, with a fraction of the overhead. What will be interesting to see is the gaming performance on 7.10 under WINE vs. on Vista with its inherent resource demands.

The features I see as the most valuable happen to be the most boring, but they’re:

• Ease of use in finding drivers for your hardware
• One-click server setup for common sevrer roles like File/Print servers, DNS, Web server, etc.
• NTFS support, which will GREATLY help introduce 7.10 machines to Windows-based networks.

All in all, you can try out 7.10 without having to erase anythimg. Simple burn a CD, but it in the drive, and restart your machine. You can check it out before you take the plunge. Perhaps the next time you’re going to consider re-installing Windows 2000 on that old machine you’ll consider 7.10, or when you’re re-installing WinXP, go for a dual-boot setup. or maybe even just go for it and order an Ubuntu machine direct from Dell!

Check this link out for a tour of the full features of 7.10: