Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian <bastisoft@arcor.de>
To: buildroot@busybox.net
Subject: [Buildroot] Creating a bootable filesystem image?
Date: Tue, 08 Apr 2008 12:02:58 +0200	[thread overview]
Message-ID: <47FB42D2.7040905@arcor.de> (raw)
In-Reply-To: <326f33790804071158h125bc8c3n9701bf1774ce5611@mail.gmail.com>

Hello Arun,

 > My question is, does anyone know if there is a way to configure 
buildroot to make rootfs.i386.ext2 bootable? Please note that I disabled 
RAMDISK in the > kernel .config before compiling buildroot because I 
don't need to use one.

This is because rootfs.i386.ext2 is only a file system image, not a hard 
disk image. It is missing the boot sector of the disk, which contains 
the Master Boot Record and the partition table. The BIOS on i386 does 
only execute the first sector on the disk (the MBR code) which usually 
only boots from the active partition. So you need a bootloader, as the 
kernel itself is not able to be loaded this way.

Like John said, you can use GRUB. But if you only want to boot a ext2 
partition, you can easily get away with Extlinux. It is a syslinux 
derivate with support for ext2 (and ext3) instead of FAT. It installs 
only into the partition (not into the master boot record), which means 
you should be fine by creating and activating the partition containing 
your ext2 image.

The changes in scripts/build-ext3-img references ext3 only while 
creating the file system. So you only need to change that if you want to 
use grub.

Best regards,
Sebastian

  parent reply	other threads:[~2008-04-08 10:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07 18:58 [Buildroot] Creating a bootable filesystem image? Arun Reddy
2008-04-07 19:29 ` John Voltz
2008-04-08 10:02 ` Sebastian [this message]
     [not found]   ` <326f33790804081325s680eb37bg9b8e73663277f4c2@mail.gmail.com>
2008-04-08 20:27     ` [Buildroot] Fwd: " Arun Reddy
     [not found]     ` <47FBE4A8.9080104@arcor.de>
2008-04-08 22:26       ` [Buildroot] " Arun Reddy
     [not found]         ` <47FBF3F3.4040001@arcor.de>
2008-04-08 23:50           ` Arun Reddy
     [not found]             ` <47FCD648.8040007@arcor.de>
2008-04-11 18:51               ` Arun Reddy
  -- strict thread matches above, loose matches on Subject: below --
2008-04-07 20:07 Sam Liddicott
2008-04-07 23:30 ` Arun Reddy
2008-04-11 19:11 Sam Liddicott
2008-04-14 16:57 ` Arun Reddy
2008-04-14 17:09   ` Arun Reddy
2008-04-15  8:35     ` Guillaume Dargaud
2008-04-14 20:29 Sam Liddicott
2008-04-14 22:31 ` Arun Reddy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47FB42D2.7040905@arcor.de \
    --to=bastisoft@arcor.de \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox