From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] need help making bootable image
Date: Mon, 21 Nov 2011 09:31:50 +0100 [thread overview]
Message-ID: <20111121093150.17b188e6@skate> (raw)
In-Reply-To: <90A7D971-7584-4B45-8DCB-61BEE8AE3EC0@jakesullivan.com>
Hello,
Le Sun, 20 Nov 2011 14:34:42 -0800,
Jacob Sullivan <mail@jakesullivan.com> a ?crit :
> > I don't understand why you're trying to mix an ISO image and an ext2
> > partition here. Why don't you simply make your ext2 image bootable ?
> >
> > I have some script stuff that does that here (create partitions,
> > loopback mount them, install grub, etc.), I could extract it and
> > make it available if you're interested.
>
> I tried to make the ext2 image bootable (that is the only thing I
> can't seem to make work). I went down the iso path because that
> image would boot and had a version of grub that was the same as in
> the ext2 image. I would love to have a copy of the scripts.
Basically, you have a version of Grub available in
output/staging/sbin/grub that you can use to install Grub.
I'll try to clean up the script, but it unfortunately won't be this
week as I'm busy with many other things.
> how should I install grub? Since my dev machine has grub2, I thought
> booting from the ISO image would be a good workaround... I also
> thought that the whole idea of fakeroot was so that tools like
> buildroot could do these types of tasks...
fakeroot can do *some* things, but not everything.
> > Instead, use a custom post-build script (BR2_POST_BUILD_SCRIPT) that
> > tweaks the inittab.
>
> Ah. That is what I was looking for. I would love sample post-build
> scripts if you have any.
There's one little sample script in the slides, do you more examples ?
> This was really useful, there should be a link to this from the
> buildroot doc or faq page. In all my google searches for other
> buildroot problems, this didn't come up, but should have.
My intention was to make improvements to the Buildroot documentation by
integrating some aspects of those slides.
> No, I'll download those and search them. My problem is from the
> search bar on this page: http://buildroot.uclibc.org/lists.html I get
> this strange error from google... " We're sorry...
>
> ... but your computer or network may be sending automated queries. To
> protect our users, we can't process your request right now.
>
> See Google Help for more information."
Ah, okay, I never used the search engine for the mailing list archives.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2011-11-21 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 20:51 [Buildroot] need help making bootable image Jacob Sullivan
2011-11-19 21:42 ` Bjørn Forsman
2011-11-20 8:26 ` Thomas Petazzoni
2011-11-20 22:34 ` Jacob Sullivan
2011-11-21 8:31 ` Thomas Petazzoni [this message]
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=20111121093150.17b188e6@skate \
--to=thomas.petazzoni@free-electrons.com \
--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