<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>the blog of Chris &#187; boot</title>
	<atom:link href="http://blog.christophersmart.com/tag/boot/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.christophersmart.com</link>
	<description>Fortiter Et Recte</description>
	<lastBuildDate>Wed, 28 Dec 2011 23:39:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>How to triple boot Mac Pro with OS X, Fedora, Windows</title>
		<link>http://blog.christophersmart.com/2009/12/02/how-to-triple-boot-mac-pro-with-os-x-fedora-windows/</link>
		<comments>http://blog.christophersmart.com/2009/12/02/how-to-triple-boot-mac-pro-with-os-x-fedora-windows/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 04:42:19 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Fedora]]></category>
		<category><![CDATA[FOSS]]></category>
		<category><![CDATA[boot]]></category>
		<category><![CDATA[efi]]></category>
		<category><![CDATA[fedora]]></category>
		<category><![CDATA[gpt]]></category>
		<category><![CDATA[intel]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[mbr]]></category>
		<category><![CDATA[os x]]></category>
		<category><![CDATA[osx]]></category>
		<category><![CDATA[triple]]></category>
		<category><![CDATA[Windows]]></category>

		<guid isPermaLink="false">http://blog.christophersmart.com/?p=1607</guid>
		<description><![CDATA[Here are some step by step instructions on how to triple boot a Mac Pro (and I guess any Intel based Mac) with OS X (Snow Leopard), Fedora 12 and Windows XP. I ran into trouble because of the Fedora 12 installer being clever and setting my Fedora partition to be bootable, which didn&#8217;t play [...]]]></description>
			<content:encoded><![CDATA[<p>Here are some step by step instructions on how to triple boot a Mac Pro (and I guess any Intel based Mac) with OS X (Snow Leopard), Fedora 12 and Windows XP. I ran into trouble because of the Fedora 12 installer being clever and setting my Fedora partition to be bootable, which <a href="http://blog.christophersmart.com/2009/12/02/fedora-mac-and-efi/">didn&#8217;t play nice with the MBR table and Windows</a>.</p>
<p>Firstly, the Mac Pro I am using has a 500GB SATA drive, so the partition sizes that I choose reflect that fact. Your machine might be different, so adjust accordingly.</p>
<p><strong>Step 1</strong><br />
Install OS X on single partition using the whole drive (insert DVD and boot with C key held down).</p>
<p><strong>Step 2</strong><br />
Use the diskutil terminal command to resize the OS X partition and create one for Linux and Windows.</p>
<p>Open &#8220;Terminal&#8221; and then run:<br />
<code>sudo diskutil resizeVolume disk0s2 200G "MS-DOS" "Linux" 200G "MS-DOS" "Windows" 5G</code><br />
(Note that the final number for the Windows drive doesn&#8217;t really matter, it will fill all remaining available space.)</p>
<p><strong>Step 3</strong><br />
Under OS X, install <a href="http://refit.sourceforge.net">rEFIt</a> (a graphical EFI boot loader) and then bless the drive:<br />
<code>sudo /efi/refit/enable-always.sh</code></p>
<p><strong>Step 4</strong><br />
Insert Fedora 12 disk and reboot, holding down the C key (or boot it from the Linux CD entry in rEFIt menu).<br />
(Note: I had to install via FTP, because installing from DVD didn&#8217;t always work on my Mac Pro. If you have the same issue then at the boot menu hit the &#8220;Tab&#8221; key and add &#8220;askmethod&#8221; to the kernel line and boot the entry.)</p>
<p><strong>Step 5</strong><br />
During the installer, select the 3rd partition for / (choose &#8220;Custom&#8221; partition), format ext4.</p>
<p>Next, switch to terminal 2 (CTRL+Alt+2) and toggle boot to <em>off</em> for the Linux partition, like so:<br />
<code>  parted /dev/sda<br />
  toggle 3 boot<br />
  quit</code></p>
<p>Now sync the GPT and MBR partition tables:<br />
<code>  gptsync /dev/sda</code><br />
(Or you can do this step via rEFIt menu after the install if you prefer.)</p>
<p>Switch back to terminal 6 (Alt+6) and continue. Install the boot loader to /dev/sda3 (this is the default).</p>
<p>Complete Fedora install, reboot into OS X, eject disk, insert Windows XP install CD.</p>
<p>For reference, the GPT partition table should look something like this:<br />
<code><br />
<blockquote>[chris@localhost ~]$ sudo parted -l</p>
<p>Model: ATA ST3500630AS P (scsi)<br />
Disk /dev/sda: 500GB<br />
Sector size (logical/physical): 512B/512B<br />
Partition Table: gpt</p>
<p>Number  Start   End    Size    File system  Name                  Flags<br />
 1      20.5kB  210MB  210MB   fat32        EFI System Partition  boot<br />
 2      210MB   200GB  200GB   hfs+         OS X<br />
 3      200GB   400GB  200GB   ext4         Linux<br />
 4      400GB   500GB  99.9GB  ntfs         Windows</p></blockquote>
<p></code></p>
<p>While the MBR table should look like this:<br />
<code><br />
<blockquote>[chris@localhost ~]$ sudo fdisk -l</p>
<p>WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.</p>
<p>Disk /dev/sda: 500.1 GB, 500107862016 bytes<br />
255 heads, 63 sectors/track, 60801 cylinders<br />
Units = cylinders of 16065 * 512 = 8225280 bytes<br />
Disk identifier: 0xcce7cce7</p>
<p>   Device Boot      Start         End      Blocks   Id  System<br />
/dev/sda1               1          26      204819+  ee  GPT<br />
/dev/sda2              26       24325   195181428   af  HFS / HFS+<br />
/dev/sda3   *       24341       48656   195311616   83  Linux<br />
/dev/sda4           48657       60802    97556480    7  HPFS/NTFS</p></blockquote>
<p></code></p>
<p><strong>Step 6</strong><br />
Reboot, holding down C key (or choose the Windows CD entry from rEFIt menu), install Windows XP to 4th partition, format NTFS.<br />
If the Windows installer sees a single partition and can&#8217;t detect the file system, re-sync the GPT and MBR partition tables via rEFIt or Fedora gptsync command. Also, ensure that the Fedora partition is not set to be bootable (Step 5, part 2). The installer should see multiple drive letters, with the 4th partition being the C drive. Yes, Windows has to be installed on the last partition.</p>
<p>After install, the rEFIt menu should see Windows on the hard drive. Boot it and continue your Windows install. Once installed, insert the OS X Snow Leopard DVD and install the system drivers, etc.</p>
<p>That&#8217;s about it.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.christophersmart.com/2009/12/02/how-to-triple-boot-mac-pro-with-os-x-fedora-windows/feed/</wfw:commentRss>
		<slash:comments>55</slash:comments>
		</item>
		<item>
		<title>Fedora, Macs and EFI</title>
		<link>http://blog.christophersmart.com/2009/12/02/fedora-mac-and-efi/</link>
		<comments>http://blog.christophersmart.com/2009/12/02/fedora-mac-and-efi/#comments</comments>
		<pubDate>Tue, 01 Dec 2009 22:18:40 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Fedora]]></category>
		<category><![CDATA[FOSS]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[boot]]></category>
		<category><![CDATA[efi]]></category>
		<category><![CDATA[fedora]]></category>
		<category><![CDATA[gptsync]]></category>
		<category><![CDATA[mac]]></category>
		<category><![CDATA[mbr]]></category>
		<category><![CDATA[os x]]></category>
		<category><![CDATA[parted]]></category>

		<guid isPermaLink="false">http://blog.christophersmart.com/?p=1599</guid>
		<description><![CDATA[When installing Linux beside OS X, Fedora toggles the boot flag on for its partition. This causes GPT to see it as an &#8220;EFI boot partition,&#8221; rather than &#8220;Basic Data&#8221;. This appears to cause a problem if you want to triple boot with Windows and under OS X the disk utility will see it as [...]]]></description>
			<content:encoded><![CDATA[<p>When installing Linux beside OS X, Fedora toggles the boot flag on for its partition. This causes GPT to see it as an &#8220;EFI boot partition,&#8221; rather than &#8220;Basic Data&#8221;. This appears to cause a problem if you want to triple boot with Windows and under OS X the disk utility will see it as one whole partition, with the Linux half missing.</p>
<p>To fix this, toggle the boot flag to off using parted and then sync the GPT partition table to the master boot record partition table. It&#8217;s easiest to do this while the installer&#8217;s running (switch to TTY2) else you&#8217;ll have to install anaconda under your install to get <code>gptsync</code> (or run it from the rEFIt menu).</p>
<p>Simply run the following:<br />
<code>parted /dev/sda<br />
toggle 3 boot<br />
quit<br />
gptsync /dev/sda</code></p>
<p>The gptsync command should spit out the &#8220;Current GPT partition table&#8221; which should show something like:<br />
<code>EFI System (FAT)<br />
Mac OS X HFS+<br />
Basic Data<br />
Basic Data (if you have a fourth partition for Windows)</code></p>
<p>The &#8220;Proposed new MBR partition table&#8221; should show something like:<br />
<code>EFI Protective<br />
Mac OS X HFS+<br />
Linux<br />
FAT32 (LBA) (or NTFS, depending if it's already been formated)</code></p>
<p>Now Windows should install cleanly on the fourth partition (if you&#8217;re doing that) and the partition structure under OS X should be correct.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.christophersmart.com/2009/12/02/fedora-mac-and-efi/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>More jackalope than jaunty</title>
		<link>http://blog.christophersmart.com/2009/08/18/more-jackalope-than-jaunty/</link>
		<comments>http://blog.christophersmart.com/2009/08/18/more-jackalope-than-jaunty/#comments</comments>
		<pubDate>Tue, 18 Aug 2009 06:00:14 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[FOSS]]></category>
		<category><![CDATA[aacraid]]></category>
		<category><![CDATA[boot]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[raid]]></category>
		<category><![CDATA[root]]></category>
		<category><![CDATA[server]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[x3650]]></category>

		<guid isPermaLink="false">http://blog.christophersmart.com/?p=1114</guid>
		<description><![CDATA[We have some IBM x3650 servers at work with Adaptec 8k ServeRAID controller cards and SAS drives. For the life of me I can&#8217;t get Jaunty to boot on the machines. It installs just fine, but the initial reboot fails to find the root device and drops me to an &#8220;ash&#8221; shell which doesn&#8217;t ever [...]]]></description>
			<content:encoded><![CDATA[<p>We have some IBM x3650 servers at work with Adaptec 8k ServeRAID controller cards and SAS drives.</p>
<p>For the life of me I can&#8217;t get Jaunty to boot on the machines. It installs just fine, but the initial reboot fails to find the root device and drops me to an &#8220;ash&#8221; shell which doesn&#8217;t ever actually appear. The keyboard also doesn&#8217;t work.</p>
<p>It doesn&#8217;t matter what RAID array I have, whether I&#8217;m using LVM or a standard partitioning scheme with an msdos partition table.. it just doesn&#8217;t work.</p>
<p>I&#8217;ve added aacraid and several other modules to the initramfs, still no joy.</p>
<p>Add the fact that the machine takes 10 minutes to boot each time I want to test a small change and it&#8217;s one <em>super frustrating </em>situation.</p>
<p>Oh, and 8.04 LTS works just fine.</p>
<p>One bug which appears to be a <a href="https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/131919">grub issue that I don&#8217;t have</a>, which hasn&#8217;t been touched since April. There&#8217;s another about being <a href="https://bugs.launchpad.net/ubuntu/+source/linux/+bug/294747">unable to find the root device</a> that also hasn&#8217;t received any love.</p>
<p>If anyone has some suggestions (install Debian?), let me know. The reason I&#8217;m using Ubuntu is because we have a local mirror and Jaunty because it&#8217;s a virtual machine and KVM is the way I want to go.</p>
<p><strong>Update:</strong> Ahh, problem resolved and it was my fault. See comments..</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.christophersmart.com/2009/08/18/more-jackalope-than-jaunty/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Linux on an Apple Xserve EFI only machine</title>
		<link>http://blog.christophersmart.com/2009/07/23/linux-on-an-apple-xserve-efi-only-machine/</link>
		<comments>http://blog.christophersmart.com/2009/07/23/linux-on-an-apple-xserve-efi-only-machine/#comments</comments>
		<pubDate>Thu, 23 Jul 2009 06:53:48 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[Fedora]]></category>
		<category><![CDATA[FOSS]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[boot]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[efi]]></category>
		<category><![CDATA[fedora]]></category>
		<category><![CDATA[grub]]></category>
		<category><![CDATA[install]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[loader]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[xserve]]></category>

		<guid isPermaLink="false">http://blog.christophersmart.com/?p=1005</guid>
		<description><![CDATA[We have a few of these Apple Xserve machines at work which weren&#8217;t doing much, so I thought I&#8217;d make better use of them. Naturally, this meant installing Linux on them. These machines do not have a BIOS (or even any emulation), they use EFI and as such won&#8217;t boot the standard Linux install media. [...]]]></description>
			<content:encoded><![CDATA[<p>We have a few of these <a href="http://www.apple.com/au/xserve/">Apple Xserve machines</a> at work which weren&#8217;t doing much, so I thought I&#8217;d make better use of them. Naturally, this meant installing Linux on them.</p>
<p>These machines do not have a BIOS (or even any emulation), they use EFI and as such won&#8217;t boot the standard Linux install media. I knew that Fedora could boot EFI, so that&#8217;s where I started, with Leonidas (version 11). Unfortunately, the install media just wouldn&#8217;t work on this device, presumably as it has no BIOS emulation.</p>
<p>To cut a long story short, I had to <a href="http://homepages.tesco.net/~J.deBoynePollard/FGA/efi-boot-process.html">learn how EFI works</a> in order to get it booting and it wasn&#8217;t an easy thing to discover!</p>
<p><span id="more-1005"></span></p>
<p><strong>Booting EFI</strong><br />
In short, the Apple EFI boots and scans all available drives (including USB drives) for a GPT partitioned device which has a FAT formatted partition on it. Inside this partition it looks for an <code>efi</code> directory.</p>
<p>In that directory must be another from the <a href="http://www.uefi.org/specs/esp_registry">list of approved vendor named directories</a>, such as <code>redhat</code> or <code>apple</code>. The default is <code>boot</code> and this is what I used.</p>
<p>Inside that <code>boot</code> directory, EFI looks for a binary EFI file, which it can run. In my case, this is a GRUB2 EFI binary. The name of the file must match your architecture, so for me it is called <code>bootia32.efi</code> but if you&#8217;re running a 64bit system it should be <code>bootx64.efi</code>.<br />
<strong>NOTE:</strong> Your Mac <a href="http://blog.christophersmart.com/2009/12/22/does-your-mac-have-64bit-efi/">must have a 64bit EFI</a> to load the 64bit EFI Linux installer (bootx64.efi)). Else, try choosing the 64bit options when using the 32bit EFI installer (bootia32.efi), but either way your system must have a 64bit CPU.</p>
<p>The GRUB2 EFI binary I am using looks for the standard GRUB config file, which is called <code>grub.cfg</code>. This must also be in the efi/boot/ directory of the USB device. The kernel and initramfs for the net installer should also be in that directory.</p>
<p>I have made a Debian Squeeze, Fedora Constantine and Ubuntu Karmic installer <a href="http://christophersmart.com/files/efi-grub.tar.bz2">which you can download</a> and extract onto your USB device (<a href="http://christophersmart.com/files/efi-grub.tar.bz2.sha1">sha1sum</a>). You will still need to partition and format your device, so more on how to do that later.</p>
<p><strong>Partition USB Boot Device</strong><br />
So, once we understand how EFI works, next we need to get a bootable GRUB happening in order to install Linux.</p>
<p>Grab a USB memory stick and let&#8217;s prepare it. Please know what device it is you&#8217;re partitioning!! I&#8217;ll use sdz just for example purposes only.<br />
Unmount it<br />
<code>su -c 'umount /dev/sdz1'</code></p>
<p>Partition and format it<br />
<code>Partition and format it<br />
<code>su -c 'parted -s /dev/sdz mklabel gpt mkpartfs EFI fat32 0% 100% toggle 1 boot'</code></code></p>
<p>It should now automatically mount. If not, unplug it and plug it in again, or mount it manually.</p>
<p><strong>Prepare USB Boot Device</strong><br />
Next you can extract my tarball onto the device, ensuring that it maintains the efi/boot/ directory structure on it and not create an extra directories because of the archiver. If it&#8217;s not right, then re-arrange things and eject the device.</p>
<p>You should now be able to plug it into your Xserve and turn it on.</p>
<p>Hold down the Option key (Alt key on non-Apple keyboards) until you see the boot option. It should show &#8220;EFI&#8221; on the usb stick. Boot this and you should see the GRUB menu load. Choose the distro you want to install and away you go! See the &#8220;Installation&#8221; section below and skip the next few.</p>
<p><strong>Manual preparation &#8211; Building GRUB2</strong><br />
Before we can compile GRUB, we need some dependencies. If you&#8217;re using Debian or Ubuntu, then run the following:<br />
<code>sudo apt-get build-dep grub2<br />
sudo apt-get install libusb-dev</code></p>
<p>We need to check out GRUB from CVS and <a href="http://grub.enbug.org/TestingOnEFI">build it for EFI systems</a>. Note, my Xserve is 32bit only, so I&#8217;m installing 32bit version. If you&#8217;re using 64bit then use a 64bit OS. You can cross compile, see the link above for info if you need to.</p>
<p>Check out source from CVS:<br />
<code>cvs -z3 \<br />
-d:pserver:anonymous@cvs.savannah.gnu.org:/sources/grub \<br />
co grub2<br />
cd grub2</code></p>
<p>Or get source from Debian (which is more likely to compile):<br />
<code>apt-get source grub2<br />
cd grub2*<br />
</code></p>
<p>Build grub2:<br />
<code>./configure --with-platform=efi<br />
make</code></p>
<p>Now, make a temporary directory in which to put the GRUB EFI binary.<br />
<code>mkdir -p efi/boot/</code></p>
<p>Next we need to create the GRUB2 EFI program, and will specify a bunch of modules to include. This was a big stumbling block for me because someone removed the ability to read config files from module &#8220;configfile&#8221; and put it into &#8220;minicmd&#8221; requiring &#8220;sh&#8221;. The documentation I was following was not updated and I couldn&#8217;t work out why GRUB2 couldn&#8217;t parse my config (typing it in manually at the GRUB2 command prompt worked however). After lots of wasted time I emailed the GRUB list and had an answer within 20 minutes, which was a big relief.</p>
<p><code>./grub-mkimage -d . -o bootia32.efi part_gpt hfsplus fat ext2 normal sh chain boot configfile minicmd linux loadbios reboot appleldr halt search<br />
sudo cp bootia32.efi efi/boot/</code></p>
<p>The efi/ directory now just needs to be copied onto your FAT USB stick. Don&#8217;t forget to make sure the directory structure is correct, as laid out above.</p>
<p>Now you just need to create a GRUB2 config file, which we&#8217;ll do below after getting the kernel and initramfs.</p>
<p><strong>Manual preparation &#8211; Linux installers</strong><br />
I am using the netboot installers for each distro. This basically consists of a kernel, initramfs (which includes the installer). To know how to boot these in the GRUB config file, I read the isolinux configs included on the install CDs.</p>
<p>So, download the network installer of your choice in ISO format. Mount loop it and copy the kernel and initramfs onto the efi/boot/ directory on your USB disk.</p>
<p>For example (32bit), <a href="ftp://mirror.internode.on.net/ubuntu/dists/karmic/main/installer-i386/current/images/netboot/mini.iso">Ubuntu</a>, <a href="ftp://mirror.internode.on.net/pub/fedora/linux/releases/12/Fedora/i386/os/images/boot.iso">Fedora</a>, <a href="ftp://mirror.internode.on.net/debian/dists/squeeze/main/installer-i386/current/images/netboot/mini.iso">Debian Squeeze</a> (note that Fedora does actually have an <a href="ftp://mirror.internode.on.net/pub/fedora/linux/releases/11/Fedora/i386/os/images/efidisk.img">EFI boot disk</a> which you can dd directly to a USB stick and boot, however this didn&#8217;t work on my Xserve but it might be useful to grab the kernel and initramfs from as it&#8217;s smaller).</p>
<p>Mount loop ISO:<br />
<code>mkdir /tmp/iso<br />
sudo mount -o loop boot.iso /tmp/iso</code></p>
<p>Copy the kernel and initramfs from /tmp/iso onto your USB stick. You might need to look at the isolinux.cfg files under /tmp/iso in order to find out which is the kernel. On Debian and Ubuntu the kernel is called <code>linux</code> and the initramfs is called <code>initrd.gz</code>, both in the root directory.</p>
<p><strong>GRUB Config File</strong><br />
Now that you have the GRUB2 EFI binary (bootia32.efi), kernel and initramfs on the USB stick, we need a config file for GRUB to read when it loads.</p>
<p>Here is an example for all four distros that I use in my provided tarball.<br />
<code>set timeout=10<br />
set default=0<br />
menuentry "Debian Squeeze" {<br />
   linux /efi/boot/linux-squeeze priority=low vga=normal video=efifb<br />
   initrd /efi/boot/initrd-squeeze.gz<br />
}<br />
menuentry "Fedora Leonidas" {<br />
  linux /efi/boot/vmlinuz-leonidas nomodeset xdriver=fbdev noselinux<br />
   initrd /efi/boot/initrd-leonidas.img<br />
}<br />
menuentry "Ubuntu Jaunty" {<br />
   linux /efi/boot/linux-jaunty priority=low vga=normal video=efifb<br />
   initrd /efi/boot/initrd-jaunty.gz<br />
}<br />
menuentry "Ubuntu Karmic" {<br />
   linux /efi/boot/linux-karmic priority=low vga=normal video=efifb<br />
   initrd /efi/boot/initrd-karmic.gz<br />
}</code></p>
<p>Note that for Fedora I had to turn kernel based mode-setting <strong>off</strong>, and specify the Xserver driver.</p>
<p>The USB keyboard just wouldn&#8217;t work on either Ubuntu, but Debian Squeeze worked fine. I ended up choosing Fedora.</p>
<p><strong>Manual preparation &#8211; Install Linux</strong><br />
Once you have all the required files, plug the stick in and turn on the Xserve. Hold down the Option key (Alt key on non-Apple keyboards) until you see the boot option. It should show &#8220;EFI&#8221; on the usb stick. Boot this and you should see the GRUB menu load where you can boot your network installer of choice.</p>
<p><strong>Installation</strong><br />
When installing, you need to follow the same partition structure as the USB stick. I completely blew away all Apple partitions and am booting only Linux. The <strong>drives need to be GPT</strong> and to have a <strong>small FAT partition at the beginning</strong> with the efi/boot/ directory, GRUB2 EFI binary, GRUB config, kernel and initramfs.</p>
<p>There&#8217;s probably a better way to do this, I&#8217;m sure some distros will support GRUB2 and EFI out of the box soon. In the mean time I install the OS without a boot loader and create the efi/boot/ system manually. This means every time you update your kernel, you need to copy the kernel and initramfs, and update the GRUB config file.</p>
<p>The config file should be the same as the one used on the USB stick, except that the names of the kernel and initramfs will be different. For example:</p>
<p><code>set timeout=10<br />
set default=0<br />
menuentry "Fedora Leonidas" {<br />
  linux /efi/boot/vmlinuz-2.6.28-13-generic nomodeset xdriver=fbdev noselinux root=/dev/sda3 ro<br />
   initrd /efi/boot/initrd.img-2.6.28-13-generic<br />
}</code></p>
<p><strong>Conclusion</strong><br />
These are some rough notes to hopefully help others out there trying similar things. Please let me know how it works for you. I installed Fedora on my Xserve and it&#8217;s running quite well!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.christophersmart.com/2009/07/23/linux-on-an-apple-xserve-efi-only-machine/feed/</wfw:commentRss>
		<slash:comments>132</slash:comments>
		</item>
		<item>
		<title>Bootology [bōōt-ol-uh-jee] -noun. The art of booting Linux</title>
		<link>http://blog.christophersmart.com/2008/10/01/bootology-boot-ol-uh-jee-noun-the-art-of-booting-linux/</link>
		<comments>http://blog.christophersmart.com/2008/10/01/bootology-boot-ol-uh-jee-noun-the-art-of-booting-linux/#comments</comments>
		<pubDate>Wed, 01 Oct 2008 02:29:01 +0000</pubDate>
		<dc:creator>Chris</dc:creator>
				<category><![CDATA[FOSS]]></category>
		<category><![CDATA[boot]]></category>
		<category><![CDATA[Linux]]></category>

		<guid isPermaLink="false">http://blog.christophersmart.com/?p=166</guid>
		<description><![CDATA[I just came across bootchart, a tool for &#8220;performance analysis and visualization of the GNU/Linux boot process&#8221;. Ever wondered what was causing that big delay in bootup? Install bootchart and check! I installed bootchart on my openSUSE box at work with sudo zypper in bootchart, rebooted and edited grub on the fly, adding init=/sbin/bootchartd to [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://christophersmart.com/images/bootchart-opensuse11-lrg.png"><img src="http://christophersmart.com/images/bootchart-opensuse11-sml.png" align=left border="1" alt="Bootchart openSUSE 11.0" /></a>I just came across <a target="_blank" href="http://bootshart.org">bootchart</a>, a tool for &#8220;performance analysis and visualization of the GNU/Linux boot process&#8221;.</p>
<p>Ever wondered what was causing that big delay in bootup? Install bootchart and check!</p>
<p>I installed bootchart on my openSUSE box at work with <font color=green><em>sudo zypper in bootchart</em></font>, rebooted and edited grub on the fly, adding <font color=green><em>init=/sbin/bootchartd</em></font> to the kernel line.</p>
<p>After your system has loaded, bootchart creates a log of the process which you can then turn into a chart with the command <font color=green><em>bootchart</em></font>. You can also specify the log location if required, or change the output format of the chart from PNG to SVG or EPS.</p>
<p>Of course, what you do with this information is up to you <img src='http://blog.christophersmart.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  Happy hacking.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.christophersmart.com/2008/10/01/bootology-boot-ol-uh-jee-noun-the-art-of-booting-linux/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

