Difference between revisions of "Step-by-step NFS-mounted Root File System"
From odroid US
(→Prerequisites) |
|||
| Line 13: | Line 13: | ||
=== Prerequisites === | === Prerequisites === | ||
<li> You need to know how to build a kernel. There are many ways to do it. This tutorial walks through a native kernel build: [[Kernel Compiling]] | <li> You need to know how to build a kernel. There are many ways to do it. This tutorial walks through a native kernel build: [[Kernel Compiling]] | ||
| − | <li> You need to know how to abort booting at the u-boot console. [odroid.us/mediawiki/index.php?title=U-boot_Topics&action=view§ion=5] | + | <li> You need to know how to abort booting at the u-boot console. [http://odroid.us/mediawiki/index.php?title=U-boot_Topics&action=view§ion=5] |
Revision as of 21:10, 17 January 2013
THIS TOPIC ACTIVELY BEING EDITED. IT IS NOT COMPLETE
This tutorial is for Developers
Introduction
A common technique for embedded development is to NFS-mount your root file system. This means that all files are actually on a host. The host is configured to export the filesystem. The target (odroid) mounts the filesystem at boot time and uses it as its own. All files are visible on the host.
As targets have increased in storage capacity and speed, the need for NFS-mounting root file systems will decrease. The technique is still useful when bringing up a new port or you have a lot of files that need to change together.
It is common to check in a whole root file system into a source control system for quality control.
