On 12.09.2016 10:20, Michal Privoznik wrote:
> On 27.05.2016 10:05, Nikolay Shirokovskiy wrote:
>> There is already a patch [1] on this topic with a different approach - keep
>> nvram file by default. There is also some discussion there. To sum up keeping
>> nvram on undefine could be useful in s
On Mon, Sep 12, 2016 at 07:01:38PM +0200, Andrea Bolognani wrote:
> On Mon, 2016-09-12 at 10:20 +0200, Michal Privoznik wrote:
> > On 27.05.2016 10:05, Nikolay Shirokovskiy wrote:
> > > There is already a patch [1] on this topic with a different approach -
> > >keep
> > > nvram file by default.
On Mon, 2016-09-12 at 10:20 +0200, Michal Privoznik wrote:
> On 27.05.2016 10:05, Nikolay Shirokovskiy wrote:
> > There is already a patch [1] on this topic with a different approach -
> >keep
> > nvram file by default. There is also some discussion there. To sum up
> > keeping
> > nvram on und
On 27.05.2016 10:05, Nikolay Shirokovskiy wrote:
> There is already a patch [1] on this topic with a different approach - keep
> nvram file by default. There is also some discussion there. To sum up keeping
> nvram on undefine could be useful in some usecases so there should be an
> option
> to
27-May-16 11:05, Nikolay Shirokovskiy пишет:
There is already a patch [1] on this topic with a different approach - keep
nvram file by default. There is also some discussion there. To sum up keeping
nvram on undefine could be useful in some usecases so there should be an option
to do it. On t
ping
On 27.05.2016 11:05, Nikolay Shirokovskiy wrote:
> There is already a patch [1] on this topic with a different approach - keep
> nvram file by default. There is also some discussion there. To sum up keeping
> nvram on undefine could be useful in some usecases so there should be an
> option
ping
On 27.05.2016 11:05, Nikolay Shirokovskiy wrote:
> There is already a patch [1] on this topic with a different approach - keep
> nvram file by default. There is also some discussion there. To sum up keeping
> nvram on undefine could be useful in some usecases so there should be an
> option
There is already a patch [1] on this topic with a different approach - keep
nvram file by default. There is also some discussion there. To sum up keeping
nvram on undefine could be useful in some usecases so there should be an option
to do it. On the other hand there is a danger of leaving domain