Ashish, With respect, people here have already mentioned a couple of ways. The most common for non-embedded systems is a initramfs or initrd via a cpio archive. There's extensive documentation on this in Documentation/initrd.txt.
Embedded systems typically _don't_ want a writable root filesystem. uClinux is typically setup with a romfs, and then a writeable ramfs located at /var. If you're looking for a space to write temporary files during runtime, you'd probably want to do so there. Be aware of course that those go away at reboot. And for that matter, typically the way the initramfs or initrd work is you may be able to write to them, but on reboot any changes aren't persisted anyway. In my rc file: /bin/expand /etc/ramfs.img /dev/ram1 mount -t ext2 /dev/ram1 /var There's also tmpfs. You can set one of those up (exist in 2.4??) and mount on some arbitrary mount point. For writable and persisting, you're going to need to use a real filesystem on some real media, either disk or flash. And if you don't need persistance, then I don't see why directing your temp files to an already writable space in /var or /tmp won't work. As for the exact configuration settings and all that... well, you're on a 2.4 kernel and nearly no one is bothering with that kernel anymore. Heck, I'm working on a 3.2 kernel and someone told me the other day that I'm way out-of-date. Anyway, since you're on a 2.4 kernel, I certainly don't remember the specific settings anymore, nor do I have one setup that way lying around to check for you. You're going to do some looking and some trial-and-error to figure out the correct settings. But I'd be shocked if there isn't some legacy how-to out there. And the aforementioned documentation should be sufficient. If you don't have a very compelling reason to stay on a 2.4 kernel you might want to consider upgrading. Especially if you're starting a new project. I hope that helps, - Steve On Sat, Mar 23, 2013 at 4:14 PM, Ashish Phogat <engineerpho...@gmail.com>wrote: > Hi, > Could someone provide me the mechanism/configuration to have a RAM based > filesystem which is writable? My kernel is 2.4. > > Thanks for replying > > > On Sat, Mar 23, 2013 at 4:19 AM, Greg Ungerer > <gregunge...@westnet.com.au>wrote: > >> Hi Lennart, >> >> On 22/03/13 23:41, Lennart Sorensen wrote: >> > The fact we can recreate the cpio archive and update the uImage from >> > the kernel and cpio archive is great. No recompile crap to deal with >> > the way romfs and such have tended to need. For us building the kernel >> > and the filesystem are totally seperate issues. >> >> I don't follow you here. How does using a ROMfs mean that building >> the kernel and filesystem are not separate? >> >> Regards >> Greg >> >> >> >> _______________________________________________ >> uClinux-dev mailing list >> uClinux-dev@uclinux.org >> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev >> This message was resent by uclinux-dev@uclinux.org >> To unsubscribe see: >> http://mailman.uclinux.org/mailman/options/uclinux-dev >> > > > _______________________________________________ > uClinux-dev mailing list > uClinux-dev@uclinux.org > http://mailman.uclinux.org/mailman/listinfo/uclinux-dev > This message was resent by uclinux-dev@uclinux.org > To unsubscribe see: > http://mailman.uclinux.org/mailman/options/uclinux-dev >
_______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
