Using the Remote Registry Editor supplied with Visual Studio and with the Windows Mobile SDK installed change the following key value from 0 to 1 (and vise-versa to reset the change)

HKEY_LOCAL_MACHINE\Security\Policies\Policies\0000101a = 1

That’s it.

The solution is to go into the Properties of each connection (right click on it) –> select Internet Protocol (TCP/IP) –> click Properties -> click Advanced –> uncheck Automatic metric in the bottom and set a number between 1 and 9999 where the smaller the number the higher the connection priority. I have set my Wireless Internet connection to 1 and my LAN connection to 9999 and that works.

I hope this post will save someone else’s precious time in the future.

1. Create a new VirtualBox HDD with the desired size and add it as a secondary HDD (Primary Slave) in the Virtual Machine HDD settings.

2. Download the GParted LiveCD and boot from it inside the Guest – http://gparted.sourceforge.net/

3. Right click on the partitions of the original HDD in GParted and click “Copy“. Select the second HDD and “Paste”.  This will ask to create a “msdos” partition table first so click “OK” and “Paste” again. Adjust partition sizes as you wish and hit “Apply“.

4. Mark the new partition as bootable in right click -> “Manage Flags” -> tick “boot“. Once done shutdown the VM and release the gparted Live CD.

5. Because the HDD characteristics have changed you might not be able to boot at this point. Insert the Windows/Linux OS installation CD/DVD and run in repair mode. For Windows this would be the recovery console and the “fixboot c:” or fixmbr commands. On Linux just reinstall the boot loader.

That’s it. It’s not very convenient doing this but at least it works.

P.S: If you get an error “FATAL: INT18 Boot Failure” you have forgotten to mark the new partition as bootable.

1) Install git-merge-changelog which is part of gnulib . For openSUSE you can use my repository at http://download.opensuse.org/repositories/home:/i-nZ/

2) Make Git aware of it by adding the following to your ~/.gitconfig

[merge "merge-changelog"]
name = GNU-style ChangeLog merge driver
driver = /usr/bin/git-merge-changelog %O %A %B

3) For each repository where you want to use this driver make Git aware of it by adding to $GIT_REPO/.git/info/attributes the following (create the file if it doesn’t exist):

ChangeLog    merge=merge-changelog

That’s it! Enjoy.

You are using Git and git-svn on a big project which has lots of branches and tags but you only need to work with a small selection of those and you don’t want to import all of the rest.

Import an individual SVN branch

1) Define the new branch in .git/config :

[svn-remote "release-branch"]
        url = svn+ssh://xxxx@mono-cvs.ximian.com/source/branches/mono-2-2/mcs
        fetch = :refs/remotes/git-svn-release-branch

2) Import the SVN branch. SVN_BRANCHED_REVISION is the the revision when the branch happened in SVN.

[~]$ git svn fetch release-branch -r SVN_BRANCHED_REVISION

3) Hook up a local Git branch to the remote branch:

[~]$ git branch --track release git-svn-release-branch

5) Checkout and update

[~]$ git checkout release
[~]$ git svn rebase

Done!

Delete the branch checkout

The following command sequence will delete (locally only) the SVN branch and its history:

[~]$ git branch -D release
[~]$ git branch -D -r git-svn-release-branch
[~]$ rm -rf .git/svn/git-svn-release-branch
[~]$ git gc

Now what?

Well, for starters given that you are ready to commit something to trunk and you also want to “backport” to the release branch you just have to do:

[~]$ git svn dcommit
[~]$ git checkout release && git svn rebase
[~]$ git cherry-pick master && git svn dcommit
[~]$ git checkout master

[Dialer nokia-usb]
Modem = /dev/ttyACM0
Baud = 3600000
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2
Init3 =
Modem Type = USB Modem
Area Code =
Phone = *99#
Username = ppp
Password = ppp
Ask Password = 0
Dial Command = ATDT
Stupid Mode = 1
Compuserve = 0
Force Address =
Idle Seconds = 0
DialMessage1 =
DialMessage2 =
ISDN = 0
Auto DNS = 1
New PPPD = yes

[Dialer nokia-bluetooth]
Modem = /dev/rfcomm0
Baud = 3600000
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2
Init3 =
Area Code =
Phone = *99#
Username = ppp
Password = ppp
Ask Password = 0
Dial Command = ATDT
Stupid Mode = 1
Compuserve = 0
Force Address =
Idle Seconds = 0
DialMessage1 =
DialMessage2 =
ISDN = 0
Auto DNS = 1
New PPPD = yes

3.) For USB when you connect the phone set it to “PC Suite” mode (else the modem won’t appear) and then:

su -c "wvdial nokia-usb"

4.) For Bluetooth, where ### is the Bluetooth Address of you phone

su -c "rfcomm release 0; rfcomm bind 0 ### `sdptool search \
--bdaddr=### dun | grep -i Channel | cut -c14-14` && wvdial nokia-bluetooth"

5.) Workaround for broken newer versions of NetworkManager where the DNS won’t be set properly can be found at http://seife.kernalert.de/blog/2008/12/11/using-dialup-with-111-if-networkmanager-does-not-handle-your-device/

In this HowTo I will cover how to configure a triple boot Apple Mac machine to boot openSUSE, Windows Vista and Mac OS X.

The Problems

Apple Macs are EFI systems and as such they do not have BIOS. Even though EFI does support the standard partition scheme (MBR), Apple is using the added support for a GUID partition table (GPT). GPT has a limit of 4 partitions and 1 is already used.

Linux supports the GPT and can boot by using elilo as a bootloader. However the lack of BIOS will not allow the video card drivers to operate properly.

Windows doesn’t support GPT.

The Solutions

Video

Apple has updated the firmware to allow emulation of BIOS for its Boot Camp tool to work. It should be noted that while Boot Camp offers an easy way to set up a dual boot Windows/OS X machine it does not come in handy for the purpose of this HowTo.

Partitioning

While GPT is a new scheme, it doesn’t fully replace the MBR, but rather keeps it in the beginning for compatibility reasons. Fortunately one can abuse that and create a MBR partitioning table to match the GPT one. It is very important that the MBR partioning table is kept in sync with the GPT one, because else it will provide false information for the actual physical layout to the software reading it.

Since there are only 3 free GPT partition table slots one can install the three OSes. Linux works just fine with swap on a file in /.

Booting and MBR/GPT syncing

There is an awesome tool available called rEFIt. It includes is not only a boot loader, but also has a built in MBR/GPT partition synchronization tool. It automatically recognizes bootable OSes by scanning the partitions (also scans external devices).

The HowTo

Partitioning

Boot from your Mac OS X CD 1 and use Disk Utility from the menu on top to create one partition for Mac OS X, one Unix type partition and one FAT32 type partition. It appears that it is crucial to have the Windows partition as the last one, else Vista will complain and won’t even install and Windows XP will install, but will throw missing hal.dll error and won’t boot.

Install Mac OS X

Install Mac OS X and update it to the latest version. Reboot and install rEFIt. Reboot and use the sync tool (called “Partition Tool” in the menu) in the rEFIt menu to sync MBR to GPT.

Install Windows Vista (setup NTFS partition)

In Vista’s setup select the FAT32 partition, format it and install there. After the first reboot during the installation use rEFIt sync tool again. This is just to get the NTFS partition in place. Do not finish off the installation now, but rather procceed to the Linux installation. Windows won’t be able to boot after the sync anyway.

Install Linux (openSUSE)

Crucial elements during the installation of openSUSE before the first reboot:

• Install Linux (yes, everything) on the single UNIX type partition. Use custom partitioning to format the UNIX type partition to ext3 and set mount point to /. Do not create a swap partition and do not even think about resizing partitions.
• Set the boot loader to LILO, because GRUB will fail to install.
• Install the boot loader in the boot record for the partition. REFIt can boot it fine and also the master boot record will be free for Windows later on.
• Remove the Windows entry from the lilo menu, because it causes LILO’s installation to fail.

Unfortunatly for unknown reasons to me after the first reboot during the installation the MBR partitioning table will be gone, so one has to use rEFIt to resync GPT and MBR. This of course will break lilo’s previous setup, so we have to reinstall it before continuing the installation. This can be done by boot from the openSUSE cd/dvd again and once the setup has loaded Ctrl + Fx to a terminal. From that point on we have to mount the partition where we have Linux installed and rerun lilo:

mkdir /media/suse;
mount /dev/sda3 /media/suse
mount --bind /dev /media/suse/dev
chroot /media/suse
lilo -v

Reboot and resync GPT/MBR once more (so that rEFIT sets proper partition types) and then reboot for the last time. You should see OS X, Windows (won’t boot) and Linux icons in the rEFIt menu now. Select the Linux one and finish your openSUSE installation.

Install Windows Vista

Run the Windows Vista installation from the start (again by formatting the partition) to end now. Do not sync MBR/GPT after!

Additional Notes

parted, fdisk, Boot Camp

Do not use parted nor fdisk once you have a working system. I have had very bad experiences with both of those. As bad as in missing GPT and/or MBR partition table after. Do not use Boot Camp as well.

Linux swap on a file

It works fine and can be done as follows. Example sets 2gb swap.

dd if=/dev/zero of=/swap bs=1024 count=2097152
mkswap /swap
swapon /swap
echo "/swap swap swap pri=1 0 0" >> /etc/fstab

Linux Built-in iSight WebCam Driver

Here or possibly supplied by your distribution of choice as uvcvideo patched with my isight patch.

Apple Mac Windows Driver CD iso

After installing Boot Camp the driver cd image is here: /Applications/Utilities/Boot Camp Assistant.app/Contents/Resources/DiskImage.dmg.

Have fun!

The Preboot Execution Environment (in short PXE) is a protocol that enables a computer to be booted on the network. PXE is saved in ROM on newer network cards and, depending on the boot sequence configured in the computer’s BIOS, loaded and executed after turning on the computer.

This HOWTO describes how to setup an openSUSE 10.2 machine to act as a network boot and install server. I have used this method to install openSUSE 10.2 on my Tablet PC (Toshiba Portege M200).

The plan is to have a DHCP server assigning IPs, TFTP server for PXELINUX to be loaded (to load the openSUSE installer) and an NFS share to supply the installation files.

Prerequests

• PXE boot capable machine
• Packages – all of them can be found on the DVD or in the main openSUSE repository.
  • dhcp-server – to automatically asign IPs.
  • tftp – to share the boot image
  • syslinux – to supply the boot image (pxelinux.0)
  • yast2-tftp-server – Graphical configurator for a TFTP server
  • yast2-dhcp-server – Graphical configurator for a DHCP server
  • yast2-nfs-server – Graphical configurator for a NFS server.
• A network cable
• openSUSE 10.2 DVD

All of the graphical configurators used in this HOWTO can be found in Yast2 in the Network Services section.

[[Image:software/suse-netboot-screens/yast2-network-services.png|center|640|480]]

Network Interface Setup

For the purpose of this HOWTO I will set and use the IP 192.168.69.1 for the network interface. This can be configured in Yast in the Network Devices section using the Network Card configurator.

[[Image:software/suse-netboot-screens/card-setup-1.png|center|640|480]]

[[Image:software/suse-netboot-screens/card-setup-2.png|center|640|480]]

[[Image:software/suse-netboot-screens/card-setup-3.png|center|640|480]]

The last step is to bring the interface up:

ifconfig eth0 up 192.168.69.1

NFS Configuration

For the purpose of this HOWTO I am going to share the openSUSE 10.2 DVD as shown. This is going to be the installation source supplied for the installation as you will see later.

[[Image:software/suse-netboot-screens/nfs-1.png|center|640|480]]

[[Image:software/suse-netboot-screens/nfs-2.png|center|640|480]]

TFTP Configuration

Time to configure PXELINUX to be offered by the TFTP server.

[[Image:software/suse-netboot-screens/tftp.png|center|640|480]]

We will also tell PXELINUX to boot the linux kernel we will copy from the openSUSE 10.2 DVD.

cp /usr/share/syslinux/pxelinux.0 /tftpboot
cp /media/SU1020.001/boot/i386/loader/initrd /tftpboot/
cp /media/SU1020.001/boot/i386/loader/linux /tftpboot/
mkdir /tftpboot/pxelinux.cfg
cd /tftpboot/pxelinux.cfg
touch default
chmod 777 default

The boot configuration in the file default should be as follows:

default linux
label linux
kernel linux
append initrd=initrd install=nfs://192.168.69.1/media/SU1020.001
implicit         0
display         message
prompt          1
timeout         1

DHCPD Configuration

[[Image:software/suse-netboot-screens/dhcpd-1.png|center|640|480]]

[[Image:software/suse-netboot-screens/dhcpd-2.png|center|640|480]]

[[Image:software/suse-netboot-screens/dhcpd-3.png|center|640|480]]

[[Image:software/suse-netboot-screens/dhcpd-4.png|center|640|480]]

The configurator will create the /etc/dhcpd.conf file, but with this configuration the dhcp server won’t know about the existance of the tftp server, so we have to add 2 the next-server and filename options. Finally the configuration should look like this:

option domain-name "mydomainname";
ddns-update-style none;
   default-lease-time 14400;
   subnet 192.168.69.0 netmask 255.255.255.0 {
   range 192.168.69.2 192.168.69.254;
   default-lease-time 14400;
   max-lease-time 172800;
   next-server 192.168.69.1;
   filename "pxelinux.0";
}

[[Image:software/suse-netboot-screens/dhcpd-5.png|center|640|480]]

Booting

You can now boot the machine and the result should be something simliar to:

Trying to load: pxelinux.cfg/01-88-99-aa-bb-cc-dd
Trying to load: pxelinux.cfg/C000025B
Trying to load: pxelinux.cfg/C000025
...
Trying to load: pxelinux.cfg/default

and then the system should boot.

References and More Information

• ftp://download.intel.com/design/archives/wfm/downloads/pxespec.pdf
• http://en.wikipedia.org/wiki/Tftp
• http://en.wikipedia.org/wiki/Network_File_System_%28Sun%29
• http://en.opensuse.org/SDB:Network_Installation_of_SuSE_Linux_via_PXE_Boot
• http://syslinux.zytor.com/pxe.php

autoconf
automake
bison
gcc-mingw
gcc-mingw-g++
libtool
pkg-config
subversion
make

export MONO_LOCATION=/cygdrive/c/mono
export PATH=${PATH}:${MONO_LOCATION}/bin
export ACLOCAL_FLAGS="-I ${MONO_LOCATION}/share/aclocal"
export PKG_CONFIG_PATH=${PKG_CONFIG_PATH}:${MONO_LOCATION}/lib/pkgconfig
mkdir -p /mono/svn
mkdir /mono/build

cd /mono/svn
svn co svn://anonsvn.mono-project.com/source/trunk/mono
svn co svn://anonsvn.mono-project.com/source/trunk/mcs
cd mono
./autogen.sh --prefix=/mono/build
make
make install