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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=NkRthgzlhrV49CHm QvoLwrRKYuuqIq1lh0dr8ogZj1DWpA06XRuNcW8Q7WyUpVkMW15KDqeEV8uvhaGi +mmSBPuaLSyKlvWWJxT2x6UqBOPfBfYB9EGKZJQ3X9/+ncbhYK/dfnXehSfRjciC MuR0T14b8tjmrTg5Bga43/AmW6A= 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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=bYfTwok2FLAUzTXB4SqBd6 HEOaQ=; b=J0rBr9IYAMrn5lNogZW5JM68a40StY8nH61M0iSnBRvFHuo0V0lySd An6uySz9tAb7w7SfIfMkuND3wPsKnP1jrXG7cAq/sXzAwAtqUjHlUBE19cLif4H/ usril6p8sL9b6vhj3sCyiLzltEV26JkdFLcrr0utO5Kqm0NjO1e08= 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-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=disturbing, H*Ad:D*ca, H*R:D*ca, calgary X-HELO: smtp-out-so.shaw.ca Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.0.0-0.2 To: cygwin AT cygwin DOT com References: <5f727fe5-1c98-3fb5-30f3-9cb1120d4aa4 AT SystematicSw DOT ab DOT ca> <20190130173104 DOT GK3912 AT calimero DOT vinschen DOT de> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <0dd6e7ce-a503-e181-97a3-0d6e289251e5@SystematicSw.ab.ca> Date: Wed, 30 Jan 2019 11:47:02 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 MIME-Version: 1.0 In-Reply-To: <20190130173104.GK3912@calimero.vinschen.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 2019-01-30 10:31, Corinna Vinschen wrote: > On Jan 30 09:11, Brian Inglis wrote: >> On 2019-01-30 07:03, Corinna Vinschen wrote: >>> I uploaded a new Cygwin test release 3.0.0-0.2 >>> It also changes the output of uname(2) for newly built applications. >>> Applications built so far (that includes uname(1) from coreutils) >>> will still print the old uname output. The new format allows for longer >>> strings. Compare: >>> Upcoming new uname content: >>> sysname: CYGWIN_NT-10.0-17763 or CYGWIN_NT-10.0-17763-WOW64 >>> release: 3.0.0-335.x86_64 or 3.0.0-335.x86_64.snap >>> version: 2019-01-29 19:23 UTC Build time in UTC >> Re: "(*) It would really be nice not having to ask for these infos every time." >> may want to append HKLM/SOFTWARE/Microsoft/Windows NT/CurrentVersion/UBR to >> uname -s sysname to show the patch levels of installed builds, as there appears >> to be substantial differences between editions and service models. > Thanks for the info, but what to do with this? Is there a thorough > description somewhere to allow deciphering what this means to us? UBR Update Build Revision appears to be incremented for each patch set released for the W10 feature set OS build, to complete a unique revision id, similar to Cygwin 335 above. Would save those of us who know to, having to also run and append the output of $ cmd /c ver Microsoft Windows [Version 10.0.17134.523] and save asking those who don't know that, in case the revision makes a difference. Insider build feature sets bump the builds, and patch sets bump those revisions; up to base releases with known feature sets, builds, and revisions; then patch Tuesdays bump those revisions higher; so you can tell if installs are Insider, base, or patched. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- 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