From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: cyg Simple <cygsimple@gmail.com>
Subject: RE: Ability to specify /cygdrive mount value in setup
Date: Wed, 25 Nov 2015 19:17:00 -0000 [thread overview]
Message-ID: <6CF2FC1279D0844C9357664DC5A08BA21BC3C014@msgb09.nih.gov> (raw)
In-Reply-To: <452598469.20151125193908@yandex.ru>
Andrey Repin sent the following at Wednesday, November 25, 2015 11:39 AM
>On 11/25/2015 10:56 AM, cyg Simple wrote:
>> I find /cygdrive/ just unbearable and I always change it to / after an
>> install. The issue with this is that post install activities will
>> create symlinks using /cygdrive moniker so I must go change those if I
>> find them.
>
>Just which activities? I haven't seen any. And I do remap /cygdrive to /
>at all times.
I grepped everything in and under /etc for cygdrive. The only hits were
/etc/fstab and /etc/postinstall/000-cygwin-post-install.sh.done, and the
latter was just setting up the former. So I have to ask, what's creating
these shortcuts?
The idea that setup or the post-install scripts create symlinks that
point to things that are not under / and need to be accessed as, for
example, /cygdrive/d (= D:\) seems very strange.
>> Would it be possible for setup to ask for the value and
>> setup the /etc/fstab with the value? Do others find this bit of annoying?
>
>You can precreate fstab, I think.
Maybe you could do a 3-step install?
- minimal install.
- fix fstab.
- install optional packages.
Another (partially tested) idea: Create a folder in / named /cygdrive.
Then create a symlink in it for each drive, where the symlink points to
the drive and is named as the drive letter. That seems to work for
some purposes, e.g., cd /cygdrive/d/dir/ goes to /d, though the CWD will
be /cygdrive/d/dir, not /d/DIR. YMMV.
But pre-creating c:\cygwin\etc\fstab seems like the best option.
Good Luck.
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
--
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
next prev parent reply other threads:[~2015-11-25 19:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 16:24 cyg Simple
2015-11-25 16:50 ` Eliot Moss
2015-11-25 17:39 ` Andrey Repin
2015-11-25 19:17 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
2015-11-25 18:51 ` Roger Wells
2015-11-25 19:06 Charlie
2015-11-25 20:35 ` Andrey Repin
2015-11-25 21:01 ` cyg Simple
2015-11-25 22:44 ` Buchbinder, Barry (NIH/NIAID) [E]
2015-11-26 13:52 ` Corinna Vinschen
2015-11-26 18:06 ` Achim Gratz
2015-11-26 20:08 ` Corinna Vinschen
2015-11-29 18:25 ` cyg Simple
2015-11-29 20:15 ` cyg Simple
2015-12-06 9:47 ` Achim Gratz
2015-12-06 14:10 ` Corinna Vinschen
2015-12-06 14:28 ` Achim Gratz
2015-12-06 17:01 ` cyg Simple
2015-12-06 17:16 ` Achim Gratz
2015-12-06 17:12 ` Achim Gratz
2015-12-06 19:02 ` Corinna Vinschen
2015-12-06 19:07 ` Achim Gratz
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=6CF2FC1279D0844C9357664DC5A08BA21BC3C014@msgb09.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--cc=cygsimple@gmail.com \
--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).