All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] initrd isn't needed for iso9660 when initramfs is used
Date: Thu, 22 Aug 2013 07:56:26 +0200	[thread overview]
Message-ID: <5215A80A.9070006@mind.be> (raw)
In-Reply-To: <1377148166-21030-1-git-send-email-shmuelzon@gmail.com>

On 22/08/13 07:09, Assaf Inbal wrote:
> I'm not entirely sure of this patch.
> The problem is that, while initrd isn't needed when initramfs is used, the
> default menu for grub always includes the initrd directive and will fail to load
> when it's missing.

  Why do you want to use iso9660 with an initramfs? initramfs is only 
really useful for boat loaders that have a problem with passing an 
initrd, e.g. network boot.


  Regards,
  Arnout

> Perhaps we should have two grub menus? Or create it during build?
> Any ideas?
>
> Thanks,
> Assaf
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2013-08-22  5:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22  5:09 [Buildroot] initrd isn't needed for iso9660 when initramfs is used Assaf Inbal
2013-08-22  5:09 ` [Buildroot] [PATCH] iso9660 fs: no need to copy initrd when using initramfs Assaf Inbal
2013-08-22  5:56 ` Arnout Vandecappelle [this message]
2013-08-22  8:42   ` [Buildroot] initrd isn't needed for iso9660 when initramfs is used Assaf Inbal

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=5215A80A.9070006@mind.be \
    --to=arnout@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.