Strange Behavior - help

Strange Behavior - help

[Yashwant Shitoot]

[-- Attachment #1: Type: text/plain, Size: 446 bytes --]

Hello Friends,

 

My root file system and linux is in rom (flash). The linux itself runs
out of ram. When I reprogram the rom, I erase and write a new image of
the rom from a compact flash card. After the new image is programmed in
the function fclose() hangs up, implying that fclose() is rom resident
and loaded as needed. Does this make sense ? Remember even after erasing
the rom fopen() works fine.

 

Thanks 

 

Yash


[-- Attachment #2: Type: text/html, Size: 2286 bytes --]

Strange Behavior - help

[Yashwant Shitoot]

[-- Attachment #1: Type: text/plain, Size: 446 bytes --]

Hello Friends,

 

My root file system and linux is in rom (flash). The linux itself runs
out of ram. When I reprogram the rom, I erase and write a new image of
the rom from a compact flash card. After the new image is programmed in
the function fclose() hangs up, implying that fclose() is rom resident
and loaded as needed. Does this make sense ? Remember even after erasing
the rom fopen() works fine.

 

Thanks 

 

Yash


[-- Attachment #2: Type: text/html, Size: 2286 bytes --]

Re: Strange Behavior - help

[Ralf Baechle]

On Thu, May 06, 2004 at 10:19:43AM -0700, Yashwant Shitoot wrote:

> Hello Friends,

Allright, dinner on you ;-)

> My root file system and linux is in rom (flash). The linux itself runs
> out of ram. When I reprogram the rom, I erase and write a new image of
> the rom from a compact flash card. After the new image is programmed in
> the function fclose() hangs up, implying that fclose() is rom resident
> and loaded as needed. Does this make sense ?

Demand loading that is the binary will be paged in from backing store
(which is your ROM) as needed.

> Remember even after erasing the rom fopen() works fine.

Linux may at any time deciede to discard a page of memory.  It does so
when it think it has a better use for that memory.

Rewriting the underlying device of any filesystem is not a safe thing to
do.  A possible safe approach would be running from a ramdisk, for example.

  Ralf