linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Gérard Guével" <gguevel@interfaceconcept.com>
Cc: linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: File system boot strategy
Date: 14 Nov 2003 06:40:06 -0700	[thread overview]
Message-ID: <1068817206.29984.5.camel@hermes> (raw)
In-Reply-To: <000101c3aaae$e61e4240$5201a8c0@GEG2400>


On Fri, 2003-11-14 at 05:57, Gérard Guével wrote:
> Hi,
>
> I have a custom 8260 board with a 2.4.18 Kernel.
>
> I want to mount multiple file systems from a CFI compliant flash.
> The directories are distributed  like this :
>
> 	/   /bin /home /lib /root /sbin /usr		-> cramfs  to have a protected Linux
> kernel
> 	/etc /tftpboot				-> jffs2      to allow modifying services and files to
> load
> 	/dev /proc /tmp /var			-> ramfs    to store data which can be lost.
>
> I want to boot with the cramfs as root file system but the UNTAR wants all
> the directories /dev /proc /tmp in the cramfs.
>
> Can I use multiple file systems like this ?
> Must I start with a ramfs and then mount cramfs ?
>
> I find many docs to mount each file system individually and to add others
> file systems mounted on /mnt
> but no example to break a standard filesystem into multiple sub file
> systems.

There is nothing special about /mnt - it's just a directory (or set of
directories like /mnt/floppy, /mnt/cdrom, etc). Also, the main names
(like /etc) could be symbolic links.  Here's how I might solve this:

==  cramfs  contents

    /bin
    /home
    /lib
    /root
    /sbin
    /usr
    /JFFS2          (just a mount point)
    /etc => /JFFS2/etc
    /tftpboot => /JFFS2/tmp
    /RAMDISK        (another mount point)
    /tmp => /RAMDISK/tmp
    /var => /RAMDISK/var

/dev and /proc are special.  If you enable "devfs" and "procfs" in the
kernel they get populated automatically, all you need do is mount them.

--
Gary Thomas <gary@mlbassoc.com>
MLB Associates


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-11-14 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14 12:57 File system boot strategy Gérard Guével
2003-11-14 13:40 ` Gary Thomas [this message]
2004-03-19 18:32 ` MPC8260 HDLC RX length errors Gérard Guével

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=1068817206.29984.5.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=gguevel@interfaceconcept.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).