From: Paulius Zaleckas <paulius.zaleckas@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Use case: initrd + NFS
Date: Thu, 29 Apr 2010 18:44:49 +0300 [thread overview]
Message-ID: <4BD9A971.7040404@gmail.com> (raw)
In-Reply-To: <4BD9959C.5000905@triumf.ca>
On 04/29/2010 05:20 PM, 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.
I am booting my Asus EEE PC 701 through PXE (without initrd) and I pass
options for kernel to mount NFS root file system. Everything works just
fine.
> --- rod.
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
prev parent reply other threads:[~2010-04-29 15:44 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
2010-04-29 15:44 ` Paulius Zaleckas [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=4BD9A971.7040404@gmail.com \
--to=paulius.zaleckas@gmail.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 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.