From a1db0380d4e43cd13197c8b1b1cfa335d6d933c1 Mon Sep 17 00:00:00 2001
From: freesource <freesource>
Date: Sun, 10 Mar 2002 21:07:03 +0000
Subject: [PATCH] This should be pretty obviously, however, this provides some
 good information which should make a gbootroot user even more knowledgable.

---
 yard/templates/Example-EmptyFS.yard | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 yard/templates/Example-EmptyFS.yard

diff --git a/yard/templates/Example-EmptyFS.yard b/yard/templates/Example-EmptyFS.yard
new file mode 100644
index 0000000..8822c9e
--- /dev/null
+++ b/yard/templates/Example-EmptyFS.yard
@@ -0,0 +1,21 @@
+# $Id$
+# Example-EmptyFS.yard
+
+# The recommended way for creating empty filesystems is to run gbootroot as
+# a normal user, choose the size you want, choose uml exclusively in the 
+# Filesystem Box, choose a filesystem command like mkreiserfs, press return or
+# submit, choose the create stage (see next paragraph) and continue.
+#
+# If you just created a filesytem with stuff in it, you will want to choose
+# the check stage along with the create state or you can take a look at 
+# /tmp/gboot_non_root_`ud -u`/loopback, if there is stuff in it you can just 
+# delete it by hand, and then proceed with the create stage.
+#
+# Notes: jffs/jffs2, cramfs, and romfs filesystems always have the /initrd and 
+# /dev  directories added since these directories need to exist in order for 
+# the MTD Emulator to work.  Genext2fs will have devices added if 
+# /tmp/gboot_non_root_`ud -u`/device_table.txt exists, and many fiLesystem
+# creators automatically add the lost+found directory.
+#
+# jffs/jffs2, cramfs and romfs have their respective fs type appended to
+# the image name you choose: root_fs turns into root_fs_jffs2