IP Addresses and Computer Names...

I couldn't ping a computer name, just an IP address. And the internet (in its wisdom) posted a fix here.

Update /etc/nsswitch.conf to add "wins" to the line "hosts:"

And you also need to install samba, samba-common and samba-winbind...

Chrome SE Linux fix...

From here:

# cat /var/log/audit/audit.log | grep chrome | audit2allow -m local > local.te
# make -f /usr/share/selinux/devel/Makefile
Compiling targeted local module
/usr/bin/checkmodule: loading policy configuration from tmp/local.tmp
/usr/bin/checkmodule: policy configuration loaded
/usr/bin/checkmodule: writing binary representation (version 10) to tmp/local.mod
Creating targeted local.pp policy package
rm tmp/local.mod.fc tmp/local.mod
# semodule -i local.pp

Colours...

Not an interesting post by any means. However, as an aide memoir, it is probably a good idea to write down the colours we've used so far in painting the house, so we can repaint them when the kids get creative with their crayons:

Living Room: Almost Oyster and Muddy Puddle

Smaller Bedroom: Natural Hessian

Front Bedroom: Amber Spirit (Light and Space)

Rebuilding Windows

I need to rebuild Windows again (it has been a few years now). So I will need to install:

• Windows
• Windows Updates
• MS Security Essentials
• Printer Drivers
• Webcam Drivers
• Mouse Drivers
• Bamboo One Drivers
• MS Office
• Skype
• Adobe Photoshop
• Canon Camera Software
• Digiguide
• VirtualBox
• Tweetdeck
• iTunes
• Chrome + apps: Amazon, tasks, Chrome too Phone and AdBlock
• HTC Sync
• Picasa
• FoxIt Reader
• CutePDF
• MS SyncToy
• Roxio CD Creator
• Auslogics Disk Defrag?
• Programmer's Notepad
• Vuescan

Could take a while. And see here for the historical XP version...

Linux post-install...

Once it has been installed, there are a couple of things needed to make it a better experience.

These are (package names that can be used with yum):

• google-chrome
• vim-enhanced
• kdebase (konsole)
• kdesdk (kompare)
• eclipse-platform

Also need to:

• add "paul ALL=(ALL) NOPASSWD: ALL" using visudo
• usermod -g vboxsf paul
• ln -sf /media/sf_Documents ~/Documents
• ln -sf /media/sf_Pictures ~/Pictures

VirtualBox Guest Additions...

It seems that sometimes they just stop working. So... to get them running on Fedora, the following instructions apply:

• Install Guest Additions Virtual Drive: Devices-> Install Guest Additions (may have to Remove Disk from Virtual Drive then repeat to get Linux to auto mount).
• su -
• yum update
• yum install dkms gcc
• cd /media/VBOXADDITIONS*
• sh ./VBoxLinuxAdditions.run

You may need to reinstall the appropriate kernel devel packge (it will tell you it can't find the correct files). And then restart the Guest machine...

Oh, and note that if you want GNOME3 to work, you need to select 3D acceleration in Virtual Box settings...

Backup Strategy...

I have noticed that Windows Backup only appears to back up files that have programs associated with their file extensions.

Which means that all my Perl files which were only run through Linux, weren't backed up.

I just think it's a little too clever for its own good...

Edit: on installing ActivePerl for Windows, Backup still doesn't backup these files. It appears maybe it is just not clever enough...

Liberty Valance...

There seems to be a quite ridiculous and unjustified amount of hand-wringing over the events surrounding the death of Osama Bin Laden and demands for justification of why he was not captured and put on trial.

But this is a pretty good response...

Virtually...

So, my old 750MHz box which found a new lease of life with Linux may have just lost it again after installing VirtualBox on my main PC.

This allows the installation and execution of a Guest OS simultaneously with the Host OS.

Installation of a Linux Guest is easy. However, this only gives a screen resolution of 1024x800 for the Guest. To increase it, you need to update the Linux kernel and install VirtualBox Guest additions. Full instructions can be found here.

Also worth noting is that if you want to ssh into the Guest from the host, using NAT it is necessary to set up port forwarding (see VirtualBox User Manual section 6.3.1). Once this is done, it is necessary to ensure ssh is running on the Guest, and ssh in with the correct port, e.g. using Xming:

plink.exe -l user -p 2222 localhost

Finally, it is good to set up folder sharing so you can access all the files on the Host. This is explained in section 4.3 of the User Manual, and you just have to make sure that the user is in the vboxfs group using:

usermod -a -G vboxfs user

And that should give a full screen Guest OS with access to the Host directories wherever necessary without the overhead of maintaining either separate hardware, or a dual boot system. Brilliant!

Network Geography and Topology (Part 2)...

Setting up ICS wasn't so easy the second time, probably on the basis that I forgot to document some steps in the last post.

So, to do things properly, you have to set the router to IP address 192.168.2.x, so the wireless adapter on the Windows PC connects on an appropriate subnet.

Then, on the wireless internet connection, right click properties and enable ICS.

It is probably necessary to set the IP address of the wired adapter to 192.168.0.1, and on my Fedora installation, the Linux box sets itself up on 192.168.0.254.

From the Linux box, you should be able to ping the Windows box on 192.168.2.x, and a good check is to ping a website, the IP address of which can be obtained by pinging from the Windows PC (e.g. ping www.google.co.uk).

If that works, then you just need to set up the DNS addresses on the Linux box. These can be obtained from your ISP, or from the settings in the wireless router. And they are added to /etc/resolv.conf in the format "nameserver xxx.xxx.xxx.xxx", by adding DNS1=xxx.xxx.xxx.xxx to file /etc/sysconfig/network-scripts/ifcfg-eth0:1 (or whatever file as appropriate).

I'll probably struggle to do this a third time, so have to avoid rebuilding my machines...