linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "John Zhou" <zjzhou@newrocktech.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: How to change /proc to the writable directory
Date: Fri, 28 Nov 2003 12:30:43 +0800	[thread overview]
Message-ID: <000001c3b568$639e70a0$b702a8c0@newrock2> (raw)
In-Reply-To: <3FC65067.4060900@kegel.com>


Hi,

I have a based mpc82xx board running embedded linux. But, I met a problem now:

when I boot kernel and mount file system( cramfs and JFFS), for default, the dir /proc is not writable that located in cramfs. Now, I want to change it to be writable. which places/functions should I modify?

In cramfs I have these dirs:
/bin
/root
/boot
/sbin
/usr
/mnt
/dev/ --> /mnt/rwfs/dev
/proc --> /mnt/rwfs/proc
/etc  --> /mnt/rwfs/etc
/tmp  --> /mnt/rwfs/tmp
/var  --> /mnt/rwfs/var
...

In R/W JFFS I have these dirs:

dev
proc
etc
tmp
var

Thanks in advance!
John

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

  reply	other threads:[~2003-11-28  4:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-27 16:07 mpc / linux kernel - user space Juergen Oberhofer
2003-11-27 17:38 ` Jaap-Jan Boor
2003-11-27 18:08   ` Juergen Oberhofer
2003-11-27 19:28     ` Dan Kegel
2003-11-28  4:30       ` John Zhou [this message]
2003-11-28  8:12         ` How to change /proc to the writable directory Wolfgang Denk
2003-11-28  9:16     ` mpc / linux kernel - user space Jaap-Jan Boor
2003-11-28 15:42       ` Dan Malek
2003-12-01  8:18         ` Jaap-Jan Boor
2003-12-01 12:51           ` Peripherals Memory Mapping Kevin A. Sapp
2003-12-14 15:28             ` Paul Miller
2003-12-01 13:47           ` mpc / linux kernel - user space Juergen Oberhofer
2003-11-28  5:34 ` Sampath Kumar
2003-11-28  8:14   ` Wolfgang Denk

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='000001c3b568$639e70a0$b702a8c0@newrock2' \
    --to=zjzhou@newrocktech.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).