From: Thomas Schweikle <tschweikle@bfs.de>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Changing user home to overlap Windows user home possible? Or a bad idea?
Date: Fri, 7 Apr 2023 20:48:58 +0000 [thread overview]
Message-ID: <5eae9f1f-9d58-d8a1-cf43-e6eeb77c7e1b@bfs.de> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 431 bytes --]
Hi!
Is it possible to have the same home for Windows and cygwin? Using
"C:\Users\<user>" for Cygwin home setting mount points for users?
Or is this a bad idea? Or is it something which has some drawbacks
you've to decide to live with? At the moment the most ugly drawback is
duplication of various data needed within "C:\cygwin\home\<user>" and
"C:\Users\<user>". Would be nice if I could overlay both.
--
Thomas
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2521 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 321 bytes --]
next reply other threads:[~2023-04-07 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 20:48 Thomas Schweikle [this message]
2023-04-08 8:30 ` Andrey Repin
2023-04-11 20:42 ` Thomas Schweikle
2023-04-11 22:16 ` 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=5eae9f1f-9d58-d8a1-cf43-e6eeb77c7e1b@bfs.de \
--to=tschweikle@bfs.de \
--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).