And new semantics to allow that would have one twist: you really only
want to allow this zone-requested loopback when the filesystem to mount
is share(1M)'d to the zone. You can't allow zones to have arbitrary
loopback mounts created upon request. So this might need support for
share -F lofs
[EMAIL PROTECTED] wrote On 07/31/06 07:36,:
Hi all,
I have a customer with the following question
I'm curious on what the best way to propagate all the user accounts on
the global zone down to the zones that are already created.
The only way that I know is to just copy the files needed
On 7/31/06, Steffen Weiberle [EMAIL PROTECTED] wrote:
Home directories are more problematic; you will need to loopback mount
them into the local zones.
Is the underlying problem being worked on, or is it worth an RFE to make this
transparent (automount
if remote, auto-lofs if local (not
Paul Kraus wrote:
On 7/31/06, Steffen Weiberle [EMAIL PROTECTED] wrote:
Home directories are more problematic; you will need to loopback mount
them into the local zones.
Is the underlying problem being worked on, or is it worth an RFE to
make this transparent (automount
if remote,
There is no way for the non-global zone automounter to convert these
automounts from NFS to LOFS. Firstly, there is no API for the non-global
zone to determine that the NFS server is, in fact, the global zone
sharing the same kernel.
It can easily tell this though.
Paul Kraus wrote:
On 7/31/06, Steffen Weiberle [EMAIL PROTECTED] wrote:
Home directories are more problematic; you will need to loopback mount
them into the local zones.
Is the underlying problem being worked on, or is it worth an RFE to
make this transparent (automount
if remote,
On 7/31/06, Glenn Faden [EMAIL PROTECTED] wrote:
Paul Kraus wrote:
If the home directories are auto-mounted, then work just like
on a non-zoned system. NFS from remote servers is mounted via NFS, if
the global zone is the home directory server, then the NFS mount is
supposed to be
[EMAIL PROTECTED] wrote:
There is no way for the non-global zone automounter to convert these
automounts from NFS to LOFS. Firstly, there is no API for the non-global
zone to determine that the NFS server is, in fact, the global zone
sharing the same kernel.
It can easily tell this
It's not obvious to me how the non-global zone can determine the
hostname of its global zone unless the global zone puts that information
somewhere (like in a new file).
Connect to rpcbind and then check whether getpeerucred() works :-)
That's just a small matter of programming :-)
Seems
Glenn Faden writes:
It can easily tell this though.
It's not obvious to me how the non-global zone can determine the
hostname of its global zone unless the global zone puts that information
somewhere (like in a new file).
It should not be based on something flimsy (and
Rainer Orth wrote:
Glenn Faden [EMAIL PROTECTED] writes:
Since the non-global zone automounter is unaware and unable to do
anything else, it will simply do an NFS mount. The problem is that CR
5065254 (NFS/UFS deadlock when system is both NFS server and client) is
likely to cause a
11 matches
Mail list logo
