<div class="gmail_quote">On Mon, Nov 29, 2010 at 3:12 AM, Tom H <<a href="mailto:tomh0665@gmail.com">tomh0665@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div class="im">On Sun, Nov 28, 2010 at 6:08 PM, Nathan Bahn <<a href="mailto:nathan.bahn@gmail.com">nathan.bahn@gmail.com</a>> wrote: > On Sun, Nov 28, 2010 at 5:41 AM, Tom H <<a href="mailto:tomh0665@gmail.com">tomh0665@gmail.com</a>> wrote: >> On Sat, Nov 27, 2010 at 10:20 PM, Nathan Bahn <<a href="mailto:nathan.bahn@gmail.com">nathan.bahn@gmail.com</a>> >> wrote: >>> >>> Wait a minute! I thought dual-booting created partitions that cannot be >>> breached! >> >> core.img is embedded into the post-MBR gap and not a partition. > </div><div class="im">> I am sorry, but I know what neither a core.img nor a post-MBR gap is. May I > trouble you for a link to some references? </div>Heard of Google? Anyway: Core.img is grub2's equivalent of grub1's stage 1.5. If you run "fdisk -lu /dev/sda", you'll see that /dev/sda1 starts at 63 (for a default Ubuntu install; Lubuntu and Fedora start at 2048). Sector 0 is the MBR and sectors 1-62 are the post-MBR gap. </blockquote></div> T.H.-- Thanks for the info. --N.B. -- Please avoid sending me Word or PowerPoint attachments. See <a href="http://www.gnu.org/philosophy/no-word-attachments.html" target="_blank">http://www.gnu.org/philosophy/no-word-attachments.html</a>