From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: HOME when using both cygwin and cygwin64
Date: Fri, 26 Feb 2016 12:33:00 -0000 [thread overview]
Message-ID: <56D0460A.2040303@cs.umass.edu> (raw)
In-Reply-To: <56D00B19.209@gmail.com>
On 2/26/2016 3:21 AM, Marco Atzeri wrote:
> On 26/02/2016 05:18, Eliot Moss wrote:
>> Dear Cygwin-ers -- I solicit suggestions around the following.
>> For a long time I have used cygwin (32 bit) almost exclusively,
>> and in that universe my home directory is /home/moss, which in
>> Windows land is C:\cygwin\home\moss. Now I also have cygwin64
>> installed under C:\cygwin64, with another home directory there,
>> C:\cygwin64\home\moss. When I start a 64-bit bash in a 64-bit
>> xterm, HOME gets set to /cygdrive/c/cygwin/home/moss. Does
>> this seem right? It seems counter-intuitive to me -- should
>> it not be /home/moss, namely C:\cygwin64\home\moss? If that
>> would be better (I think so), how can I best achieve it?
>>
>> Regards -- Eliot Moss
>>
>
> The default is /home/$USERNAME
> https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-passwdinfo
>
> If it is different you modified it in some way
Indeed, you are right. If I start cygwin64 from its installed .bat
file, I get a Cygwin terminal with HOME as /home/moss, under the
C:\cygwin64 Cygwin root. So it is something about starting using
my (32 bit) .XWinrc. Presumably the 32-bit HOME is being passed
as an environment variable. The trick will be to get it unset
so that the 64-bit bash uses its own /home/moss. I think I'll
have to play with the .XWinrc more to figure that out.
Regards -- EM
--
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
prev parent reply other threads:[~2016-02-26 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 4:18 Eliot Moss
2016-02-26 7:05 ` Andrey Repin
2016-02-26 8:21 ` Marco Atzeri
2016-02-26 12:33 ` Eliot Moss [this message]
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=56D0460A.2040303@cs.umass.edu \
--to=moss@cs.umass.edu \
--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).