On Fri, 29 Apr 2022 13:59:59 +0200
Thomas Wolff wrote:
> I upgraded 3.3.3 → 3.3.4 in a lab environment, where my home directory
> is H:\ or /cygdrive/h
>
> Starting cygwin (cmd/bash or mintty) with some tools from gnuutils (like
> ls) in the path gives me this message:
>
>
I upgraded 3.3.3 → 3.3.4 in a lab environment, where my home directory
is H:\ or /cygdrive/h
Starting cygwin (cmd/bash or mintty) with some tools from gnuutils (like
ls) in the path gives me this message:
mkdir: cannot create directory ‘/cygdrive/h’: File exists
/cygdrive/h could not be
use your software in years.
Best wishes,
Aldi Kraja, DSc, PhD
aldi.kr...@pystat.com
From: Cygwin on behalf of KAVALAGIOS Panagiotis
(EEAS-EXT)
Sent: Wednesday, March 3, 2021 06:43 AM
To: Thomas Wolff
Cc: cygwin@cygwin.com
Subject: RE: Home direc
On 2021-03-03 04:22, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
-Original Message-
From: Cygwin On Behalf Of Brian Inglis
Sent: 02 March 2021 19:57
On 2021-03-02 01:08, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
-Original Message-
From: KAVALAGIOS Panagiotis (EEAS-EXT)
Sent: 02 March
> -Original Message-
> From: Cygwin On Behalf Of KAVALAGIOS
> Panagiotis (EEAS-EXT)
> Sent: 03 March 2021 12:23
>
> > -Original Message-
> > From: Cygwin On Behalf Of Brian Inglis
> > Sent: 02 March 2021 19:57
> >
> > All postinstall steps failed because of BLODA or installation
On 2021-03-03 06:07, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
-Original Message-
From: Thomas Wolff
Sent: 03 March 2021 13:59
Am 03.03.2021 um 13:43 schrieb KAVALAGIOS Panagiotis (EEAS-EXT):
-Original Message-
From: Thomas Wolff
Sent: 03 March 2021 12:58
Am 03.03.2021 um 12:22
> -Original Message-
> From: Thomas Wolff
> Sent: 03 March 2021 13:59
>
> Am 03.03.2021 um 13:43 schrieb KAVALAGIOS Panagiotis (EEAS-EXT):
> >> -Original Message-
> >> From: Thomas Wolff
> >> Sent: 03 March 2021 12:58
> >>
> >> Am 03.03.2021 um 12:22 schrieb KAVALAGIOS Panagiotis
> -Original Message-
> From: Andrey Repin
> Sent: 03 March 2021 12:56
>
> Greetings, KAVALAGIOS Panagiotis (EEAS-EXT)!
>
> >> All postinstall steps failed because of BLODA or installation path:
> >>
> >> 2021/02/09 17:48:06 running: C:\Program Files\Cygwin\bin\dash.exe
> >> "/etc/postins
Am 03.03.2021 um 13:43 schrieb KAVALAGIOS Panagiotis (EEAS-EXT):
-Original Message-
From: Thomas Wolff
Sent: 03 March 2021 12:58
Am 03.03.2021 um 12:22 schrieb KAVALAGIOS Panagiotis (EEAS-EXT):
-Original Message-
From: Cygwin On Behalf Of Brian Inglis
Sent: 02 March 2021 19
> -Original Message-
> From: Thomas Wolff
> Sent: 03 March 2021 12:58
>
> Am 03.03.2021 um 12:22 schrieb KAVALAGIOS Panagiotis (EEAS-EXT):
> >> -Original Message-
> >> From: Cygwin On Behalf Of Brian Inglis
> >> Sent: 02 March 2021 19:57
> >>
> >> On 2021-03-02 01:08, KAVALAGIOS
Greetings, KAVALAGIOS Panagiotis (EEAS-EXT)!
>> All postinstall steps failed because of BLODA or installation path:
>>
>> 2021/02/09 17:48:06 running: C:\Program Files\Cygwin\bin\dash.exe
>> "/etc/postinstall/0p_000_autorebase.dash"
>>0 [main] dash (2296) shared_info::initialize: size of
Am 03.03.2021 um 12:22 schrieb KAVALAGIOS Panagiotis (EEAS-EXT):
-Original Message-
From: Cygwin On Behalf Of Brian Inglis
Sent: 02 March 2021 19:57
On 2021-03-02 01:08, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
-Original Message-
From: KAVALAGIOS Panagiotis (EEAS-EXT)
Sent: 02
> -Original Message-
> From: Cygwin On Behalf Of Brian Inglis
> Sent: 02 March 2021 19:57
>
> On 2021-03-02 01:08, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
> > -Original Message-
> > From: KAVALAGIOS Panagiotis (EEAS-EXT)
> > Sent: 02 March 2021 08:15
>
> > zip 358KB > 256KB too b
On 2021-03-02 01:08, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
-Original Message-
From: KAVALAGIOS Panagiotis (EEAS-EXT)
Sent: 02 March 2021 08:15
To: cygwin@cygwin.com
Subject: RE: Home directory was not created
-Original Message-
From: On Behalf Of Brian Inglis
Sent: 01 March
On Mon, 1 Mar 2021 at 15:33, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
> Dear all,
>
> Something went wrong to my Cygwin installation update (update is performed by
> removing everything and installing again the new version). The home directory
> of my user was not created, when you
On 2021-03-01 08:33, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
Something went wrong to my Cygwin installation update (update is performed
by removing everything and installing again the new version). The home
directory of my user was not created, when you run Cygwin for the first time.
When I
Dear all,
Something went wrong to my Cygwin installation update (update is performed by
removing everything and installing again the new version). The home directory
of my user was not created, when you run Cygwin for the first time. When I
start Cygwin it defaults to the evil C:\Windows
Silly me -- problem was due to a typo in an old (and forgotten)
fstab.d file.
Never mind. Sorry for the troubles...
"" wrote at about 15:47:59 -0400 on Tuesday, August 27, 2019:
> In summary:
> 1. Home directory is not accessible via: 'cd ' or 'cd ~' (it
When I use an fstab.d file to mount my home directory at an
alternative point, everything seems to work (so far) except for
ssh-add that returns with exit code 2 (error) seemingly because it
can't find the .ssh folder and associated key.
Note that the perms of the .ssh folder and contained
In summary:
1. Home directory is not accessible via: 'cd ' or 'cd ~' (it
takes me to /tmp) and 'ls -al /home' shows my home directory as
having corrupted permissions, UID and GID (all are ???)
2. Home directory is accessible and shows proper perms/UID/GID wh
On Tue, 19 Feb 2019 19:24:38, Boylan, Ross" wrote:
> [Answering my own question after better searching]
> Same question asked and answered in the thread starting https://cygwin.com/=
> ml/cygwin/2016-06/msg00400.html.
> The answer is to set db_home in nsswitch.conf.
>
> Comment: the current behav
Am 19.02.2019 um 21:08 schrieb Andrey Repin:
Greetings, Boylan, Ross!
I recently installed cygwin on Win 10, both 64 bit.
When I run ssh in a cygwin shell it complains
Could not create directory '/home/rdboylan/.ssh'.
The /home directory is empty--that is, it has n
Greetings, Boylan, Ross!
> I recently installed cygwin on Win 10, both 64 bit.
> When I run ssh in a cygwin shell it complains
> Could not create directory '/home/rdboylan/.ssh'.
> The /home directory is empty--that is, it has no rdboylan subdirectory.
> My
.
From: Boylan, Ross
Sent: Tuesday, February 19, 2019 11:15:47 AM
To: cygwin@cygwin.com
Subject: ssh confused about home directory?
I recently installed cygwin on Win 10, both 64 bit.
When I run ssh in a cygwin shell it complains
Could not create directory '
I recently installed cygwin on Win 10, both 64 bit.
When I run ssh in a cygwin shell it complains
Could not create directory '/home/rdboylan/.ssh'.
The /home directory is empty--that is, it has no rdboylan subdirectory.
My home directory appears to be /cygdrive/c/Users/rdbo
On Fri, Feb 15, 2019 at 11:09 PM L A Walsh wrote:
> Vince, I think What Bill is trying to ask is how does
> the cygwin shell might do it (answer: look at the source! ;-)).
Or rather more succinctly: "Cygwin, what is the path to the current
user's home directory?"
IMO it
On 2/14/2019 3:57 PM, Vince Rice wrote:
>> On Feb 14, 2019, at 5:41 PM, Bill Stewart wrote:
>>
>> (?) I understand that the shell does ~ expansion
>>
>
> It would not appear that you do. You asked why a Cygwin shell would be a
> prerequisite.
>
Vince, I think What Bill is
Greetings, Doug Henderson!
>>
>> Greetings, Bill Stewart!
>>
>> >> Setup your system to use %USERPROFILE% as $HOME and forget this problem
>> >> altogether.
>> >> For interoperability's sake! (q)
>>
>> > That won't work, because Cygwin $HOME can be different from the
>> > USERPROFILE environment v
On Fri, 15 Feb 2019 at 13:35, Andrey Repin wrote:
>
> Greetings, Bill Stewart!
>
> >> Setup your system to use %USERPROFILE% as $HOME and forget this problem
> >> altogether.
> >> For interoperability's sake! (q)
>
> > That won't work, because Cygwin $HOME can be different from the
> > USERPROFILE
Greetings, Bill Stewart!
>> Setup your system to use %USERPROFILE% as $HOME and forget this problem
>> altogether.
>> For interoperability's sake! (q)
> That won't work, because Cygwin $HOME can be different from the
> USERPROFILE environment variable on Windows.
Make. It. The. Same.
Tell, don't
On Fri, Feb 15, 2019 at 4:50 AM Andrey Repin wrote:
> Not as good as bash. Just so you know.
We'll just agree to disagree on that (particularly on Windows).
> Setup your system to use %USERPROFILE% as $HOME and forget this problem
> altogether.
> For interoperability's sake! (q)
That won't work
On Fri, Feb 15, 2019 at 9:14 AM Takashi Yano wrote:
> If you don't want to use "shell", you can:
> c:/cygwin/bin/cygpath -w $(c:/cygwin/bin/getent passwd $env:USERNAME |
> c:/cygwin/bin/cut -d: -f6)
> but I'm not sure if you think this is "awkward" as well.
Why cut if you are already using Power
On 2019-02-14 17:03, Bill Stewart wrote:
> On Thu, Feb 14, 2019 at 4:57 PM Vince Rice wrote:
>> Here, you say "forget about the ~ character." We can't "forget" about the
>> tilde. This whole
>> conversation is about the tilde, specifically tilde expansion.
> Eric Blake seems to have understood (se
On Thu, 14 Feb 2019 16:41:11 -0700 Bill Stewart wrote:
> (?) I understand that the shell does ~ expansion. I am asking for a
> way to get that particular path (forget about the ~ character for the
> time being) without needing to invoke a Cygwin shell in the first
> place. (That was the whole point
;/bin/cygpath -aw ~'
> However, this seems awkward and requires a Cygwin shell (why should
> that be a prerequisite?).
Try http://make-everything-ok.com/ then.
> So I guess I have a feature request:
> Add a new flag to cygpath that returns the current user's home
>
On 15.02.2019 2:41, Bill Stewart wrote:
> On Thu, Feb 14, 2019 at 4:32 PM Vince Rice wrote:
>
>> I didn't suggest everyone did. But people who want tilde expansion do,
>> because it's
>> the shell that is responsible for tilde expansion.
>> ...
>> No, it isn't "oddly" absent. As has been said rep
On Thu, Feb 14, 2019 at 4:57 PM Vince Rice wrote:
> Here, you say "forget about the ~ character." We can't "forget" about the
> tilde. This whole
> conversation is about the tilde, specifically tilde expansion.
Eric Blake seems to have understood (see his response if it's still unclear).
Regard
> On Feb 14, 2019, at 5:41 PM, Bill Stewart wrote:
>
> On Thu, Feb 14, 2019 at 4:32 PM Vince Rice wrote:
>
>> I didn't suggest everyone did. But people who want tilde expansion do,
>> because it's
>> the shell that is responsible for tilde expansion.
>> ...
>> No, it isn't "oddly" absent. As has
On 2/14/19 4:52 PM, Bill Stewart wrote:
> So I guess I have a feature request:
>
> Add a new flag to cygpath that returns the current user's home
> directory (same as what ~ returns from a Cygwin shell).
Let's phrase that more accurately. You want a new option to cygpath
On Thu, Feb 14, 2019 at 4:32 PM Vince Rice wrote:
> I didn't suggest everyone did. But people who want tilde expansion do,
> because it's
> the shell that is responsible for tilde expansion.
> ...
> No, it isn't "oddly" absent. As has been said repeatedly in this thread,
> tilde expansion
> is t
> On Feb 14, 2019, at 4:52 PM, Bill Stewart wrote:
>
> On Thu, Feb 14, 2019 at 3:14 PM Vince Rice wrote:
>
>> There is -- use a cygwin shell. As Eric has already explained, expansion is
>> the
>> shell's responsibility. Powershell doesn't do it. If you want expansion, use
>> one
>> that does.
/bin/cygpath -aw ~'
However, this seems awkward and requires a Cygwin shell (why should
that be a prerequisite?).
So I guess I have a feature request:
Add a new flag to cygpath that returns the current user's home
directory (same as what ~ returns from a Cygwin shell).
Thanks!
> On Feb 14, 2019, at 3:51 PM, Bill Stewart wrote:
>
> Seems like there must be a better way...
There is — use a cygwin shell. As Eric has already explained, expansion is the
shell's responsibility. Powershell doesn't do it. If you want expansion, use one
that does.
--
Problem reports: http
On Thu, Feb 14, 2019 at 2:15 PM Eric Blake wrote:
> If you want tilde-expansion to happen, you have to use a shell that does
> tilde-expansion. bash and dash do, PowerShell does not. It is not
> cygpath's fault, but your choice of shell, that determines whether ~ is
> expanded. And, since the ti
On 2/14/19 2:22 PM, Bill Stewart wrote:
> On Thu, Feb 14, 2019 at 12:49 PM Eric Blake wrote:
>
>> Depending on the shell, ~ is expanded to $HOME prior to invoking a
>> program. But if you want to take the shell's expansions out of the
>> equation, you could use:
>>
>> cygpath -w "$HOME"
>
> Ah. I
On Thu, Feb 14, 2019 at 12:49 PM Eric Blake wrote:
> Depending on the shell, ~ is expanded to $HOME prior to invoking a
> program. But if you want to take the shell's expansions out of the
> equation, you could use:
>
> cygpath -w "$HOME"
Ah. I'm not using a Cygwin shell (PowerShell actually). So
On 2/14/19 1:40 PM, Bill Stewart wrote:
> According to this:
>
> https://stackoverflow.com/questions/42841907/
>
> cygpath -w ~
>
> ...formerly produced to stdout the home directory path for the current user.
>
> This seems not be the case any more: When I run cygpat
According to this:
https://stackoverflow.com/questions/42841907/
cygpath -w ~
...formerly produced to stdout the home directory path for the current user.
This seems not be the case any more: When I run cygpath -w ~, I get just ~.
Is this by design? If so, what's the way to programmati
for some reason, running fish shell fails with
>>>> PermissionDenied error if the home directory is a Windows Junction.
>>>
>>> Unfortunately I don't know how to help with this. fish works fine except in
>>> this case where the directory ~/.config/f
> On 9/10/2018 12:06 PM, Andrew Schulman wrote:
> >> This report originates from a ticket created on Fish Github account here:
> >> https://github.com/fish-shell/fish-shell/issues/2590
> >> The issue is, that for some reason, running fish shell fails with
> >
On 9/10/2018 12:06 PM, Andrew Schulman wrote:
>> This report originates from a ticket created on Fish Github account here:
>> https://github.com/fish-shell/fish-shell/issues/2590
>> The issue is, that for some reason, running fish shell fails with
>> PermissionDenied err
> This report originates from a ticket created on Fish Github account here:
> https://github.com/fish-shell/fish-shell/issues/2590
> The issue is, that for some reason, running fish shell fails with
> PermissionDenied error if the home directory is a Windows Junction.
Unfortunately
Hi,
This report originates from a ticket created on Fish Github account here:
https://github.com/fish-shell/fish-shell/issues/2590
The issue is, that for some reason, running fish shell fails with
PermissionDenied error if the home directory is a Windows Junction.
This is what I get when I run
On 2018-02-14 10:58, Scott Neugroschl wrote:
| Using greed 3.10-1
| At the end of a game, it reports the following
|
| /home/jaalto/cygwin/my/greed/greed-3.10/.inst/var/games/greed/greed.hs:
| Cannot open.
New release uploaded, should be in archives soon.
Jari
--
Problem reports: http://cy
Using greed 3.10-1
At the end of a game, it reports the following
greed:
/home/jaalto/cygwin/my/greed/greed-3.10/.inst/var/games/greed/greed.hs:
Cannot open.
System info:
$ uname -srvmpio
CYGWIN_NT-6.1 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 unknown unknown
Cygwin
$ cygcheck -cd
On Jul 30 14:38, Reckoner wrote:
> Thanks for your reply. By "home" directory, I mean "/home/". This is
> c:\cygwin\home on Windows but /home/ on cygwin.
>
> % icacls foo
> foo NULL SID:(DENY)(Rc,S,WEA,X,DC)
> S4\jhu:(DENY)(S,RD,WD,AD,REA,WEA,DC)
>
I mean '/home/jhu' as the user's home.
Sorry for the confusion.
On Sat, Jul 30, 2016 at 2:38 PM, Reckoner wrote:
> Thanks for your reply. By "home" directory, I mean "/home/". This is
> c:\cygwin\home on Windows but /home/ on cygwin.
>
> %
Thanks for your reply. By "home" directory, I mean "/home/". This is
c:\cygwin\home on Windows but /home/ on cygwin.
% icacls foo
foo NULL SID:(DENY)(Rc,S,WEA,X,DC)
S4\jhu:(DENY)(S,RD,WD,AD,REA,WEA,DC)
S4\jhu:(D,Rc,WDAC,WO,RA,WA)
NT AUTHORITY\Authenticated User
Greetings, Reckoner!
> When I do
> % touch foo
> in my home directory, `ls -l` gives,
> rw+ 1 jhu 0 Jul 30 09:16 foo
Define "home directory"? Is this cygwin private home? Your user's home set as
Cygwin home through nsswitch ?
What is the output on said
When I do
% touch foo
in my home directory, `ls -l` gives,
rw+ 1 jhu 0 Jul 30 09:16 foo
Note the permissions. Here's my /etc/fstab
none /mnt cygdrive binary,noacl,posix=0,user 0 0
c: /c ntfs noacl,binary,auto 0 0
d: /d ntfs noacl,binary,auto 0 0
c:/Temp /tmp ntfs noacl,b
- Original Message -
> From: Bruce Halco
> To: cygwin
> Cc:
> Date: 2016/7/2, Sat 06:28
> Subject: Can't Delete Home Directory - Unknown+User:Unknown+Group
>
> I don't know how this happened, and it was probably self-inflicted, but one
>
I don't know how this happened, and it was probably self-inflicted, but
one of the home directories in a new cygwin install has wound up owned
by Unknown+User and Unknown+Group, with permissions 750.
Opening the cygwin window "As Administrator" will not allow me to remove
the directory or chan
On 28 June 2016 at 10:06, Corinna Vinschen wrote:
> On Jun 28 09:38, Chris Sutcliffe wrote:
>> I have my $HOME path setup as /cygdrive/c/Users (using Windows 7)
>> however ssh doesn't seem to honour that. When I fire up ssh, I get:
>>
>> Could not create directory '/home/csutclif/.ssh'.
>
> OpenSS
'/home/csutclif/.ssh'.
>>
>> Why is it defaulting to /home? Is there a way to configure ssh to
>> point to the $HOME path? I have a .ssh directory with my private key
>> in /cygdrive/c/Users/csutlif.
>
> You need to configure your home directory using the
ay to configure ssh to
point to the $HOME path? I have a .ssh directory with my private key
in /cygdrive/c/Users/csutlif.
Thanks,
Chris
You need to configure your home directory using the db_home setting in
/etc/nsswitch.conf.
See the following section in the Cygwin User's Guide:
https
On Jun 28 09:38, Chris Sutcliffe wrote:
> Hi,
>
> I have my $HOME path setup as /cygdrive/c/Users (using Windows 7)
> however ssh doesn't seem to honour that. When I fire up ssh, I get:
>
> Could not create directory '/home/csutclif/.ssh'.
OpenSSH never honors $HOME. It checks explicitely for
Hi,
I have my $HOME path setup as /cygdrive/c/Users (using Windows 7)
however ssh doesn't seem to honour that. When I fire up ssh, I get:
Could not create directory '/home/csutclif/.ssh'.
Why is it defaulting to /home? Is there a way to configure ssh to
point to the $HOME path? I have a .ssh
On 06/04/2016 17:48, Jim Reisert AD1C wrote:
My employer is making us use Box Sync for backup. We have to move all
directories we want backed up into the Box Sync folder.
So I have moved my Cygwin ~ (home) directory to that folder. I
configured nsswitch.conf as follows:
db_home
> So I have moved my Cygwin ~ (home) directory to that folder. I
> configured nsswitch.conf as follows:
>
> db_home: /cygdrive/c/Users/reisert/Box%_Sync/Home
>
> Most things are working. However, my Xterms are coming up in the
> default 80x24 format with black text
Hi,
My employer is making us use Box Sync for backup. We have to move all
directories we want backed up into the Box Sync folder.
So I have moved my Cygwin ~ (home) directory to that folder. I
configured nsswitch.conf as follows:
db_home: /cygdrive/c/Users/reisert/Box%_Sync/Home
Most
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
ll "db_home: windows" fall back
> > > to the default Windows home dir if homeDrive/homeDirectory are empty?
> >
> > 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 s
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
>> > homeDrive/homeDirectory attributes, because it doesn't fall back to the
>> > Windows default values.
>>
>> > So, another question is this: Shall "db_home: windows" fall back
>> > to the default Windows home dir if homeDrive/homeDirectory
> > homeDrive/homeDirectory attributes, because it doesn't fall back to the
> > Windows default values.
>
> > So, another question is this: Shall "db_home: windows" fall back
> > to the default Windows home dir if homeDrive/homeDirectory are empty
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
fault values.
> So, another question is this: Shall "db_home: windows" fall back
> to the default Windows home dir if homeDrive/homeDirectory are empty?
Yes, if you mean it.
I mean, if you intend to use the same directory OS using for user's home
directory, you gott
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
1 - 100 of 365 matches
Mail list logo
