From: "Gérard Guével" <gguevel@interfaceconcept.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: File system boot strategy
Date: Fri, 14 Nov 2003 13:57:40 +0100 [thread overview]
Message-ID: <000101c3aaae$e61e4240$5201a8c0@GEG2400> (raw)
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.
Any help would be welcome.
Thanks
Gérard Guével
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2003-11-14 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 12:57 Gérard Guével [this message]
2003-11-14 13:40 ` File system boot strategy Gary Thomas
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='000101c3aaae$e61e4240$5201a8c0@GEG2400' \
--to=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