X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: Subject: RE: chown with not existing user/group Date: Thu, 28 Feb 2008 14:28:30 -0000 Message-ID: <008b01c87a16$308a0540$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m1SETEYn001892 On 28 February 2008 13:59, Matthieu CASTET wrote: > Hi, > > I wonder why on cygwin we can't use chown with numeric id that don't exist > in /etc/passwd, /etc/group [1] ? Because it has to emulate unix perms by relating uid/gid to windows RIDs, which are owned, allocated and controlled by the system, and not under the arbitrary choice of the user, so the semantics wouldn't be the same even if we did create ACLs with unrecognised SIDs on them. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/