public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mike Rushton <mrushton@ptd.net>
To: David Conrad <DavidConrad@acm.org>, cygwin@cygwin.com
Subject: Re: Newbie Cygdrive questions
Date: Fri, 07 Feb 2014 00:35:00 -0000	[thread overview]
Message-ID: <52F42A49.4000806@ptd.net> (raw)
In-Reply-To: <CAEotdwkNuNhGS+Kf2ztAQW=pDPoqo610c35iOU2x9fjBEfURnw@mail.gmail.com>

That is good to know about that utility Cygpath.   Maybe I will try it.

What I was doing was going thru some scripts ... changing the paths ... 
clean in up stuff ...
over the years I ended up with a lot of commented out sections of code 
... and testing them.



And this is a different approach that I never would have thought of.

/l/<whatever>

or

/nfs/<whatever>



Thanks.


On 2/6/2014 5:37 PM, David Conrad wrote:
> It may be useful to know, if you do not already, that the cygpath
> utility can be used to convert between Windows and Unix paths.
>
> cygpath -u X:/INBOUND/CWSCRIPTS/myscript.sh
>
> will give you /cygdrive/x/INBOUND/CWSCRIPTS/myscript.sh, and
>
> cygpath -w /cygdrive/x/INBOUND/CWSCRIPTS/myscript.sh
>
> will give you X:\INBOUND\CWSCRIPTS\myscript.sh
>
> You can also use cygpath -m if you prefer forward slashes, even in
> your Windows paths.
>
>
> On Thu, Feb 6, 2014 at 3:03 PM, Richard <richard@karmannghia.org> wrote:
>> On Thu, 6 Feb 2014, mrushton wrote:
>>>
>>> To access this shared X drive under Cygwin it seems I have to do this :
>>>
>>> /cygdrive/X/INBOUND/CWSCRIPTS/myscript.sh
>>>
>>>
>>> Is this correct ?  Is there a better way ?
>>>
>>> And C: seems to be /cygdrive/C/
>>>
>> A BETTER way?
>>
>> This has nothing per se to do with Cygwin, but, briefly:
>>
>> Standardize all your systems on something YOU can control. For example, I
>> always create a top-level directory called l (that's the letter, not the
>> numeral) which stands for "local", and another called nfs, which simply
>> means a remote mount - could be real nfs or Samba - and then make links
>> within these directories to wherever they need to go. That way, all disk
>> space is available via either:
>>
>> /l/<whatever>
>>
>> or
>>
>> /nfs/<whatever>
>>
>> as appropriate.
>>
>> And there's never any confusion over which is which - and drive letters can
>> be completely avoided as desired, or not.
>>
>> ...All (many!) good System Administrators do things similar to this...
>>
>> Richard
>>
>>
>> --
>> 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
>>


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

  reply	other threads:[~2014-02-07  0:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2016125559.9964201.1391712687754.JavaMail.root@ptd.net>
2014-02-06 18:53 ` mrushton
2014-02-06 19:00   ` Larry Hall (Cygwin)
2014-02-06 19:53   ` Richard
2014-02-06 22:37     ` David Conrad
2014-02-07  0:35       ` Mike Rushton [this message]
2014-02-07  0:50   ` Andrey Repin
2014-02-07  1:05     ` Mike Rushton
2014-02-07  3:09       ` Larry Hall (Cygwin)
2014-02-07  3:52         ` Mike Rushton
2014-02-07 13:05           ` Andrey Repin
2014-02-07 13:05       ` Andrey Repin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52F42A49.4000806@ptd.net \
    --to=mrushton@ptd.net \
    --cc=DavidConrad@acm.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).