[FE training-materials-updates] devtmpfs related changes

Michael Opdenacker michael.opdenacker at free-electrons.com
Fri Oct 11 05:02:41 CEST 2013

Repository : git://git.free-electrons.com/training-materials.git

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=9725abc4efd6ce6b8e648ae18f80edf8f54a86c5


commit 9725abc4efd6ce6b8e648ae18f80edf8f54a86c5
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Oct 10 17:35:36 2013 +0200

    devtmpfs related changes
    - With the kernel config for omap2plus, devtmpfs is now automatically
      mounted on /dev at boot time.  Update the instructions to stop
      asking people to create the device files.
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


 .../sysdev-block-filesystems.tex                   |    9 +++------
 labs/sysdev-tinysystem/sysdev-tinysystem.tex       |    6 ++++--
 2 files changed, 7 insertions(+), 8 deletions(-)

diff --git a/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex b/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
index 2be6b85..8c0828b 100644
--- a/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
+++ b/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
@@ -81,13 +81,10 @@ the \code{www/upload/files} directory (in your target root filesystem)
 into this new partition. The goal is to use the third partition of the
 MMC card as the storage for the uploaded images.
-Connect the MMC disk to your board. On the board command line,
-have a look at \code{/proc/partitions} to see which device names
-the kernel gives to your partitions, and which major and minor numbers
-their device files should have.
+Connect the MMC disk to your board. You should see the MMC partitions
+in \code{/proc/partitions}.
-Create the device file for your third partition and mount this partition
-on \code{/www/upload/files}.
+Mount this third partition on \code{/www/upload/files}.
 Once this works, modify the startup scripts in your root filesystem
 to do it automatically at boot time.
diff --git a/labs/sysdev-tinysystem/sysdev-tinysystem.tex b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
index 57496ba..ccb0340 100644
--- a/labs/sysdev-tinysystem/sysdev-tinysystem.tex
+++ b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
@@ -151,8 +151,10 @@ Now run \code{make install} to install BusyBox in this directory.
 Try to boot your new system on the board. If everything goes right,
 the kernel should again confirm that it managed to mount the NFS root
 filesystem. Then, you should get errors about missing \code{/dev/ttyX}
-files. Create them with the \code{mknod} command (using the same major
-and minor number as in your GNU/Linux workstation). Try again.
+files. This is because the kernel didn't manage to mount the
+\code{devtmpfs} filesystem because the \code{/dev} directory doesn't
+exist yet. Create the \code{dev} directory and reboot. The errors should
+go away. 
 At the end, you will access a console and will be able to issue
 commands through the default shell.

More information about the training-materials-updates mailing list