Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: William Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] Use case: initrd + NFS
Date: Thu, 29 Apr 2010 16:18:48 +0100	[thread overview]
Message-ID: <4BD9A358.7070901@carallon.com> (raw)
In-Reply-To: <4BD9959C.5000905@triumf.ca>

On 29/04/2010 15:20, Rod Nussbaumer wrote:
> Hi all. First post here. Thanks for the great tool.
>
> Someone mentioned use-cases, and I thought I would jump in with what I 
> was hoping to be able to build, but so far it looks like I will have 
> to work outside the the box. I'm wondering if anyone is working on or 
> sees a need for the configuration I would like to achieve.
> I am targeting diskless, headless CPUs that boot entirely from a 
> network server using PXE.
> In my world, it would be ideal to have a system that includes a 
> minimal initrd filesystem, plus a more substantial filesystem which 
> would be suitable for exporting via NFS. In this scenario, the target 
> would boot, and the init process would connect to the NFS server to 
> mount the rest of the filesystem which would contain applications and 
> the majority of the tools that the target host would use.
> Using such a scheme would allow a lot of 'offline' upgrades to be 
> added without requiring the target to be rebooted; simply replace the 
> content of the filesystem on the NFS server to upgrade the target. 
> Also, part of my intent is to get a system that boots as quickly as 
> possible, and the minimal initrd seems to aid in accomplishing this.
> I am still quite green with the use of buildroot, and not sure how 
> much effort is required to add this kind of capability. If someone can 
> assure me that it isn't a giant project, I may try to undertake it. Of 
> course any pointers about how to accomplish it would be gratefully 
> accepted, and the result of my effort would be available to roll back 
> into the buildroot tool, if it was wanted. Or, perhaps I've simply 
> overlooked an existing  configuration option that would produce such a 
> system.
> Thanks for listening.

This sounds similar to a problem that is on my todo list. I want to 
build a system with a minimal initramfs and then split the rest of the 
filesystem into a jffs2 image. I don't believe this functionality 
exists, although there is something in there for getting an initramfs 
built by busy box. If you have any ideas on how to proceed I'd be happy 
to offer feedback.

Will

-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Development Manager                      Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

  reply	other threads:[~2010-04-29 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-29 14:20 [Buildroot] Use case: initrd + NFS Rod Nussbaumer
2010-04-29 15:18 ` William Wagner [this message]
2010-04-29 15:44 ` Paulius Zaleckas

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=4BD9A358.7070901@carallon.com \
    --to=will_wagner@carallon.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