On 10/12/14 20:52, cyg Simple wrote:
On Fri, Dec 5, 2014 at 4:05 PM, Andrey Repin wrote:
Greetings, Corinna Vinschen!
I'd appreciate if those not shy to install developer snapshots would
give this stuff a try in the meantime.
I think I'm about to make a script to install snapshots, at this ra
Greetings, cyg Simple!
> On Fri, Dec 5, 2014 at 4:05 PM, Andrey Repin wrote:
>> Greetings, Corinna Vinschen!
>>
> I'd appreciate if those not shy to install developer snapshots would
> give this stuff a try in the meantime.
I think I'm about to make a script to install snapshot
On Fri, Dec 5, 2014 at 4:05 PM, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
>>> > I'd appreciate if those not shy to install developer snapshots would
>>> > give this stuff a try in the meantime.
>>>
>>> I think I'm about to make a script to install snapshots, at this rate it
>>> seems
>>
On Dec 6 00:05, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> >> > I'd appreciate if those not shy to install developer snapshots would
> >> > give this stuff a try in the meantime.
> >>
> >> I think I'm about to make a script to install snapshots, at this rate it
> >> seems
> >> the r
Greetings, Corinna Vinschen!
>> > I'd appreciate if those not shy to install developer snapshots would
>> > give this stuff a try in the meantime.
>>
>> I think I'm about to make a script to install snapshots, at this rate it
>> seems
>> the right thing to do.
>> Is there a direct way to query f
On Dec 5 08:28, Andrey Repin wrote:
> >> On Nov 11 12:14, Corinna Vinschen wrote:
> >> The new stuff is still missing documentation, [...]
>
> > If you're wondering why I didn't create a test release yet, it's all
> > about this dreaded documentation.
>
> > Did I mention already how much I hate
Greetings, Corinna Vinschen!
>> On Nov 11 12:14, Corinna Vinschen wrote:
>> > On Nov 11 11:05, Achim Gratz wrote:
>> > > Corinna Vinschen cygwin.com> writes:
>> > > > 1. Add a setting to /etc/nsswitch.conf which allows to specify one of
>> > > > the above:
>> > > >
>> > > > home: [unix|win
On Nov 26 21:56, Corinna Vinschen wrote:
> On Nov 11 12:14, Corinna Vinschen wrote:
> > On Nov 11 11:05, Achim Gratz wrote:
> > > Corinna Vinschen cygwin.com> writes:
> > > > 1. Add a setting to /etc/nsswitch.conf which allows to specify one of
> > > > the above:
> > > >
> > > > home: [unix
On Dec 4 04:20, Linda Walsh wrote:
> Andrey Repin wrote:
> >Greetings, cyg Simple!
> Don't forget that CMD will not create a second connection to a
> \\host\share if Cygwin already has one open.
> >>>What do you mean by that?
> >
> >>$ cd //somehost/someshare
> >>$ cmd /c start cmd
> >
> >
Andrey Repin wrote:
Greetings, cyg Simple!
Don't forget that CMD will not create a second connection to a
\\host\share if Cygwin already has one open.
What do you mean by that?
$ cd //somehost/someshare
$ cmd /c start cmd
cmd will complain about UNC paths and start in %WINDIR% instead.
-
Greetings, cyg Simple!
> On Tue, Dec 2, 2014 at 12:29 AM, Andrey Repin wrote:
>> Greetings, cyg Simple!
>>
>>> Don't forget that CMD will not create a second connection to a
>>> \\host\share if Cygwin already has one open.
>>
>> What do you mean by that?
> $ cd //somehost/someshare
> $ cmd /c sta
On Tue, Dec 2, 2014 at 12:29 AM, Andrey Repin wrote:
> Greetings, cyg Simple!
>
>> Don't forget that CMD will not create a second connection to a
>> \\host\share if Cygwin already has one open.
>
> What do you mean by that?
$ cd //somehost/someshare
$ cmd /c start cmd
cmd will complain about UNC
On Nov 28 13:48, Corinna Vinschen wrote:
> 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
> > >>
Greetings, cyg Simple!
> Don't forget that CMD will not create a second connection to a
> \\host\share if Cygwin already has one open.
What do you mean by that?
--
WBR,
Andrey Repin (anrdae...@yandex.ru) 02.12.2014, <08:29>
Sorry for my terrible english...
--
Problem reports: http://cy
On Fri, Nov 28, 2014 at 5:21 PM, Andrey Repin wrote:
> 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 $HO
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 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
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
Corinna Vinschen writes:
>> In practise IT would do these edits via a dedicated web interface that
>> takes most of its data from the install order form.
>
> -v please? Is there something available out of the box? Please keep in
> mind that I'm not an admin. ADSI Edit is perfectly fine for my li
On Nov 27 18:47, Achim Gratz wrote:
> Corinna Vinschen writes:
> > Ideally, such a configuration extension requires a new tool for Admins.
> > It's not exactly feasible for an Admin to install and maintain the
> > configuration extension in ADSI Edit.
>
> In practise IT would do these edits via a
Corinna Vinschen writes:
> Ideally, such a configuration extension requires a new tool for Admins.
> It's not exactly feasible for an Admin to install and maintain the
> configuration extension in ADSI Edit.
In practise IT would do these edits via a dedicated web interface that
takes most of its d
On Nov 26 21:56, Corinna Vinschen wrote:
> 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
On Nov 26 21:56, Corinna Vinschen wrote:
> db_gecos:
>
> windows AD and SAM: displayName attribute, or "Full Name"
> setting in SAM.
>
> cygwin AD-only: cygwinGecos attribute from cygwinUser class.
>
> unixAD-only: gecos attribute fro
On Nov 26 22:58, Corinna Vinschen wrote:
> On Nov 26 22:28, Achim Gratz wrote:
> > Corinna Vinschen writes:
> > > Ok, so we have a cygwin schema extension now. The file is called
> > > cygwin.ldif and is in the Cygwin CVS repo. It gets installed to
> > > /usr/share/cygwin. The schema extension c
On Nov 26 22:28, Achim Gratz wrote:
> Corinna Vinschen writes:
> > Ok, so we have a cygwin schema extension now. The file is called
> > cygwin.ldif and is in the Cygwin CVS repo. It gets installed to
> > /usr/share/cygwin. The schema extension consists of two auxiliary
> > classes:
> […]
> > Do
On Nov 26 21:44, Habermann, David (D) wrote:
> > In the long run I'm also planning to allow replacing /etc/fstab and
> > /etc/nsswitch.conf with a Cygwin-specific AD configuration extension.
>
> While I can see how this might be attractive for some, I see it as
> something that must be an optional
> In the long run I'm also planning to allow replacing /etc/fstab and
> /etc/nsswitch.conf with a Cygwin-specific AD configuration extension.
While I can see how this might be attractive for some, I see it as something
that must be an optional replacement of the /etc/fstab and /etc/nsswitch.conf
Corinna Vinschen writes:
> Ok, so we have a cygwin schema extension now. The file is called
> cygwin.ldif and is in the Cygwin CVS repo. It gets installed to
> /usr/share/cygwin. The schema extension consists of two auxiliary
> classes:
[…]
> Do you think this makes sense? Would you actually us
On Nov 26 21:56, Corinna Vinschen wrote:
> > Cygwin schema extension? :)
>
> I just created a patch and a matching snapshot on
> https://cygwin.com/snapshots/
Ok, so we have a cygwin schema extension now. The file is called
cygwin.ldif and is in the Cygwin CVS repo. It gets installed to
/usr/sh
On Nov 11 12:14, Corinna Vinschen wrote:
> On Nov 11 11:05, Achim Gratz wrote:
> > Corinna Vinschen cygwin.com> writes:
> > > 1. Add a setting to /etc/nsswitch.conf which allows to specify one of
> > > the above:
> > >
> > > home: [unix|win|home]...
> > >
> > >- "unix" means, set pw_di
Greetings, Corinna Vinschen!
>> >> > So the Cygwin home dir
>> >> > is equivalent to the CMD homedir, which is %HOMEDRIVE%%HOMEPATH%,
>> >>
>> >> Which is covered by "system" setting. Which will either read the location
>> >> from
>> >> AD or use %HOMEPATH%, if all else fails.
>> >>
>> >> > not
On Nov 14 01:04, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> >> > 1. Utilize the homeDirectory AD attribute (aka %HOMEDRIVE%%HOMEPATH%).
> >> > 2. If homeDirectory is empty, fall back to /home/$USER.
> >>
> >> This is just a subset of what I suggested, so I’m in favor of it.
> >> (By s
On Nov 14 00:49, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> > On Nov 12 23:23, Andrey Repin wrote:
> >> > So the Cygwin home dir
> >> > is equivalent to the CMD homedir, which is %HOMEDRIVE%%HOMEPATH%,
> >>
> >> Which is covered by "system" setting. Which will either read the location
Greetings, Corinna Vinschen!
>> > 1. Utilize the homeDirectory AD attribute (aka %HOMEDRIVE%%HOMEPATH%).
>> > 2. If homeDirectory is empty, fall back to /home/$USER.
>>
>> This is just a subset of what I suggested, so I’m in favor of it.
>> (By subset I mean that I’d prefer you do essentially the
Greetings, Corinna Vinschen!
> On Nov 12 23:23, Andrey Repin wrote:
>> > So the Cygwin home dir
>> > is equivalent to the CMD homedir, which is %HOMEDRIVE%%HOMEPATH%,
>>
>> Which is covered by "system" setting. Which will either read the location
>> from
>> AD or use %HOMEPATH%, if all else fail
On Nov 12 09:45, Warren Young wrote:
> On Nov 11, 2014, at 3:18 AM, Corinna Vinschen
> wrote:
>
> > 1. Utilize the homeDirectory AD attribute (aka %HOMEDRIVE%%HOMEPATH%).
> > 2. If homeDirectory is empty, fall back to /home/$USER.
>
> This is just a subset of what I suggested, so I’m in favor o
On Nov 12 23:23, Andrey Repin wrote:
> > So the Cygwin home dir
> > is equivalent to the CMD homedir, which is %HOMEDRIVE%%HOMEPATH%,
>
> Which is covered by "system" setting. Which will either read the location from
> AD or use %HOMEPATH%, if all else fails.
>
> > not %HOMEPATH%/AppData/Roaming/
On Nov 12 21:51, Habermann, David (D) wrote:
> > current scenario. Besides, it is nice to have the Cygwin HOME
> > directory isolated to the Cygwin installation for a portable install
> > that can be used on a USB thumb drive.
>
> I hadn't even thought about thumb drive/portable use since I hadn'
Greetings, cyg Simple!
> On Wed, Nov 12, 2014 at 12:55 PM, Habermann, David (D) wrote:
I also like having everything stored under one main directory (c:\cygwin)
for ease of backup
>>
>>> Why would you back up all of c:\cygwin? Most of it is downloaded from the
>>> Internet, and this is
> current scenario. Besides, it is nice to have the Cygwin HOME
> directory isolated to the Cygwin installation for a portable install
> that can be used on a USB thumb drive.
I hadn't even thought about thumb drive/portable use since I hadn't used mine
for a while. I, too, will have to work ar
On Wed, Nov 12, 2014 at 12:55 PM, Habermann, David (D) wrote:
>>> I also like having everything stored under one main directory (c:\cygwin)
>>> for ease of backup
>
>> Why would you back up all of c:\cygwin? Most of it is downloaded from the
>> Internet, and this is easily
>> reinstalled from yo
Greetings, Corinna Vinschen!
>> >> nsswitch.conf configurable settings:
>> >> user: Use %AppData%/Cygwin%PLATFORM% (Separate directory for different
>> >> platform Cygwins)
>>
>> > I really don't like this one.
>>
>> I'm just summing up suggestions that have been raised in the list for last
>> d
>> I also like having everything stored under one main directory (c:\cygwin)
>> for ease of backup
> Why would you back up all of c:\cygwin? Most of it is downloaded from the
> Internet, and this is easily
> reinstalled from your cached download. (I'm assuming you keep setup.exe and
> its dow
On Nov 11, 2014, at 3:18 AM, Corinna Vinschen wrote:
> 1. Utilize the homeDirectory AD attribute (aka %HOMEDRIVE%%HOMEPATH%).
> 2. If homeDirectory is empty, fall back to /home/$USER.
This is just a subset of what I suggested, so I’m in favor of it.
(By subset I mean that I’d prefer you do esse
On Nov 11, 2014, at 5:47 AM, Habermann, David (D) wrote:
> I also like having everything stored under one main directory (c:\cygwin) for
> ease of backup
Why would you back up all of c:\cygwin? Most of it is downloaded from the
Internet, and this is easily reinstalled from your cached downloa
On Nov 11, 2014, at 5:47 AM, Habermann, David (D) wrote:
> I also like having everything stored under one main directory (c:\cygwin) for
> ease of backup
Why would you back up all of c:\cygwin? Most of it is downloaded from the
Internet, and this is easily reinstalled from your cached downloa
On Nov 11 23:19, Andrey Repin wrote:
> >> nsswitch.conf configurable settings:
> >> user: Use %AppData%/Cygwin%PLATFORM% (Separate directory for different
> >> platform Cygwins)
>
> > I really don't like this one.
>
> I'm just summing up suggestions that have been raised in the list for last
> da
Greetings, Corinna Vinschen!
>> >> > Shall the "db" entries utilize the Windows home folder if it exits(*)
>> >> > and drop using the unixHomeDirectory? It seems inevitable…
>> >>
>> >> Use of AD implies some level of security consciousness. The ability to
>> >> write to c:\cygwin — not just d
On Nov 11 18:29, Andrey Repin wrote:
> Greetings, Corinna Vinschen!
>
> >> > Shall the "db" entries utilize the Windows home folder if it exits(*)
> >> > and drop using the unixHomeDirectory? It seems inevitable…
> >>
> >> Use of AD implies some level of security consciousness. The ability to
On Nov 11 17:44, Achim Gratz wrote:
> Corinna Vinschen writes:
> >> Looks good, but maybe allow the AD attribute to be explicitly named (e.g.
> >> cygwinHomeDirectory).
> >
> > Cygwin schema extension? :)
>
> I don't see why not, given that there's the possibility of having
> different information
Corinna Vinschen writes:
>> Looks good, but maybe allow the AD attribute to be explicitly named (e.g.
>> cygwinHomeDirectory).
>
> Cygwin schema extension? :)
I don't see why not, given that there's the possibility of having
different information for Windows, Cygwin and UNIX in the same AD. But
m
On Nov 11 08:51, Jeffrey Altman wrote:
> On 11/11/2014 4:59 AM, Corinna Vinschen wrote:
> > Please keep in mind that I'm talking about the Cygwin home dir not as
> > a default value which can be overridden in /etc/passwd, but of a Cygwin
> > home dir as returned by Cygwin when fetching the passwd e
Greetings, Corinna Vinschen!
>> > Shall the "db" entries utilize the Windows home folder if it exits(*)
>> > and drop using the unixHomeDirectory? It seems inevitable…
>>
>> Use of AD implies some level of security consciousness. The ability to
>> write to c:\cygwin — not just during installat
Greetings, Frank Fesevur!
>> I see literally zero reason to maintain separate, cygwin-specific "home"
>> directory.
> I think I have to disagree with you. When mixing MSYS, msysGit and
> Cygwin in the same home directory the dot-files can become a problem.
> Especially when it comes to line endin
On 11/11/2014 4:59 AM, Corinna Vinschen wrote:
> Please keep in mind that I'm talking about the Cygwin home dir not as
> a default value which can be overridden in /etc/passwd, but of a Cygwin
> home dir as returned by Cygwin when fetching the passwd entry from AD,
> and no passwd file exists. Thi
>>> Another:
>>>
>>> 1. Add a setting to /etc/nsswitch.conf which allows to specify one of
>>> the above:
>>>
>>> home: [unix|win|home]...
>>>
>>>- "unix" means, set pw_dir to unixHomeDirectory
>>>- "win" means, set pw_dir to homeDirectory
>>>- "home" means, set pw_dir to /home
On Nov 11 07:11, Bryan Berns wrote:
> One big vote for the '/etc/nsswitch.conf' idea. I think the truth of
> the matter is that enterprise environments are way too dynamic (and
> inconsistent) to attempt to satisfy the majority of configurations
> with any particular default ordering assumption.
>
One big vote for the '/etc/nsswitch.conf' idea. I think the truth of
the matter is that enterprise environments are way too dynamic (and
inconsistent) to attempt to satisfy the majority of configurations
with any particular default ordering assumption.
Another user brought up a good point about d
On Nov 11 11:05, Achim Gratz wrote:
> Corinna Vinschen cygwin.com> writes:
> > One possible, but not naturally useful default behaviour is what
> > the current code does:
> >
> > 1. Utilize the unixHomeDirectory AD attribute.
> > 2. If unixHomeDirectory is empty, fall back to /home/$USER.
> [...]
On Nov 11 11:18, Corinna Vinschen wrote:
> On Nov 10 23:09, Warren Young wrote:
> > On Nov 10, 2014, at 1:52 PM, Corinna Vinschen
> > wrote:
> >
> > > Shall the "db" entries utilize the Windows home folder if it exits(*)
> > > and drop using the unixHomeDirectory? It seems inevitable…
> >
> >
Corinna Vinschen cygwin.com> writes:
> One possible, but not naturally useful default behaviour is what
> the current code does:
>
> 1. Utilize the unixHomeDirectory AD attribute.
> 2. If unixHomeDirectory is empty, fall back to /home/$USER.
[...]
Default to /home/$USER unless a specific AD attr
On Nov 10 23:09, Warren Young wrote:
> On Nov 10, 2014, at 1:52 PM, Corinna Vinschen
> wrote:
>
> > Shall the "db" entries utilize the Windows home folder if it exits(*)
> > and drop using the unixHomeDirectory? It seems inevitable…
>
> Use of AD implies some level of security consciousness.
>Marco Atzeri wrote:
>>On 11/11/2014 7:40 AM, Andrey Repin wrote:
>>
>>In short, elusive benefits of having a separate cygwin-specific "clean"
>> homes
>>versus confusing disjoint of multiple places to look for single user's
>> files,
>>settings, and other stuff when it comes to back
On Nov 10 20:38, Jeffrey Altman wrote:
> On 11/10/2014 3:52 PM, Corinna Vinschen wrote:
> > Hi,
> >
> >
> > after a long discussion in RL today, I came to the conclusion that
> > there's a major problem in the current handling of the user's home
> > directory in AD environments in the new user ac
On Nov 10 23:19, Warren Young wrote:
> On Nov 10, 2014, at 6:38 PM, Jeffrey Altman
> wrote:
> > My personal preference would be for the Cygwin Home directory to be
> > created under
> >
> > %HOMEPATH%\AppData\Roaming\Cygwin
>
> That’s certainly the way you’re *supposed* to do it on Windows.
>
2014-11-11 1:45 GMT+01:00 Andrey Repin:
> I see literally zero reason to maintain separate, cygwin-specific "home"
> directory.
I think I have to disagree with you. When mixing MSYS, msysGit and
Cygwin in the same home directory the dot-files can become a problem.
Especially when it comes to line
On 11/11/2014 7:40 AM, Andrey Repin wrote:
Greetings, Yaakov Selkowitz!
In short, elusive benefits of having a separate cygwin-specific "clean" homes
versus confusing disjoint of multiple places to look for single user's files,
settings, and other stuff when it comes to backups and migrating pr
Corinna Vinschen cygwin.com> writes:
> > This isn't set yet in our domain, but there's another AD just for the
> > UNIX accounts (I haven't looked at how that one is structured yet).
> > There's talk about maybe unifying these two AD in the future, but I have
> > no idea how that would work.
>
>
Greetings, Yaakov Selkowitz!
>> When I implemented the new scheme I thought it a good idea to decouple
>> the Cygwin home dir from the Windows home dir. However, in the today's
>> discussion the following two arguments came up:
>>
>> - If you're using the Windows home folder setting to maintain f
Greetings, Andrew DeFaria!
> On 11/10/2014 4:45 PM, Andrey Repin wrote:
>> I see literally zero reason to maintain separate, cygwin-specific "home"
>> directory.
> My reason to have a separate, cygwin-specific "home" directory is to
> have one that is shared between Cygwin and Linux.
I do that
On Nov 10, 2014, at 6:38 PM, Jeffrey Altman
wrote:
> My personal preference would be for the Cygwin Home directory to be
> created under
>
> %HOMEPATH%\AppData\Roaming\Cygwin
That’s certainly the way you’re *supposed* to do it on Windows.
There’s some value in using %USERPROFILE% for this, h
On Nov 10, 2014, at 1:52 PM, Corinna Vinschen wrote:
> Shall the "db" entries utilize the Windows home folder if it exits(*)
> and drop using the unixHomeDirectory? It seems inevitable…
Use of AD implies some level of security consciousness. The ability to write
to c:\cygwin — not just during
On Nov 10, 2014, at 9:26 PM, Yaakov Selkowitz wrote:
> On 2014-11-10 14:52, Corinna Vinschen wrote:
>>
>> Shall the "db" entries utilize the Windows home folder if it exits(*)
>> and drop using the unixHomeDirectory? It seems inevitable...
>
> If one uses the same program, one native Windows a
On 2014-11-10 14:52, Corinna Vinschen wrote:
When I implemented the new scheme I thought it a good idea to decouple
the Cygwin home dir from the Windows home dir. However, in the today's
discussion the following two arguments came up:
- If you're using the Windows home folder setting to maintai
On 11/10/2014 4:45 PM, Andrey Repin wrote:
I see literally zero reason to maintain separate, cygwin-specific "home"
directory.
My reason to have a separate, cygwin-specific "home" directory is to
have one that is shared between Cygwin and Linux. Windows define home
directories rarely are sha
On 11/10/2014 3:52 PM, Corinna Vinschen wrote:
> Hi,
>
>
> after a long discussion in RL today, I came to the conclusion that
> there's a major problem in the current handling of the user's home
> directory in AD environments in the new user account code when not using
> /etc/passwd files.
My p
Greetings, Corinna Vinschen!
> Up to Cygwin 1.7.32, mkpasswd (but not with -u) generated the Cygwin
> home directory by converting the SAM/AD home folder entry to POSIX
> style, if it's non-empty. Fallback is /home/$USER.
> When I implemented the new scheme I thought it a good idea to decouple
>
On Nov 10 22:18, Achim Gratz wrote:
> Corinna Vinschen writes:
> > - If your account is an AD account, the home directory is taken from the
> > RFC 2307 entry unixHomeDirectory.
>
> This isn't set yet in our domain, but there's another AD just for the
> UNIX accounts (I haven't looked at how tha
Corinna Vinschen writes:
> - If your account is an AD account, the home directory is taken from the
> RFC 2307 entry unixHomeDirectory.
This isn't set yet in our domain, but there's another AD just for the
UNIX accounts (I haven't looked at how that one is structured yet).
There's talk about may
82 matches
Mail list logo
