From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31555 invoked by alias); 28 Nov 2014 12:48:22 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 31527 invoked by uid 89); 28 Nov 2014 12:48:18 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.0 required=5.0 tests=AWL,BAYES_20 autolearn=ham version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 28 Nov 2014 12:48:16 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 6233C8E1439; Fri, 28 Nov 2014 13:48:14 +0100 (CET) Date: Fri, 28 Nov 2014 16:20:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: RFC: 1.7.33 problem with user's home directory Message-ID: <20141128124814.GM3810@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <20141110205216.GJ2782@calimero.vinschen.de> <0B8D23F7-0258-472D-BF38-860402FD3CDC@etr-usa.com> <20141111101821.GO2782@calimero.vinschen.de> <20141111111437.GB28012@calimero.vinschen.de> <20141126205658.GA9157@calimero.vinschen.de> <20141127170042.GE3810@calimero.vinschen.de> <8610043342.20141128150810@yandex.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Fh+fyCUbzktHKe74" Content-Disposition: inline In-Reply-To: <8610043342.20141128150810@yandex.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2014-11/txt/msg00620.txt.bz2 --Fh+fyCUbzktHKe74 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 2883 On Nov 28 15:08, Andrey Repin wrote: > Greetings, Corinna Vinschen! >=20 > >> The meaning of the schemata depend on the setting: > >>=20 > >> db_home: > >>=20 > >> windows AD and SAM: Utilizes the setting of the homeDrive = or > >> homeDirectory attributes, or their SAM "Home folder" > >> counterparts. The Windows path is converted to a > >> POSIX path. >=20 > > I'm not really happy with this. It requires to write some value to the > > homeDrive/homeDirectory attributes, because it doesn't fall back to the > > Windows default values. >=20 > > So, another question is this: Shall "db_home: windows" fall back > > to the default Windows home dir if homeDrive/homeDirectory are empty? >=20 > Yes, if you mean it. > I mean, if you intend to use the same directory OS using for user's home > directory, you gotta use something that resembles the OS behavior. Good point. It's just a bit lengthy to implement. > >> @ad_attribute AD-only: Read AD attribute "ad_attribute" as POSIX > >> path. > >>=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 > >> However, I'm contemplating to allow a Windows path > >> here, too. Does this make sense to you? >=20 > > I implemented this now. It doesn't hurt. >=20 > Windows path here makes more sense. The translation to POSIX path depends > on the fstab settings, and may vary across different systems, and even > different users, given your aim to make fstab configurable per-user. (Am I > reading it right?) We already have user mount points in /etc/fstab.d. Reading them from AD only changes the point of administration. In many organizations the client machines use a standarized layout anyway. Allowing a DOS path here just adds convenience for admins feeling uncomfortable with POSIX paths. > >> db_shell: > >>=20 > >> windows Ignored. Do you want CMD instead? >=20 > > Would be interesting for symmetry only, I guess... >=20 > With bogus quoting rules of CMD? It would just not work straight, I'm > afraid. May be better with PS, but I'm not familiar with it, and I don't = know > anyone, who's familiar or even considering it's use as a shell interprete= r. Lots of people do. You won't believe in how many scenarios the users use Cygwin tools from CMD. If we implement the above, we would just have to add a cmd wrapper script in /bin to make sure $PATH is set correctly and to make sure CMD starts up in $HOME, something along the lines of: $ cat /bin/cmd #!/bin/dash PATH=3D/bin:$PATH cd $HOME # Don't rely on COMSPEC! cmd=3D$(cygpath -ua "${SYSTEMROOT}\\System32\\CMD.EXE") exec "${cmd}" =20=20 Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --Fh+fyCUbzktHKe74 Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJUeG8OAAoJEPU2Bp2uRE+gwGkP/0hK/DyLB80bj7fTvDww9ERQ OEskkNrEdkS0WM0CF3sZA+V9ozb9gJV1TswpwuhICBrCQjLkJGT0aJnYBKSuXS5p kkPNPeZJuH985lXzixKUyOqOBnOG6EwZCUW02/YfcvHEzkSjydQ3fA7gjPw8O+D5 BaC71VJf76GXu/rS1qUHETce4Li32YBf994kMsT0HGKQ6/KJOg2ARi78IcNTfsqO 9+FJrmmzhecieS5ZYnhQhsCWn9HWktiBeknm/tsmuLv7hpZthZaOFU2WgM1QyN1y OJf1MhCxp5AYGQaDOaeLo0sBRvwLtQXiiPgJgKWE/lDRpsfWhh+595COKU4W2FR9 P1B4Et+UpPV5pXx/kO9tuQ9WlkNnAfP72ZGFphMT6vnabZdji+wv/qx+MCBmv6Af Qyg8LQrTzJQzUZHhPlLiISR6Jcf8bwAD4TsPm1GPAaRRNQP69WSvGrcOMgHB/y8c iTWIpJFllTwRJxCn9Q37YMWoZMCn4MjTrVSAXwV58/gAFTFb6lFJpOjsdpHp2C/m M5XmQ1SlRAlGRvoWpsD/o2AIHQvEPqU4bONtP9g4QCNjdsY3X8cqIwnFhc7c43wZ EHHUbmdDao5uThsgwiBIqXTcjKn15z0yA7uBnV/5vFAHBJBWe1ibNDf0L0XiJCPM 0LVXqruoO+0UgvEfKeNn =TMZh -----END PGP SIGNATURE----- --Fh+fyCUbzktHKe74--