[ale] Hard time with ram disks
Christopher Fowler
cfowler at outpostsentinel.com
Wed Oct 24 18:21:21 EDT 2001
Will using a ramdisk smaller than specify give me a problem? I thought
maybe my blowfish encryption was an issue.
I have a C file that is the only binary on the initrd. It opens the rom and
then reads the 2 files on. Placing both in different locations. Each is
4mb in size and placed at 2 locations. One to be mounted as root and the
other to be mounted as /usr. I'm debating on even using 2 4mb files and
combining them into 1 8mb ext2 file system.
Originally / was a writable ext2 and /usr was a readonly cramfs partition.
But i had so many problems with 2.4.2 that I tried 2.4.12 and then 2.4.10.
I have a /log that is ramfs but it does not respect my maxsize setting. It
apperas I can fill it up till my box crashes.
the blowfish was used to keep anyone reading the files on the flash to be
able to mount and reverse engineer the unit.
Anyone here have any design suggestions?
Thanks,
Chris
-----Original Message-----
From: Vaidhy Mayilrangam [mailto:vaidhy at loonys.net]
To: ale at ale.org
Sent: Wednesday, October 24, 2001 6:09 PM
To: Christopher Fowler
Cc: ale at ale.org
Subject: Re: [ale] Hard time with ram disks
The default ramdisk size is 4MB.. you can create larger ramdisks by
specifying
ramdisk_size=N where N is in K.. it will create ramdisk for that size.
I do not think you need to change the kernel at all.
Vaidhy
On Wed, Oct 24, 2001 at 05:22:23PM -0400, Christopher Fowler wrote:
> I'm sending this email out but I believe I'm having problem with neomail
> retrieving them.
>
> I currently using a 2.4.10 kernel with 16mb ramdisks enabled. I'm loading
> only 4mb ramdisks. I can get
> one full filesystem loaded to /dev/ram7 but almost all the way through
> loading /usr to /dev/ram6 I get an out of bounds error on write. Should
I
> configure the size of the ramdisk to only 4mb each? should I change
> kernels?
>
> I upgraded from 2.4.2 because it appeared the kernel did not respect my us
> of ramdisks it would overwrite them at any chance. It usually protected /
> but would destroy /usr
>
>
>
> Thanks,
> Chris
>
>
> ---
> This message has been sent through the ALE general discussion list.
> See http://www.ale.org/mailing-lists.shtml for more info. Problems should
be
> sent to listmaster at ale dot org.
>
>
---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
sent to listmaster at ale dot org.
---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
sent to listmaster at ale dot org.
More information about the Ale
mailing list