On Feb 14 11:48, Corinna Vinschen wrote: > On Feb 14 11:16, Frank Fesevur wrote: > > I've installed that snapshot on my work laptop, part of AD domain. I > > moved passwd and group out of the way and noticed my .bashrc is not > > executed. > > [...] > > Most noticeable difference between the two are in the dates of the > > files (The months are in Dutch, and not in "long-iso") and not showing > > the dot-files. Among others, I have set an export LANG=en_US > > ...hopefully LANG='en_US.utf8"... > > > and an > > alias for "ls" in my bashrc for that. > > Hmm, off the top of my head I can't explain this. Is that > via mintty or a Windows console? What does `id' print? Is there a > difference in upper/lower case of your name? > > [...time passes...] > > Oh, hang on. I'm a tcsh gal, so I set /bin/tcsh in my AD domain entry. > However, the default is *not* /bin/bash, but /bin/sh at the moment. I'm > a bit fuzzy on bash, but does bash read the .bachrc file only if it's > called bash and not if it's called sh? What happens if you symlink > your .bashrc to .profile (Not that I suggest this as the ultimate > solution, this is just for testing)?
Ultimately, the right thing to do is either: - We switch Cygwin to use /bin/bash as default, instead of /bin/sh, - or, you ask your admin to set the "loginShell" attribute of your AD entry to "/bin/bash". Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat
pgpBZJwky_mbr.pgp
Description: PGP signature
