Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Fri, 10 Jan 2003 20:45:43 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Repost, different list...File::Spec, cygwin, Syntactic vs. Semantic path analysis Message-ID: <20030111014543.GB7720@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3E1F113F DOT 1080002 AT cotagesoft DOT com> <003501c2b8ff$89206c90$1403a8c0 AT sc DOT tlinx DOT org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003501c2b8ff$89206c90$1403a8c0@sc.tlinx.org> User-Agent: Mutt/1.5.1i One would have to wonder... On Fri, Jan 10, 2003 at 03:25:17PM -0800, LA Walsh wrote: >Interesting...wonder why they wouldn't just create pseudo devices >in /dev and do the normal unix mount thing? Seems odd to complicate the simple >namespace model needlessly by adding a special syntax. > >Even still, just because one wants to have more traditional unix names doesn't >preclude the possible design goal of backward compatibility with >existing Win32 pathnames to aid in portable tool usage and design. > >Even a hard coded /smb/ or /smb:/ prefix on smb shares would be >a better choice that "//". Why perpetuate the MS view of >SMB being 'special' vs. using an eventual mounting syntax that would >allow it to coexist with /nfs/ type files? If the mount system evolved >enough in cygwin, then I could see mount allowing specification of >'nfs' in a mount command -- either as a link to an MS-nfs method >(assuming they were supply one) or cygwin-based NFS methods like the >universal NFS server... > >-linda > > >> Cygwin predates RedHat. See http://cygwin.com/history.html (the >> earliest date in the file is Dec 1995). RedHat bought Cygnus >> Solutions >> (which was a shop for commercial support for GNU software, especially >> GCC ports to obscure and new platforms), which did the >> original Cygwin work. >> >> Anyone at RedHat from the original Cygwin team (the last >> warriors of the >> (in)famous "Beta 20" :-)?) wanna answer this? >> >> There's an interesting line in the early changelogs: >> >> Release Beta 8 >> [...] >> Much nicer way of describing paths, eg //c/foo is c:\foo. >> >> Suggests that the early goal *was* to provide a POSIX-y view, and the >> exposing of Windows paths was added as a convenience.. >> >> > > >-- >Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple >Bug reporting: http://cygwin.com/bugs.html >Documentation: http://cygwin.com/docs.html >FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/