Re: RAM based filesystem in uclinux

Ashish Phogat <[email protected]>
Newsgroups gmane.linux.uclinux.devel
Message-ID <CANNeoba3_pYqvGX+Et1gUhvKa-Mad2t9RKXPRUzSo5Yzh7tcdQ@mail.gmail.com>
I am using Linux kernel version 2.4...Whether initramfs is available in
that kernel version 2.4 with cpio archieve.
DO I need to select initrd or ramdisk with initramfs?

I am sorry I am new to uclinux/linux. I am building myself in uclinux

Thanks
Ashish Phogat

On Fri, Mar 22, 2013 at 9:41 AM, Lennart Sorensen <
[email protected]> wrote:

> On Fri, Mar 22, 2013 at 09:28:18AM -0400, Ashish Phogat wrote:
> > Hi folks,
> > I have some basic problem:
> >
> > I have my uclinux currently running on Coldfire board from RAM. I have
> > romfs as my file system but that is read only file system.I donot enable
> > MTD support, blckmem is also disabled.
> >
> > I enabled a RAM disk(CONFIG_BLK_DEV_RAM) and
> initrd(CONFIG_BLK_DEV_INITRD)
> > and choose rootfs as my filesystem.
> >
> >
> > Now I want to change my configuration so that I have a writable
> filesystem
> > in RAM.
> >
> > I am confused with the configurations I need to set to choose a writable
> > file system for uclinux running from RAM.
> >
> > What uclinux configuration I need to select to boot uclinux in RAM with
> > writeable filesystem?
> >
> > I guess I donot need MTD because that is used for FLASH memory, Neither I
> > need blckmen that is also for FLASH memory. I need to just create a block
> > on RAM and just put a filesystem on that block.
> >
> > Please correct me if I am wrong.
> >
> > Please also proivde the reason which and why a particular configuration
> is
> > enabled. What role the config is playing in writeable filesystem?
> > Thanks a lot for replying
>
> We use initramfs and a cpio archive joined with the kernel in a multipart
> uImage.  Works great.  In the case of busybox and other multicall binaries,
> using hardlinks uses vastly less ram than symlinks (each symlink uses
> one page of ram to store the symlink file).
>
> 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.
>
> --
> Len Sorensen
> _______________________________________________
> uClinux-dev mailing list
> [email protected]
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> This message was resent by [email protected]
> To unsubscribe see:
> http://mailman.uclinux.org/mailman/options/uclinux-dev
>

_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.