On 2009.07.29 11:31:14 -0700, Steve Lawrence wrote:
On Wed, Jul 29, 2009 at 08:43:05AM +0200, Martin Rehak wrote:
Hi Steve,
On 2009.07.23 14:34:22 -0700, Steve Lawrence wrote:
On Thu, Jul 23, 2009 at 09:14:55AM +0200, Martin Rehak wrote:
Hi Steve,
On 2009.07.22 12:32:01
Hi Steve,
On 2009.07.23 14:34:22 -0700, Steve Lawrence wrote:
On Thu, Jul 23, 2009 at 09:14:55AM +0200, Martin Rehak wrote:
Hi Steve,
On 2009.07.22 12:32:01 -0700, Steve Lawrence wrote:
The issue is that from the global zone context (non-zlogin), stuff like
symbolic links to
On Wed, Jul 29, 2009 at 08:43:05AM +0200, Martin Rehak wrote:
Hi Steve,
On 2009.07.23 14:34:22 -0700, Steve Lawrence wrote:
On Thu, Jul 23, 2009 at 09:14:55AM +0200, Martin Rehak wrote:
Hi Steve,
On 2009.07.22 12:32:01 -0700, Steve Lawrence wrote:
The issue is that from the
On Thu, Jul 23, 2009 at 09:14:55AM +0200, Martin Rehak wrote:
Hi Steve,
On 2009.07.22 12:32:01 -0700, Steve Lawrence wrote:
The issue is that from the global zone context (non-zlogin), stuff like
symbolic links to something like /etc could copy files from the global
zone.
I don't
Hi,
I am trying to get Live Upgrade better by reimplementing some parts of
the code. What I am not sure of is whether is it safe to do a copy of
non global zone imports (filesystems dedicated to a zone in its config)
from the global zone.
This is existing code (lucopy.sh:1808, install-nv-clone):
The issue is that from the global zone context (non-zlogin), stuff like
symbolic links to something like /etc could copy files from the global
zone.
I'm not sure why this is dangerous in this case, as we are only reading
from the zone, as cpio does not traverse/open sym links, it just copes the
