Re: minimizing disk WRITES - if OS is on CompactFlash

Yyy wrote:
I'd like to replace HDD with CompactFlash+IDEadapter and to setup system entirely on CompactFlash memory card.
(In notebook/laptop this'll mean en enormous energy/battery savings!)

And I also want to save a CF card from too many writes to it.
The reason: longevity of such flash memory and also the speed - since writes consume more time than reads.

Is there any ready solution to use the folders: /tmp, /var and /home in read-
only mode? ;)

In such a would-be solution (minor) modifications would be kept in the memory as kind of "differences",
and only when the system was shut down, or on explicit user's demand, the modifications would be writen down back to "disk" CF?

The point is not to exert media with too frequent writes. Only just browsing wwws means countless brower's "history" updates etc., moving/positioning windows constantly make changes in KDE configuration files,
all such frequent modifications definitely are not good neither necessery to write back to the 'disk' in real-time...

Use the noatime and nodiratime mount options. That way the inode access times won't be updated, even for reads. The async mount option is already included in defaults.

/tmp, /var, and /home pretty much always have changes. If you've got a funky setup where you think they won't, you can try mounting them ro to see how fast the system crashes. There's no other magic I know for what you want.
.

Relevant Pages

  • Re: minimizing disk WRITES - if OS is on CompactFlash
    ... system entirely on CompactFlash memory card. ... longevity of such flash memory and also the speed - since writes consume more time than reads. ... and only when the system was shut down, or on explicit user's demand, the modifications would be writen down back to "disk" CF? ... Use the noatime and nodiratime mount options. ...
    (comp.os.linux.setup)
  • minimizing disk WRITES - if OS is on CompactFlash
    ... to setup system entirely on CompactFlash memory card. ... longevity of such flash memory and also the speed - since writes ... modifications would be writen down back to "disk" CF? ...
    (comp.os.linux.setup)