DGStevens deansx at gmail.com writes:
I'm unable to use gdb on any c/c++ executables. When I try, gdb issues the
message dll path too long and fails to start the target executable.
Try cutting your PATH after the third component. If that helps, you could
set CYGWIN_NOWINPATH either as a
Achim Gratz Stromeko at nexgo.de writes:
There are still crashes of emacs-w32 that take down Emacs completely
(sometimes with but mostly without it asking for the debugger to be
attached). So far these have all occured directly in response to
keyboard input (as in the window disappears while
Ken Brown kbrown at cornell.edu writes:
Do you remember what you were doing at the time of the crash?
I was editing something in a Perl buffer and was just about to insert an s
into a variable name. The only crashes I've got with the current test
version so far were always happening directly
Corinna Vinschen corinna-cygwin at cygwin.com writes:
That's the real output? No error message, just the names of the
mount points? Is that the 32 or 64 bit Cygwin?
Yes:
df /home/gratz
df: ‘/home/gratz’
Given the lack of access to netapp drives, if this is a bug in Cygwin
(which seems
Angelo Graziosi angelo.graziosi at alice.it writes:
In this case, all temporary files created by Windows native
applications, started with cygstart, go in /tmp Cygwin directory.., i.e.
the definition TEMP=/home/$USER/Temp in front of cygstart command is
ignored..
You should check if
Corinna Vinschen corinna-cygwin at cygwin.com writes:
Then you have to build your own Cygwin DLL for testing.
I've just set up for a build and ran into this (with the snapshot sources
from 2014-08-19 since these were the ones I had at hand):
ccwrap -g -O2 -O3 -mtune=core2 -march=core2 -Wall
Corinna Vinschen writes:
I've just set up for a build and ran into this (with the snapshot sources
from 2014-08-19 since these were the ones I had at hand):
ccwrap -g -O2 -O3 -mtune=core2 -march=core2 -Wall -Wstrict-aliasing
^^^
Huh?
Did you specify -O3
Ken Brown writes:
It looks like my idea is going to work, but it needs testing to make
sure I've implemented it correctly. If anyone is willing to test it,
you can download emacs-24.3.93-2 from my personal Cygwin repository:
http://sanibeltranquility.com/cygwin/
Instructions can be found
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I fixed that in CVS (and I'm just generating a snapshot). The problem
was that the functions reading and writing security descriptors didn't
use the special reopen by handle semantics of the NtOpenFile call if
a reopen was necessary.
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I've just set up for a build and ran into this (with the snapshot sources
from 2014-08-19 since these were the ones I had at hand):
Sorted. I just did a native build from the 2014-08-25 snapshot (which is
also the installed version). Now
Corinna Vinschen corinna-cygwin at cygwin.com writes:
It's easier to do this from CVS. It also allows to create diffs
most easily. Did you build outside the source dir, as required?
No can do CVS here... I just did a ./configure make, which seemed to
work (it built into
Corinna Vinschen corinna-cygwin at cygwin.com writes:
The call to NtQueryVolumeInformationFile() in
fhandler_disk_file::fstatvfs() in fhandler_disk_file.cc (line 737ff),
fails with STATUS_INVALID_PARAMETER. This is a NetApp bug, but we may
be able to workaround it.
The bug (if there is one)
Ken Brown kbrown at cornell.edu writes:
Achim, could you send me a recipe for reproducing the problem so that I
can test further? Please be very detailed; I have no experience with ACLs.
Let's get one issue out of the way first that may be a Cygwin bug: on Linux
a file with all access removed
Corinna Vinschen corinna-cygwin at cygwin.com writes:
-v, please. What means obviously here? Did you ask Netapp?
No, I've tried all combinations of parameters to the open calls to
absolutely no avail. I then started to look at what the VolumeInformation
call is supposed to be doing and
Corinna Vinschen writes:
Fixed in CVS. The idea to reopen the file by handle is still good.
*Iff* there is an open handle to the file to begin with...
I'm just creating a snapshot but this may take a few minutes longer
than anticipated due to connection problems.
Snapshot is up.
I failed
Achim Gratz Stromeko at NexGo.DE writes:
Let's get one issue out of the way first that may be a Cygwin bug: on Linux
a file with all access removed via standard POSIX modes and then access
granted via ACL would place the mask bits of the ACL (the maximum permission
that can be granted via ACL
Corinna Vinschen corinna-cygwin at cygwin.com writes:
[...]
The patch with the fallback to FileFsSizeInformation works as expected.
Btw., one other hare-brained idea would be if the Netapp FS has a
somewhat different idea of the size of FILE_FS_FULL_SIZE_INFORMATION,
maybe due to a
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I implemented this preliminary and uploaded a snapshot to
https://cygwin.com/snapshots/
Oh, great! I'll bump my machine to that snapshot tomorrow.
Since I can now compile my own DLL, would that be a good time to ask what
could be done for
Corinna Vinschen corinna-cygwin at cygwin.com writes:
Since the CLASS_OBJ and DEF_CLASS_OBJ entries only exist if secondary
user and group (default) entries exist, that means the default
permission entry only consists of 3 ACEs. This in turn means, the
constant MIN_ACL_ENTRIES changed from 4
Andrey Repin writes:
What Cygwin could do is to perform ACL-based access checks independently of
the acl/noacl mount mode on FSes supporting ACLs. However, if you want
ACLs, why not use the acl mount mode in the first place?
ACL inheritance, mostly. POSIX'ized permissions break inheritance
Corinna Vinschen writes:
Here's the prerequisite:
Would more than one person want that *and* be willing to give this a
*thorough* testing?
That really becomes an issue only if you have to use external shares
that are set up in peculiar ways and AD integration. The number of
people that
Sam Townsend writes:
I've been trying to install Cygwin on a Server 2012 R2 box, but the
install keeps failing. I am using the latest installer (2.850,
32-bit), and I have tried multiple mirrors.
I've done multiple installs (for testing purposes) on just such a box,
both 32bit and 64bit and
Sam Townsend writes:
It seems you are trying to install into the root directory of the C:
drive. Move it down a directory, maybe into C:\Freeware\Cygwin and
install there and I guess it will work.
I tried installing to C:\sv\cygwin, and got the same problem.
With that out of the way, the
Achim Gratz Stromeko at NexGo.DE writes:
Please test.
This fixes the read-only problem in Emacs (so that hunch was correct).
Perl still doesn't play, but I think the 5.18 version should get it correct.
Will need to switch a test installation over for that, though.
With that snapshot
Ken Brown writes:
With the latest snapshot I can't start the sshd service. The
Application Log just says, `sshd' service stopped, exit
status:255. The problem doesn't occur with the 2014-08-27 snapshot.
I guess this has something to do with the new permissions on various
files, but I'm not
Ken Brown writes:
I just checked /var/log/sshd.log. (I hadn't thought to do that
before.) The last message in it is, /var/empty must be owned by root
and not group or world-writable. So the problem seems to be that
/var/empty appears to sshd to be group writable under the latest
snapshot.
Corinna Vinschen writes:
Over the weekend it occured to me that the acl(2) function created ACLs
which not aligned well with the ACLs created by open(2),chmod(2), etc.
Yesterday I fixed the acl(2) function to create ACLs the same way as
the other functions, especially in terms of the owner
Achim Gratz Stromeko at nexgo.de writes:
- Windows Server 2012R2 64bit running on hardware
- domain member
- Cygwin 32bit (latest snapshot from 2014-08-31 w/ AD integration)
can anybody confirm they have gotten sshd successfully running? As far
as I can debug this, the sshd I have
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I have no idea what could be wrong in your environment, sorry.
Me neither. I've set all three Cygwin environments up exactly the same way,
using identical users and command lines (just different service names,
obviously).
I still have to
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I have no idea what could be wrong in your environment, sorry.
Some more information: up until the check for /etc/nologin everything works.
Things fall apart when sshd tries to switch to the user logging on. I've
traced this again, sshd
Corinna Vinschen writes:
Installed, everything looks fine so far.
Thanks for testing! Maybe you'd like to have a view into the simple
as well as the more complex ACLs created by Cygwin? Icacls output
is moderately easy to read. If you have questions or concerns...
I've used icacls in the
Corinna Vinschen writes:
Don't use privilege separation, then the non-privileged sshd user won't
matter at all. Privsep on Cygwin is only half-useful on Cygwin anyway,
if at all. As for the local cyg_server account, I'm not sure. Usually,
a local machine account has no or only limited
gjnospam2014-cyg...@yahoo.com writes:
I'm getting this whenever I try to convert any document:
WJFFM.
https://cygwin.com/problems.html
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
Gerry Reno writes:
I have a script that issues this command:
run $WINDIR/system32/mstsc.exe /multimon /v:$IP:3389
And before this script has always succeeded but now it errors as follows:
Invalid connection file (/v:192.168.1.27:3389) specified
In a terminal window I can run the
Corinna Vinschen writes:
More or less, just compare the ACLs and see if you find strange
differences. This only works for the ACLs created or modified with
`setfacl' and the snapshot DLL.
I see, I'll have to make extra tests for this. Usually I just have to
live with some inherited ACL that
Corinna Vinschen writes:
$ setfacl -d g:system: filename
Note the trailing colon.
That's not what the man page specifies, however. I'll keep it in mind.
Removing the group
owner ACL instead did the right thing in at least one instance.
??? It shouldn't. Removing the standard ACL
Corinna Vinschen corinna-cygwin at cygwin.com writes:
Don't use privilege separation, then the non-privileged sshd user won't
matter at all. Privsep on Cygwin is only half-useful on Cygwin anyway,
if at all.
I've switched privilege separateion off completely, but no dice. The Access
Denied
Achim Gratz Stromeko at NexGo.DE writes:
The strace shows that it doesn't even *try* to start bash, but it's
entirely unclear why.
Is it possible to run sshd in gdb?
I can attach the debugger but I didn't manage to break into something useful
(or anything at all, really). However
David Eisner deisner at gmail.com writes:
Is this intentional, or am I missing something? Thanks.
Looks like a packaging error for x86 (the x86_64 package is OK).
Regards,
Achim.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Corinna Vinschen writes:
I patched setfacl to not require trailing colons anymore. This also
fixes a bug in terms of the allowed acl entries when deleting.
Great, thanks!
[…]
I just created a new snapshot on https://cygwin.com/snapshots/
containing these patches. Please give them a try.
Gerry Reno writes:
On the 32-bit system cygwin installs that haven't been updated yet 'run.exe'
shows:
$ ls -l /usr/bin/run.exe
-rwxr-xr-x 1 Administrator None 65053 Jul 24 2013 /usr/bin/run.exe
On a 32-bit system with this latest cygwin 'run.exe' shows:
$ ls -l
Corinna Vinschen corinna-cygwin at cygwin.com writes:
You already built your own Cygwin DLL, right? What you could do is to
do some good old printf debugging. First let's try to find out if it's
really one of the NetUser calls:
It looks like I need to install more than the DLL to make this
Corinna Vinschen corinna-cygwin at cygwin.com writes:
I couldn't start cygserver as a service with (just) the built DLL in place.
No idea why. The patch just adds debug output to strace ouptput, nothing
else.
Whatever. I've installed all the binaries from that build and things work
Ok, I don't grok this. If you have trouble with cygserver, which is
completely unrelated to this issue, please discuss this in a new thread
and please describe detailed what you did to provoke the problem and
paste what you see.
I'm running (from an administrative account) cygserver -d in
Achim Gratz Stromeko at NexGo.DE writes:
Not the token privileges, I don't think so. But I'm not sure how to check.
If I run the sshd as the user trying to log in, then it works; regardless of
whether the user has administrative privileges or not or with or without
privilege separation enabled
Dat Head writes:
I have a symlink from /usr/local/bin to /3TB-external/bin/CYGWIN to keep
architecture independent bin files on an external drive for portability.
Just create a mount in /etc/fstab and keep the tree under the mount
point empty.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305
Corinna Vinschen writes:
For simplicity I added this experimental patch to the snapshot I just
uploaded to https://cygwin.com/snapshots/.
I'm ooO so no updates from me on this until I get back.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Factory and
Corinna Vinschen writes:
I think I found the bug. I missed the trailing \0 from the user name
in the packet length sent to cygserver. I fixed that in CVS and uploaded
a new snapshot to https://cygwin.com/snapshots/. Please test.
Thanks. As I said in the other thread, it'll be some time
Launch cmdline programs with hidden console via run.
Notes:
The maintainer of run, Charles Wilson, can currently not be reached. We
hope he is well and just busy with other things. I have taken over
maintenance temporarily.
Changes:
1.3.2-1 (bugfix release)
* src/run.c: Revert a
Gerry Reno writes:
Reran setup on a XP machine this afternoon (Base only) and when I bring up a
cygwin term I see this:
/etc/profile: line 136: /usr/bin/hostname: No such file or directory
Previously:
$ which hostname
/usr/bin/hostname
Previously, this was in coreutils, but
Gary Johnson writes:
After much fiddling (programming by successive approximation),
You should drop the cargo-cult programming before it hurts you.
I came up with this:
@START C:\cygwin\bin\mintty.exe /bin/bash --login -c cd $(cygpath
-u $0); exec bash -i %~p1\
You want at least
Gerry Reno writes:
When I rerun Setup and update them they have coreutils but no hostname
package.
The hostname package does not get added.
I've just checked it again and it does get added when it's missing, just
like all other packages in the Base category. It gets removed again
however
Sebastien Vauban writes:
The problem would be with Cygwin in general, then, if not limited to
Emacs.
But why the same fonts (Consolas, Lucida Console) don't display the same
range of characters in both worlds?
You seem to assume that those fonts define that particular glyph. Both
fonts you
Corinna Vinschen corinna-cygwin at cygwin.com writes:
cygserver: bad request body length: got 11
I think I found the bug. I missed the trailing \0 from the user name
in the packet length sent to cygserver. I fixed that in CVS and uploaded
a new snapshot to https://cygwin.com/snapshots/.
Arend Rensink writes:
25-9-2014 10:54:05 Quarantined legal software that can be used by
criminals to damage your computer or personal data
PDM.Worm.P2P.generic C:\CYGWIN\SETUP-X86.EXE
(I don't suppose there is a worm, but you might be interested in knowing
about this false positive.)
Christian Franke writes:
According to VirusTotal, some Bkav scanner reports a false positive
for both current setup.exe versions:
https://www.virustotal.com/file/ea2a2322ccce15af2b68b36f0543f263529422baf41480d4f96b320a55289d71/analysis/1411478277/
Jon TURNEY writes:
Any chance this can be promoted to current? It seems that --quote is
necessary for commands of the form 'run /usr/bin/bash -l -c command
args' to work, which are used quite a lot in X start menu items
(e.g. see [1]).
It's possible (if tedious in some instances) to arrange
Andy AndyMHancock at gmail.com writes:
According to http://www.vox.com/2014/9/25/6843949/the-bash-bug-explained,
shellshock is exploited when someone submits commands in place of parameter
data to a server, which then tries to shove the info into an environment
variable by a bash invocation.
Eric Blake ebb9 at byu.net writes:
This build is also the first against the
new ACL rules of cygwin1.dll, so there may be some oddities in ls as a
result.
That hunch proved to be correct, but it is cp and not ls that is affected:
cp -vr gnuplot.x86_64/dist/gnuplot
Eric Blake (cygwin) writes:
A new release of bash, 4.1.13-6, has been uploaded and will soon reach a
mirror near you; leaving the previous version at 4.12-5.
Just out of curiosity, why is this release version -6 instead of -1?
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb
Eric Blake writes:
Can you give me a simple self-contained script that creates all
necessary prerequisites before attempting the failing 'cp', to help me
in trying to reproduce what is going differently here?
I'll see what I can come up with.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305
Eric Blake writes:
On 09/29/2014 10:14 AM, Achim Gratz wrote:
Eric Blake (cygwin) writes:
A new release of bash, 4.1.13-6, has been uploaded and will soon reach a
mirror near you; leaving the previous version at 4.12-5.
Just out of curiosity, why is this release version -6 instead of -1
Eric Blake eblake at redhat.com writes:
Can you give me a simple self-contained script that creates all
necessary prerequisites before attempting the failing 'cp', to help me
in trying to reproduce what is going differently here?
As an admin do (replace user with any user that is not the admin
Eric Blake eblake at redhat.com writes:
Sounds like cygwin's base-files should be updated to guard
cygwin-specific .profile contents to only occur when uname says it is
running on cygwin. I'm sure the maintainer would love patches...
I'm listening... although default ~/.profile only gets
This release brings RCS to version 5.9.3 for both architectures. A
slightly modified version of the patch for the RCS work file corruption
problem is now included in the upstream sources along with a test, so no
Cygwin specific patches need to be applied.
--8---cut
Version 1.3.3 of run, previously available as a test release, is
promoted to current. This version adds a new option --quote that
effects automatic re-quoting of arguments continaing whitespace or
backslash characters suitabe for the MS-CRT. Please note that some
progams implement their own
Angelo Graziosi writes:
Why, now, does setup want to install also the run-debuginfo packages?
I uploaded the wrong setup.hint file to the run-debuginfo directory.
It's now fixed and should show up on the mirrors soon. You can delete
the debuginfo package from your installation on the next
Marcin Kurczewski rr- at sakuya.pl writes:
It seems the --directory switch is ineffective when used with --action=runas
when using cygstart. For example:
cygstart --action=runas --directory=`cygpath -wa $PWD` cmd.exe /k dir
The expected output is the contents of the working directory of
Dave Kilroy writes:
That was my conclusion as well*. Question is, should fish provide the
configuration, or should base-files cover all shells?
Since fish isn't in Base and deviates quite a bit from the classic
shells in its startup behaviour, I don't really think it would be
appropriate.
LMH writes:
Good Lord, I guess I wasn't thinking very clearly trying to use PATH as
a variable for something else. I changed to,
FILE_DIR=$(ls -d './'$SET'/'$FOLD'/'$FOLD'_anneal/'$PARAM_SET'/'$AN_SET)
echo $FILE_DIR
FILE_LIST=($(ls $FILE_DIR'/'*'out.txt' ))
echo ${FILE_LIST[@]}
and
Nellis, Kenneth writes:
I haven't changed my ~/.emacs file since 2012, but sometime in the
last several weeks I've noticed changes in emacs behavior.
1. I've never turned on automatic indentation--don't actually know
how--yet if I indent a new line by pressing the tab key, when I hit
the
Jim Garrison jhg at jhmg.net writes:
This is a newly built win7.1 x64 system with Cygwin 32-bit
installed. I recently ran the Cygwin installer to get updates
and at the end of installation in the log I see:
2014/10/13 23:29:18 running: cmd.exe /c
C:\cygwin\etc\postinstall\autorebase.bat
Eric Blake eblake at redhat.com writes:
D'oh - now I see it. In my .exe code additions, I had added a '!= 0'
test that should have really been a ' 0' test; because directories
cause an expected -1 return that should not have triggered an attempt at
.exe magic. -4 coming soon.
Fix confirmed.
I've ran into some strange problem with the snapshots. This seems to be getting
complicated, so I'm throwing it out here in the hope someone has an
idea. I've boiled it down to a minimal Cygwin (32bit, but it's
happening in 64bit too) installation, plus perl and perl_vendor. As
installed
$
Corinna Vinschen writes:
lwp-request is one of the tools using connect to try if a former
non-blocking connect worked. This is ugly but, sigh, valid behaviour,
What should it be doing instead? LWP upstream has switched to a new
maintainer recently IIRC, so it might be a good time to suggest a
Jon TURNEY writes:
Any chance this can be promoted to current? It seems that --quote is
necessary for commands of the form 'run /usr/bin/bash -l -c command
args' to work, which are used quite a lot in X start menu items
(e.g. see [1]).
I would appreciate if you could let me know if that
Corinna Vinschen corinna-cygwin at cygwin.com writes:
Oh, good! I just realized that I missed to handle EALREADY, so I
applied YA patch and just replaced the snapshot with a new one.
The snapshot fixes things in the minial test installation. I'll update my
other systems later today.
Achim Gratz Stromeko at NexGo.DE writes:
The snapshot fixes things in the minial test installation. I'll update my
other systems later today.
The new snapshot works fine on all systems I've installed it on so far.
Regards,
Achim.
--
Problem reports: http://cygwin.com/problems.html
Marco Atzeri writes:
Use make NUM_THREADS=n to support n threads.
Wait, what?
So how many THREADS would you like to see ?
It should determine the number of cores at runtime as well as the level
of SSE/AVX support: i686 starts with the PentiumPro, which didn't have
SSE. Fixing this at
Corinna Vinschen writes:
In theory, no. The last OpenSSH update, 6.7p1-1, alreadyd contained
the upstream fix to work with local sshd accounts which have the
machine name prepended.
I will check this tomorrow, I somehow missed that this patch was live.
The entry for sshd was the only thing
John Wiersba writes:
Maybe I'm confused. Isn't the purpose of run.exe to start a
cygwin program without creating a (visible) console window?
The purpose of run is to start a Windows program that needs a console to
exist and hide the console window created by windows if there is no
console that
Tom Schutter writes:
On Wed 2014-10-22 11:23, Corinna Vinschen wrote:
The major change in this new release is the new method to read account
(passwd and group) information from the Windows user databases directly,
without the requirement to generate /etc/passwd and /etc/group files to
Achim Gratz writes:
Corinna Vinschen writes:
In theory, no. The last OpenSSH update, 6.7p1-1, alreadyd contained
the upstream fix to work with local sshd accounts which have the
machine name prepended.
I will check this tomorrow, I somehow missed that this patch was live.
The entry
Corinna Vinschen writes:
Yes, flags register corruption is exactly what Eli suggested in the other
bug report I cited.
The aforementioned patch was supposed to fix this problem and it is
definitely in the current 1.7.32 release...
Emacs uses a bunch of libraries and also messes itself
John Wiersba writes:
Is this not a bug in run.exe?
No, if anything it's a bug in Windows. Look in the archives at the
beginning of 2009 where this was discussed. You can at least hide the
window after it exists now, but the option of starting it out of sight
has been removed with Windows 7 and
Am 27.10.2014 um 23:40 schrieb Warren Young:
Why did setup.exe just get 7x larger, relative to 2.850?
Not compressed by UPX, I suppose.
--
Achim.
(on the road :-)
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation:
Corinna Vinschen writes:
Not stripped before compressing, actually. Fixed now.
I once offered a Makefile patch to add a target to make stripped and
compressed binaries. Cristopher didn't like it, but I could offer it
again since I've kept it on a local branch.
Regards,
Achim.
--
+[Q+
Steven Penny writes:
On Fri, Aug 9, 2013 at 12:17 PM, Steven Penny wrote:
Because of this dependency line
This issue is back again, now with
bash
_update-info-dir
texinfo
perl
Texinfo5 is implemented in Perl. Unless install-info gets split into a
separate package that
Corinna Vinschen writes:
Off the top of my head I don't know how hard that would be, but it
doesn't sound like an especially bad idea to me. Au contraire.
It should be quite easy since the postinstall scripts are run in POSIX
sort order. Just give the script a name like 1_autorebase.bat
Ken Brown writes:
That's now what I see here, unless I'm badly confused about what POSIX
sort order is. I did an update a few days ago in which the
postinstall scripts were run in the following order:
update-info-dir.sh
autorebase.bat
wget.sh
Yes you are right. Sorry, I should have
cyg Simple writes:
I wasn't asking for help; I have a working install. I was stating the
possibility of making Cygwin better.
You haven't made an argument in which way having /usr/share be a mount
point would be an improvement over the current situation where it is
simply a directory.
Too
Nellis, Kenneth writes:
Jeremy's solution is closest to what I was looking for; however
I need it to work from a networked, non-drive-mapped folder.
(CMD.EXE doesn't like UNC paths.) I hadn't realized that I could
pipe a script into bash.
The solution to the UNC path problem is to put
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
Corinna Vinschen corinna-cygwin at 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
Corinna Vinschen corinna-cygwin at 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
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
more
Corinna Vinschen writes:
On Nov 11 10:02, Ken Brown wrote:
Of course, this still doesn't solve the problem of making sure that the
_autorebase postinstall script runs whenever the user installs a package
containing DLLs. I wonder if we should reconsider Achim's proposal. If I
understand
Corinna Vinschen writes:
I understand that you're patching setup to recognize the autorebase
package by name, but how does it recognize other perpetual postinstall
scripts ATM?
I actually match an _always suffix before the file extension. So once
such a file gets installed in
t s furriner67 at hotmail.com writes:
What is the function of the keep / cur / exp radio buttons?
It changes what the Default means: keep the installed packages, update to
whatever the current version is or update to whatever the experimental or
test version is.
Regards,
Achim.
--
Problem
Corinna Vinschen writes:
Incremental autorebase packages and patched setup.exe available on
request.
I'd like to see them. Thanks.
I'll upload them on the weekend latest, I'm a bit swamped at work. I'll
follow up on this in cygwin-applications.
Yes, me too.
Achim, does your perpetual
501 - 600 of 4234 matches
Mail list logo
