envfs: provide an intentional way to ignore an existing external environment

[Jean-Christophe PLAGNIOL-VILLARD]

On 09:44 Thu 31 Jul     , Uwe Kleine-K??nig wrote:
> 
> On Thu, Jul 31, 2014 at 09:33:02AM +0200, Juergen Borleis wrote:
> > Hi Uwe,
> > 
> > On Thursday 31 July 2014 09:14:25 Uwe Kleine-König wrote:
> > > [...]
> > > Compared with storing the default environment in the external store the
> > > only difference is that you don't need to modify it if you change the
> > > internal one, right?
> > 
> > This would also be an advantage of this new feature.
> The only one even?
> 
> > > I wonder what the targeted use case is.
> > 
> > To use an external stored environment *only* for development purposes or tests 
> > and to keep the possibility to do so.
> Doesn't make a warm and cosy feeling. Isn't it easier and more robust to
> just not tell barebox about the external storage at all and for the
> testing/development procedure do an explicit
> 
> 	loadenv /dev/tralala
+1

Best Regards,
J.