public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Charles S. Wilson" <cwilson@ece.gatech.edu>
To: Michael Bresnahan <mbresnahan1@mmm.com>
Cc: cygwin@cygwin.com
Subject: Re: CVS permissions problem with network drive
Date: Fri, 08 Dec 2000 16:46:00 -0000	[thread overview]
Message-ID: <3A3180FA.1A97A977@ece.gatech.edu> (raw)
In-Reply-To: <3A316662.661367BB@mmm.com>

Michael Bresnahan wrote:
> bash-2.04$ /usr/bin/cvs.exe co OrderStatus
> cvs.exe [checkout aborted]: /g/xapp/users/uscpw084/cvsroot/CVSROOT:
> Permission denied
> 
> I'm fairly sure I have the security setup correctly, because the direct
> NT port of CVS does not have a problem accessing the repository.

Actually, this means very little.  There are differences in the way
cygwin and NT(native) deal with SMB shares.  Please show:

ls -ld /g/xapp/users/uscpw084/cvsroot
ls -ld /g/xapp/users/uscpw084/cvsroot/CVSROOT
ls -ld /g/xapp/users/uscpw084/cvsroot/CVSROOT/

> The repository is on a HPUX 11 box 

Oh, now hold on just a minute. So this isn't windows peer-to-peer file
sharing.  Now, you've thrown SAMBA into the mix, which is ALSO different
from NT(native) SMB, w.r.t. file permissions.

It looks to me as if your problem isn't CVS, but a misunderstanding as
to how permissions on samba shares are dealt with from cygwin clients. 
Please search the archives..."samba" "permissions"

--Chuck

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-12-08 16:46 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-08 14:52 Michael Bresnahan
2000-12-08 16:46 ` Charles S. Wilson [this message]
     [not found] <OF4452111B.B0F21FC3-ON862569B2.00610F4F@mmm.com>
2000-12-12 12:25 ` Charles Wilson
2000-12-13  2:30   ` Corinna Vinschen
2000-12-13 10:49     ` Charles Wilson
2000-12-13 14:36       ` Corinna Vinschen
2000-12-13 23:02         ` Charles Wilson
2000-12-14  3:12           ` Corinna Vinschen
2000-12-14  9:23             ` Charles S. Wilson
2000-12-16  8:03               ` Corinna Vinschen
2000-12-16 23:08                 ` Charles S. Wilson
2000-12-17  0:16                   ` Charles S. Wilson
2000-12-17  3:46                     ` Corinna Vinschen
2000-12-17 11:45                       ` Charles S. Wilson
2000-12-17 13:19                         ` Corinna Vinschen
2000-12-18 18:13                           ` Charles S. Wilson
2000-12-18 18:15                             ` Robert Collins
2000-12-18 18:42                               ` Christopher Faylor
2000-12-19  4:52                                 ` Corinna Vinschen
2000-12-19  8:11                                   ` Christopher Faylor
2000-12-19  8:47                                     ` Charles S. Wilson
2000-12-19  9:28                                       ` Christopher Faylor
2000-12-19 11:47                                         ` Corinna Vinschen
2000-12-19  6:12 Earnie Boyd
2000-12-19  8:07 ` Larry Hall (RFK Partners, Inc)
2000-12-19 11:44   ` Corinna Vinschen
2000-12-19 17:38 Andrew Dalgleish

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A3180FA.1A97A977@ece.gatech.edu \
    --to=cwilson@ece.gatech.edu \
    --cc=cygwin@cygwin.com \
    --cc=mbresnahan1@mmm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).