[p4] Permissions across Samba share

[Ivey, William]

I have a common filesystem across five or six unix boxes
plus several Windows machines. It's convenient to edit
files from whatever system I happen to be on at the time,
and even more convenient to use my Windows-based editor
for everything non-trivial. (It understands unix files
just fine.)

All the unix systems share a single client for the workspace,
but I don't extend that to the Windows machines (I've done
it using alroots, but it's usually not worth it). I just
open the files from unix and edit from Windows.

-Wm


-----Original Message-----
From: Slava Imeshev [mailto:imeshev at yahoo.com] 
Sent: Monday, July 23, 2007 6:17 PM
To: Ivey, William; perforce-user at perforce.com
Subject: RE: [p4] Permissions across Samba share

William,

Just out of curiosity: why would one want to share workspace content,
using Samba or anything else?

Regards,

Slava Imeshev
vimeshev at viewtier.com
www.viewtier.com 

> -----Original Message-----
> From: perforce-user-bounces at perforce.com 
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Ivey,
William
> Sent: Monday, July 23, 2007 10:09 AM
> To: perforce-user at perforce.com
> Subject: Re: [p4] Permissions across Samba share
> 
> On our system, the default permissions for samba always set 
> the user execute bit. That solves one problem, but introduces 
> its opposite: plain text files that look executable.
> 
> There doesn't seem to be a good way to get it right via Samba.
> 
> -Wm
> 
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Stephen
Vance
> Sent: Friday, July 20, 2007 6:59 PM
> To: lokowich
> Cc: perforce-user at perforce.com
> Subject: Re: [p4] Permissions across Samba share
> 
> The problem is that Windows doesn't have a concept of "executable"
> except by the extension. There's no way for a Windows program 
> to set Unix file permissions over a Samba mount.
> 
> Steve
> 
> lokowich wrote:
> > I've been using P4Win for Linux and Windows development per the
> Alt-Root 
> > scheme.  This works well except for my files that need to maintain

> > Writeable or Executable permissions across the Samba share. 
>  How can I
> 
> > configure my client or Samba to keep write/execute attributes when

> > managing files across platforms?  I currently use the command line

> > client on Linux to deal with this issue, but would like it to work
> with 
> > the GUI. (Yes, I've used P4V in a VNC session on KDE, but I 
> don't want
> 
> > to keep switching client applications.)
> >
> > Thanks,
> > Mark Lokowich
> > Systems Engineer
> > Advanced Communication Design
> > 7901 12th Ave. So.
> > Bloomington, MN 55425
> > 952-854-4000
> > lokowich at acdstar.com
> >
> > This email was Anti Virus checked by Astaro Security Gateway.
> http://www.astaro.com
> > _______________________________________________
> > perforce-user mailing list  -  perforce-user at perforce.com 
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> >
> >   
> 
> --
> Stephen Vance
> www.vance.com
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
> 
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com 
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>