I am trying to understand several aspects \of how Linux &quot;works&quot; In the pre- X mac world they had a data and resource forking to simplify the concept. In Linux there seems to be a debate over modular Vs monolithic software architectures. What I am trying to expand my understanding of seems trivial but likely is not. It centers on which architectural path causes/needs the least writes to the core areas of what we call a &quot;distro&quot;&nbsp; I admit to being more than a bit fixated in my logic on a &quot;distro in flash&quot; eventual goal. The precedent I am looking back to is influenced by Apple&#39;s OS in ROM approach. Or the MP3 players which load their &quot;OS&quot; from a partition of their pooled flash resource into the devices working RAM area. <br>
<br>We have several folks on list who are way better coders than most folks ever meet. I am curious to hear their comments on what if any Kernel tweaks would optimise a distro for running from flash as Puppy appears to be using. I&#39;m NOT a low level coder, I can follow along some distance when it&#39;s presented clearly. The idea I&#39;m targeting is to get a distro in flash that does not abuse the flash media needlessly. <br clear="all">
<br>-- <br>Oren Beck<br><br>816.729.3645<br>