public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Cheuk Cheng" <cheng@powertv.com>
To: "Peter Buckley" <peter.buckley@cportcorp.com>, <cygwin@cygwin.com>
Subject: RE: mounts in gnupro99r1p1
Date: Wed, 18 Jul 2001 14:03:00 -0000	[thread overview]
Message-ID: <NEBBLBOGPKDNAIGFLLOJGELFCJAA.cheng@powertv.com> (raw)
In-Reply-To: <50A89B19AEAAD411B9D200A0C9FB5699E88DD0@craius.cportcorp.com>

Thanks.  What is /usr/local/bin pointing to?  How about /usr/local,
/usr/cygnus and /cygdrive?  I am confused about what are they used for and
what should they point to?  Are they needed in general or only for specific
tools?

-----Original Message-----
From: Peter Buckley [ mailto:peter.buckley@cportcorp.com ]
Sent: Wednesday, July 18, 2001 1:24 PM
To: 'Cheuk Cheng'; cygwin@cygwin.com
Subject: RE: mounts in gnupro99r1p1


Cygwin tools would be located in c:\cygwin\bin,
if you install in the default location.
Cygwin prepends

/usr/local/bin:/usr/bin:/bin:/usr/sbin

to your path, and the mounts
would be-

c:\cygwin\bin to /usr/bin
c:\cygwin to /
c:\cygwin\usr\sbin to /usr/sbin

If you set your path system or user variable,
you can use cygwin/gnupro from other shells
than the bash shell. I have in my system PATH
variable on NT-

%the typical path%;C:\cygwin\bin

so I can use cygwin from emacs and dos without
opening a bash shell.
You can enter whatever location your gnupro
tools are, and your cygwin tools, without
worrying about mount.

HTH,
Peter

-----Original Message-----
From: Cheuk Cheng [ mailto:cheng@powertv.com ]
Sent: Wednesday, July 18, 2001 4:16 PM
To: cygwin@cygwin.com
Subject: mounts in gnupro99r1p1


I am new to GNU and am confused about how to set up device mounts in
general.  I use the following with the Cygwin I recently get from the web.
I also have gnupro99r1p1 installed under d:\cygnus\gnupro99-r1p1.  When I
run the default gnupro.bat file created by the gnupro99r1p1 installer, it
just opens a DOS window within Win2k.  Since the installer put certain
command line tools like ls.exe, bash.exe, etc. under
d:\cygnus\unsupported-99r1\H-i686-cygwin32\bin while other programs like
gcc.exe are placed into d:\cygnus\gnupro-99r1p1\H-i686-cygwin32\bin.  As a
result, entering ls after running bash.exe does not work.  My questions are
what mounts/paths does Cygwin used to locate a tool?  Do I always need to
mount /, /usr/bin, /usr/lib, /usr/local and /usr/cygnus?  What should they
normally be set to (especially gnupro99r1p1 has two different directories
for storing the tools)?

d:\cygnus\latest\bin on /usr/bin type user (binmode)
d:\cygnus\latest\lib on /usr/lib type user (binmode)
d:\cygnus\latest on / type user (binmode)
d:\cygnus\latest on /usr/local type user (textmode)
d:\cygnus\latest on /usr/cygnus type user (binmode)
c:\temps on /tmp type user (textmode)
c: on /c type user (textmode)
d: on /d type user (textmode)
e: on /e type user (textmode)
g: on /g type user (textmode)
k: on /cygdrive/k type user (binmode,noumount)
m: on /cygdrive/m type user (binmode,noumount)
n: on /cygdrive/n type user (binmode,noumount)
u: on /cygdrive/u type user (binmode,noumount)


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

  reply	other threads:[~2001-07-18 14:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-18 13:25 Peter Buckley
2001-07-18 14:03 ` Cheuk Cheng [this message]
2001-07-18 14:12   ` Larry Hall (RFK Partners, Inc)
  -- strict thread matches above, loose matches on Subject: below --
2001-07-12 12:45 Running Dejagnu under Cygwin Cheuk Cheng
2001-07-18 13:16 ` mounts in gnupro99r1p1 Cheuk Cheng
2001-07-18 16:30   ` Christopher Faylor
2001-07-18 16:42     ` Cheuk Cheng
2001-07-18 16:54       ` Michael A. Chase

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=NEBBLBOGPKDNAIGFLLOJGELFCJAA.cheng@powertv.com \
    --to=cheng@powertv.com \
    --cc=cygwin@cygwin.com \
    --cc=peter.buckley@cportcorp.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).