Using a Private GIT Repo with Buildroot

Buildroot is pure awesomeness for maintaining the build of a GNU/Linux based operating system.  However, during my ventures I’ve had to keep private code private so use a git repo behind ssh.  There is a way to achieve this with Buildroot but it is undocumented:

LIBFOO_SITE_METHOD = git
LIBFOO_SITE = ssh://[email protected]/group/repo.git
LIBFOO_VERSION = v1.01.a

On the first line we have to set the method to git as the auto detect won’t work on SSH
The second line contains the git repo as it would be defined if using git via ssh accept prepended with ssh:// and the the colon that is normally between the end of the FQDN and the location is replaced with a slash.
Line 3 can be a tag, branch or commit hash.

[Read More]

Booting UrBackup over the local network (PXE)

With an already functioning TFTP server and PXE boot environment for Debian 7 network install with files also being served over http from the same path as the TFTP server it is straightforward to boot UrBackup over the network.  The same method applies to many Linux live cds.

Adding to pxelinux.cfg/default

Add the following to your default fiile in pxelinux.cfg

LABEL URbackup
    Menu Label ^UrBackup
    kernel vmlinuz append initrd\=initrd.img boot\=live config username\=urbackup toram fetch\=http://tftp/urbackup/filesystem.squashfs

Ensure you change the hostname to the ip or host of your tftp server and that you are serving the squashfs file over http.  Note that the initrd and vmlinuz are from the debian network boot sources.

[Read More]

Putting Jira behind a HTTP Proxy

If you run Jira behind a http proxy, namely https (ssl) then you need to add three options to the server.xml file in /opt/atlassian/jira/conf:

scheme=“https”
proxyName=“sub.domain.tld”
proxyPort=“443”

The only change needed to vanilla Jira.  Then in something like nginx you have the line:

proxy_pass              http://192.168.1.123:8080;

Windows Server Launch Game

TheGame

If you played the Window Server Launch sweepstakes game you may be having trouble finding out who won. My final position was something like 160th, so I think I was in with a 1:50 chance of winning.  Not too bad.  Though because I’ve still not heard anything yet, and that it’s been 2 weeks since the game has finished, I don’t think I have won.

HOW CAN YOU FIND OUT WHO WON?

To request a list of winners who received a prize worth $25.00 or more, send email with the subject line “Windows Server 2012 Virtual Launch Winners” to [email protected] by October 30, 2012.

[Read More]

Testing unattended windows installations

If you are creating unattended.xml files to use to perform automated installations of windows then you will at some point want to test it.  This is fine if the destination system has a keyboard and monitor but in my case the system I am targeting does not, a HP MediaSmart EX490.

The simplest way I found on Windows 8 to do the testing was to use the Hyper-V role.  Normally I prepare a USB stick with the Microsoft USB/DVD Download Tool and then copy the autounattend.xml file to the root of the USB disk.  However, during installation Windows will search for an autounattend.xml or unattend.xml on other removable devices.  Using this we can setup a Hyper-V VM with two DVD drives.  One with the installation media in the other with just the autounattend.xml

[Read More]

Setting up Visual Studio 2008 Remote Debugger on Windows Home Server

First get the download for your Windows Home Server – You will most likely need the x86 installation:

http://www.microsoft.com/downloads/details.aspx?FamilyID=440ec902-3260-4cdc-b11a-6a9070a2aaab&displaylang=en

Run the installer:

Hit next and accept the agreement after reading it.

Click on Finish once the installation is complete. The the configuration wizard will run:

I run my development and test Windows Home Server in a Virtual Machine so I’m happy to install the remote debugger component to run as a service whenever the VM is on.  If you want this to happen too then tick the checkbox and then enter the Administrator username and password:

[Read More]