On 11/11/09 12:17, Chris Gerhard wrote:
Alan Wright wrote:
> Chris Gerhard wrote:
>> How can I map what appears to be the default the "SYSTEM" group on
>> windows XP to a group on Solaris? I always end up with an ephemeral
>> group for that?
>>
>> I've mapped my user "cjg" <-> "cg13442" and
Chris Gerhard wrote:
Seems a shame that we can't generate a default ACL for owner@ and
gr...@for the case when user:XX == owner etc.
The semantics are different. owner@ refers to whoever owns the file now,
while user:XX is independent of the file ownership. If you change the
owner of the fi
There are technical challenges that we need to resolve before we
can offer child mounts over SMB. It's on the to-do list but we
are focusing on DFS first.
Symlinks are one of the challenges, as are mounted file systems
with different properties than the parent.
From a user perspective, you prob
Alan Wright wrote:
Chris Gerhard wrote:
How can I map what appears to be the default the "SYSTEM" group on
windows XP to a group on Solaris? I always end up with an ephemeral
group for that?
I've mapped my user "cjg" <-> "cg13442" and put it in the default
group smbstaff which I have also
Alan Wright wrote:
> Chris Gerhard wrote:
>> How can I map what appears to be the default the "SYSTEM" group on
>> windows XP to a group on Solaris? I always end up with an ephemeral
>> group for that?
>>
>> I've mapped my user "cjg" <-> "cg13442" and put it in the default
>> group smbstaff which
Chris Gerhard wrote:
How can I map what appears to be the default the "SYSTEM" group on
windows XP to a group on Solaris? I always end up with an ephemeral
group for that?
I've mapped my user "cjg" <-> "cg13442" and put it in the default group
smbstaff which I have also mapped. However every
Jordan Brown wrote:
[ Answered on the internal list, repeated here for the other audience ]
Thank you Jordan and my apologies for the double posting. My internal
post resulted in someone pointing me here. My bad for not thinking of
coming here first.
Chris Gerhard wrote:
How can I map wh
So is there anyway to map it to a UNIX group then?
Thanks
Andrew
Jordan Brown wrote:
[ Answered on the internal list, repeated here for the other audience ]
Chris Gerhard wrote:
How can I map what appears to be the default the "SYSTEM" group on
windows XP to a group on Solaris? I always end
Chris,
I just got to the same stage while playing withs CIFS.
I think the reason is that the SYSTEM is not a domain account and I have
also notice the same for HOSTNAME\Administrator account. I am noticing
it with windows profiles
If you look at #idmap dump you may notice some short SID.
An
[ Answered on the internal list, repeated here for the other audience ]
Chris Gerhard wrote:
How can I map what appears to be the default the "SYSTEM" group on
windows XP to a group on Solaris? I always end up with an ephemeral
group for that?
SYSTEM (aka "Local System", S-1-5-18) is hardwire
How can I map what appears to be the default the "SYSTEM" group on
windows XP to a group on Solaris? I always end up with an ephemeral
group for that?
I've mapped my user "cjg" <-> "cg13442" and put it in the default group
smbstaff which I have also mapped. However every object I create on XP
Thanks for your reply,
What was the rationale behind not showing / allowing access to child file
systems? Was it technical, or some other reason?
Was the child file system design purely for administrative purposes, for
allowing inheritance of file system properties? If so wouldn’t it have been
And to the CIFS group.
PS. If you have that many drives in a raid, you should split them up into two
vdev. And preferably use raidz2 instead of raidz1. Because if the drives are
large, it takes very long time to resilver a zpool. With large 2-3TB drives it
might take several days. Resilvering
13 matches
Mail list logo
