X-Recipient: archive-cygwin@delorie.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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=K1AegyOZMUGCgGfh
	yQbCJ0Uy4jiRqUOQakB1xtZsKSSRkfRoHfnDjOBKOBRx10qn+2Rccv57yEi0gYoa
	GrUQfs8U3B//Jb+Ck9TKKaT3Ue1hpIlMFiwW0dFQzbHhElcHPisCOZjzJlQij+RG
	o+4Z0HIAETUDT93NOl833aL8NqQ=
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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=pxuPeBYZLxpVQVxKp75O4j
	tBMRk=; b=ATLbGgOFGU3IKTpdmnpA90ZN1Wmpz+OmlvA9v4QP9pwBIM1bRAiNWm
	MODd3wPfrtvxDJ0PpGcZxBmI0kUnY+Ezn1FDHakjwUW2QLqKqRTp6xT78lfJNC7B
	UaSvT/FOTAbSt9QB5Qm6a+83U/wy59W0sRvXnd6ebKBxZhSPfXQnE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=4.2 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_THEBAT,SPF_SOFTFAIL autolearn=no version=3.3.2
X-HELO: smtp.ht-systems.ru
Date: Thu, 24 Sep 2015 21:33:00 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <836812111.20150924213300@yandex.ru>
To: Linda Walsh <cygwin@tlinx.org>, cygwin@cygwin.com
Subject: Re: Issues encountered with new Cygwin version
In-Reply-To: <56042985.2040104@tlinx.org>
References: <BLU182-W10FB6B21A2AEC90F71470FD4450@phx.gbl>   <154887677.20150923111537@yandex.ru>  <BLU182-DS2B4F831FEB7E4C1B67330D4440@phx.gbl> <56036256.8080209@tlinx.org>  <BLU182-DS2567923242507AF88D9315D4430@phx.gbl> <56037F66.40209@tlinx.org>  <BLU182-DS177F609D3B4BC69A880C77D4430@phx.gbl> <56042985.2040104@tlinx.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

Greetings, Linda Walsh!

>>> > > > > I believe the target of the symlink should be "protocol" (i.e.

>>> How would that affect 'services'?
>> 
>> Sorry, you lost me. 'services' has 8 characters in the file name and so is
>> its symlink target; That shouldn't be an issue. Of the 4 symlinks under
>> /etc/ (i.e. networks, hosts, services, and protocols), only 'protocols'
>> exceeds the 8 character limit and hence the actual target file in
>> Windows/System32/drivers/etc/ is 'protocol'. NOTE: I'm talking about the
>> *target* file not the symlinks themselves, which are fine.
> ---

> Oops.. my bad -- don't know why I substituted services. However,
> weren't those files there for unix-subsystem support?  Not sure:

> From this:

> https://books.google.com/books?id=6hlNFc7drzEC&pg=PA39&lpg=PA39&dq=reason+for+drivers/etc/protocol+on+windows&source=bl&hl=en&sa=X&q=reason%20for%20drivers%2Fetc%2Fprotocol%20on%20windows&f=false#v=snippet&q=reason%20for%20drivers%2Fetc%2Fprotocol%20on%20windows&f=false
> (page 39) -- it says those files were specific to NT systems beginning with
> NT4.0, which used NTFS.  I don't know if NT supported having the windows/system32
> directory on FAT][32]...

It did.
Read the help article about "convert" tool for more info.

> NT4 would have been the version before Windows 2000

Aye.


-- 
With best regards,
Andrey Repin
Thursday, September 24, 2015 21:32:08

Sorry for my terrible english...


--
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

