X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:in-reply-to:references:date:subject :from:to:mime-version:content-type:content-transfer-encoding; q= dns; s=default; b=ureQ7QhybwwRU7nUQ0vKOtkR9Px0Buazt3Qo/7N/sgmd1E CZZ9e0cMnNnIVD2Mom97bMjmOmZelm4+R+K1foADzrxzp+WWOTVduLMCvGiCw+R0 dyqFjn94zuP0nBHFha/lMuZCHSO2vvmi5QPaCtqlxj8XqY9A2TknuGsGzIsJM= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:in-reply-to:references:date:subject :from:to:mime-version:content-type:content-transfer-encoding; s= default; bh=A00+YjFKGqg7SSik7gJqbzZ8B4s=; b=iotcgdz6tNd0WyELU0og Dtr7NR2z7vvDGfPuSuMMwIQum9cF0S3qbUNAr3+VJNCdelNbzQ5l/W/FuKkKe9uf 7m1QFccRqafFh72a1UcHO0ymtwcDzDbQCaXrJGSyqa7HGpUvqS6oRd4ttcW5ivAO FTcOjJXqfakV9nBlShb+Kbg= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: smtp-vbr2.xs4all.nl Message-ID: In-Reply-To: <20141028092812.GE20607@calimero.vinschen.de> References: <20141028092812 DOT GE20607 AT calimero DOT vinschen DOT de> Date: Tue, 28 Oct 2014 10:46:48 +0100 Subject: Re: Why does mkpasswd -c use a different offset? Corinna? From: "Houder" To: cygwin AT cygwin DOT com User-Agent: SquirrelMail/1.4.18 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes > On Oct 28 00:11, Houder wrote: >> Hi Corinna, >> >> I am confused ... the output from mkpasswd -c is NOT the same as the output from mkpasswd -l -u on >> both my "Cygwin-32" and my "Cygwin-64". [snip] >> Please, enlighten me ... > > It's a bug. Funny that this has never been reported before. ... aha, that makes sense. > It shouldn't matter anymore, though, because mkpasswd is changing > significantly with 1.7.33. I would suggest to take a look into the > current test release 1.7.33-0.3. The mkpasswd command will produce > the same uid and gid values as the values generated by the Cygwin > DLL in "db" mode to avoid collisions. Aha ... I have already replaced the cygwin1.dll (on my Cygwin-32) with the one from the snapshot ... apparently, that is not sufficient ... Thank you very much for your clarification! Henri ===== -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple