From: Andrey Repin <anrdaemon@yandex.ru>
To: kuaf <kuaf.lee@gmail.com>, cygwin@cygwin.com
Subject: Re: Why not generate the .bashrc automatically under home diretory
Date: Tue, 25 Aug 2015 09:20:00 -0000 [thread overview]
Message-ID: <682862844.20150825120821@yandex.ru> (raw)
In-Reply-To: <CAFLqW4M0OJUnkDsdh_oYfU+3p-B5n8TbLNotTv6wNtfHQiUA-w@mail.gmail.com>
Greetings, kuaf!
> I used the latest [setup-x86_64.exe][1] to set up cygwin environment.
> I wanted my /home directory to point to c:\Users rather than the
> out-of-the-box home directory created by cygwin.
> My current solution is to just mount it in fstab with the following line:
> c:/Users /home ntfs binary,posix=0,nouser
And what if your profile directory name doesn't match your profile name?
Do it the right way.
/etc/nsswitch.conf:
passwd: db
group: db
db_home: desc windows
Oh, and don't forget 'noacl' on /cygdrive.
It is a VERY bad idea to stomp your profile directory with strict POSIX
permissions. Not every application is ready to accept them, you may even lose
the ability to open documents through associations.
> After refresh installing and change the fstab above, then startup mintty.
> But, I didn't see .bashrc/.profile/.inputrc/.bash_profile was
> generated automatically under home directory. I mean the `/etc/skel/*`
> files would be copied to home direcotry.
This is a standard POSIX behavior, if user directory exists, it will never be
touched. If you need the skeleton files updated, you can do it yourself.
If you need default files distributed, place them into default user profile.
--
With best regards,
Andrey Repin
Tuesday, August 25, 2015 12:01:57
Sorry for my terrible english...
--
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:[~2015-08-25 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 8:47 kuaf
2015-08-25 9:20 ` Andrey Repin [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=682862844.20150825120821@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=kuaf.lee@gmail.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).