X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_THEBAT,KHOP_THREADED,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Date: Thu, 18 Oct 2012 16:01:20 +0400 From: Andrey Repin Reply-To: Andrey Repin Message-ID: <18766546.20121018160120@mtu-net.ru> To: Gary Oberbrunner , cygwin AT cygwin DOT com Subject: Re: Mount Windows C drive as POSIX root? In-Reply-To: <367252125.299475.1350524677090.JavaMail.root@genarts.com> References: <367252125 DOT 299475 DOT 1350524677090 DOT JavaMail DOT root AT genarts DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 Greetings, Gary Oberbrunner! > Thanks for the replies, cygwin people! > ----- Original Message ----- >> From: "Andrey Repin" > ... >> >> > I understand about not installing cygwin in c:\. But I really want >> > a single >> > filesystem, so cygwin's / is Windows c:/, and cygwin /Program\ >> > Files is >> > Windows /Program Files and so on. >> >> Having single filesystem, and having cygwin mounted on root is not >> the same. > Sorry, I was not clear -- I mean the same filesystem between cygwin and > Windows. And I only care about the C drive (I've learned to keep everything > there). That's generally bad practice. But up to you, I suppose. >> > I have an environment with lots of non-cygwin tools and translating >> > paths between them is not workable. >> >> Especially not the same, when you start to interoperate with >> non-cygwin applications, and when you start to update your Cygwin installation. >> >> Heed my suggestion, don't do it. > Well, it's worked pretty well for me for the last 10 years. :-) > Of course I've also learned not to update my cygwin. :-) >> First, it just wrong. And were causing infinite grief in the past. >> So, Cygwin >> maintainers changed scheme to force some mounts off of cygwin1.dll >> location. > Can you say more about this? > ... >> Guess, what? It didn't worked well past the HDD mounts. > Correct -- I don't care about that (D drive etc.). What I do care about is > being able to mix cygwin command line tools with non-cygwin. For example, > Intel compiler. Or (non-cygwin) python. I'm really used to being able to say > # ls /my/path/foo.py > # python !$ > or > # vim /my/path/foo.cc (cygwin) > # icl -c !$ (non-cygwin) > and have it just work, like on Linux. Not have to translate paths around > and remember which utility is cygwin-based and which isn't. (I'm old, and > seem to have become a serious command-line Windows hacker, but I'm still > really a Unix guy.) As I said, if switching root folder works for you, you can make junctions back to C:\ from Cygwin installation and have it work straights. -- WBR, Andrey Repin (anrdaemon AT freemail DOT ru) 18.10.2012, <15:59> 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