> Why map it to mkdir rather than using zfs create ? Because mkdir means
> it will work over NFS or CIFS.
Also your users and applications don't need to know. The administrator sets the
policy and then it just happens, plus the resulting "directories" would end up
with the correct ownership mode
On Fri, Sep 29, 2006 at 01:26:04AM +0200, [EMAIL PROTECTED] wrote:
>
> >Please elaborate: "CIFS just requires the automount hack."
>
>
> CIFS currently access the files through the local file system so
> it can invoke the automouter and there can use "tricky maps".
Well, Samba does. And it do
>Please elaborate: "CIFS just requires the automount hack."
CIFS currently access the files through the local file system so
it can invoke the automouter and there can use "tricky maps".
Casper
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
On Thu, Sep 28, 2006 at 12:40:17PM -0500, Ed Plese wrote:
> This can be elaborated on to do neat things like create a ZFS clone when
> a client connects and then destroy the clone when the client
> disconnects (via "root postexec"). This could possibly be useful for
> the shared build system that
On Thu, Sep 28, 2006 at 09:00:47AM -0700, Ron Halstead wrote:
> Please elaborate: "CIFS just requires the automount hack."
Samba's smb.conf supports a "root preexec" parameter that allows a
program to be run when a share is connected to. For example, with
a simple script, createhome.sh, like,
#
Please elaborate: "CIFS just requires the automount hack."
Ron
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
