Greetings, Corinna Vinschen!
> On Nov 28 19:08, Andrey Repin wrote:
>> > 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
On Nov 28 10:11, Corinna Vinschen wrote:
> On Nov 28 09:24, Houder wrote:
> > Test:*:197614:197121:Test,U-Seven\Test,S-1-5-21-91509220-1575020443-2714799223-1006:/home/Test:/bin/bash
> > < gecos field has THREE members (iso two)
>
> For the gecos content, it's created
On Nov 21 15:43, Corinna Vinschen wrote:
> I'm going to take a step back for now, and reevaluate what happens
> before trying to apply even more hacks. Ultimately the problem is that
> the cygtls area is accessed from other threads (mainly the signal
> thread) without locking, and worse, that the
On 2014-11-21 14:36, Corinna Vinschen wrote:
On Nov 21 14:06, Yaakov Selkowitz wrote:
On 2014-11-21 10:06, Corinna Vinschen wrote:
On Nov 21 16:50, Marco Atzeri wrote:
On 11/21/2014 3:43 PM, Corinna Vinschen wrote:
On 32-bit. The rebuild of cygwin1.dll requires large number of packages to
cre
On 2014-11-28 03:32, Andrey Repin wrote:
>
> Look, this happens, when you are not reading documentation...
> Or, if you're in a hurry, the 'noacl' mount flag is what you are looking for.
You are totally right. The part of documentation that i have missed is in
https://cygwin.com/cygwin-ug-net/u
On Nov 28 17:17, Achim Gratz wrote:
> Corinna Vinschen writes:
> > I don't grok that. If you chmod one of your own files 070 or 060, and
> > then try to read it, you get a permission denied error. This is
> > perfectly ok from a POSIX POV. The problem here is, why does our own
> > libapr chmod t
On Nov 28 19:08, Andrey Repin wrote:
> > 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=/bin
Greetings, Corinna Vinschen!
>> >> The meaning of the schemata depend on the setting:
>> >>
>> >> db_home:
>> >>
>> >> windows AD and SAM: Utilizes the setting of the homeDrive or
>> >> homeDirectory attributes, or their SAM "Home folder"
>> >> c
Corinna Vinschen writes:
> I don't grok that. If you chmod one of your own files 070 or 060, and
> then try to read it, you get a permission denied error. This is
> perfectly ok from a POSIX POV. The problem here is, why does our own
> libapr chmod to 070 at all? If libapr does it, and if this
On Nov 28 15:08, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> >> The meaning of the schemata depend on the setting:
> >>
> >> db_home:
> >>
> >> windows AD and SAM: Utilizes the setting of the homeDrive or
> >> homeDirectory attributes, or their SAM "Hom
Greetings, Corinna Vinschen!
>> db_shell:
>>
>> windows Ignored. Do you want CMD instead?
> Would be interesting for symmetry only, I guess...
Adding to that: Cygwin shell is supposed to have access to Cygwin commands.
Running foreign shell may just get the user stuck in the midd
Greetings, Corinna Vinschen!
>> The meaning of the schemata depend on the setting:
>>
>> db_home:
>>
>> windows AD and SAM: Utilizes the setting of the homeDrive or
>> homeDirectory attributes, or their SAM "Home folder"
>> counterparts. The Win
> On Nov 28 10:34, Houder wrote:
>> > On Nov 28 09:24, Houder wrote:
>> >> Test:*:197614:197121:Test,U-Seven\Test,S-1-5-21-91509220-1575020443-2714799223-1006:/home/Test:/bin/bash
>> >> < gecos field has THREE members (iso two)
>> >
>> > For the gecos content, it's cre
On Nov 28 10:34, Houder wrote:
> > On Nov 28 09:24, Houder wrote:
> >> Test:*:197614:197121:Test,U-Seven\Test,S-1-5-21-91509220-1575020443-2714799223-1006:/home/Test:/bin/bash
> >> < gecos field has THREE members (iso two)
> >
> > For the gecos content, it's created no
> On Nov 28 09:24, Houder wrote:
>> Test:*:197614:197121:Test,U-Seven\Test,S-1-5-21-91509220-1575020443-2714799223-1006:/home/Test:/bin/bash
>> < gecos field has THREE members (iso two)
>
> For the gecos content, it's created not the same way in Cygwin vs.
> mkpasswd a
On Nov 28 09:24, Houder wrote:
> Test:*:197614:197121:Test,U-Seven\Test,S-1-5-21-91509220-1575020443-2714799223-1006:/home/Test:/bin/bash
> < gecos field has THREE members (iso two)
For the gecos content, it's created not the same way in Cygwin vs.
mkpasswd and this w
On Nov 27 23:31, Denis Excoffier wrote:
> Hello,
>
> I'm asking for advice because i don't know how to handle this.
>
> I have access to an svn repository through the "file:" protocol. The
> svn repository is homed on an ntfs disk, with all ACL permissions
> inherited from a top directory: variou
Hi Corinna,
For a rainy day ... really ;-)
Although you think about mkpasswd/mkgroup as mere helper tools (in the "future"
release of Cygwin),
I would like to draw your attention to some pecularities in the output of these
programs.
Note: mkpasswd/mkgroup were extracted from the latest snapsho
18 matches
Mail list logo
