<div class="gmail_quote">On Mon, May 19, 2008 at 7:55 AM, Rahul Sundaram <<a href="mailto:sundaram@fedoraproject.org">sundaram@fedoraproject.org</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">Paul W. Frields wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Sun, 2008-05-18 at 13:22 +0300, John Babich wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> On Sat, May 17, 2008 at 11:50 PM, Rahul Sundaram <<a href="mailto:sundaram@fedoraproject.org" target="_blank">sundaram@fedoraproject.org</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi, I suggested to Luke to use something better than "persistent overlay" to describe the amount of space alloted for storing software changes and settings in a Live USB. </blockquote> How about "permanent storage"? </blockquote> Tough call -- because the space is used for differences in the whole file system, not just data storage. So a 512 MB overlay doesn't mean the user can store 512 MB of data, especially if they start changing the package complement. </blockquote> </div> Any other suggestions please? </blockquote><div> A small list: 1) Saved State 2) State Layer 3) Writable Layer 4) Read-Write Overlay 5) Read-Write Area 6) Changeable Image "User data and system changes are saved to the _BLANK_." Calling it a "Writable Layer" might make slightly more common sense. </div></div>