<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/cowloop/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/cowloop/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 09 Mar 2005 14:19:37 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/cowloop/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>Sync back to disk?</title><link>https://sourceforge.net/p/cowloop/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Is it possible to (or could it be added) so that there is a &lt;br /&gt;
command that applies a cowfile changes to the original &lt;br /&gt;
block device?&lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;In this way, you could spawn several cow instances on &lt;br /&gt;
a r-o device, perform several different actions and when &lt;br /&gt;
you have the one that works correctly, you could apply it &lt;br /&gt;
back to the r-o device (once you had mounted it r-w of &lt;br /&gt;
course) so that the changes you made inside the cowfile &lt;br /&gt;
would be written back to the original filesystem.&lt;/p&gt;
&lt;p&gt;This could be useful for all sorts of testing and &lt;br /&gt;
development purposes, e.g. for those testing &lt;br /&gt;
filesystems. &lt;/p&gt;
&lt;p&gt;It could also be used on LiveCD's etc. so that someone &lt;br /&gt;
could use the LiveCD, make a change to it (e.g. upgrade &lt;br /&gt;
a piece of software, tweak a setting) and then just &lt;br /&gt;
submit the cowfile.  The developers could then have the &lt;br /&gt;
changes be "patched" directly into the original LiveCD &lt;br /&gt;
filesystem.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lee Dowling</dc:creator><pubDate>Wed, 09 Mar 2005 14:19:37 -0000</pubDate><guid isPermaLink="false">https://sourceforge.neta48c40ebc09e3ec7829e018af313c75895664cfc</guid></item></channel></rss>