This is the mail archive of the
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT] New release of setup.exe (126.96.36.199)
- From: Markus Schönhaber <mks99 at t-online dot de>
- To: cygwin at cygwin dot com
- Date: Thu, 13 Mar 2003 23:45:58 +0100
- Subject: Re: [ANNOUNCEMENT] New release of setup.exe (188.8.131.52)
- References: <20030313205847.E1E4B1C221@redhat.com>
Robert Collins wrote:
I'm happy to announce a new release of setup.exe. It will *improve* the
display of permissions for use with the ntsec setting of cygwin (which
is the default now) in the majority of cases. More fine tuning may be
needed but our calls for exhaustive testing have met the same fate as
the calls to test this set of snapshots of setup.exe.
Did a fresh install at my XP-Prof box at home - moving the directories and
registry keys out of th way beforehand. I just now realize, I forgot to
remove the CYGWIN environment variable. Don't know if this has any
influence on the installation process.
Two things pose some concern to Pierre, who developed the setup/ntsec
code: domain users and the Windows popup asking if setup should run as
Seems to me that almost everything has worked fine (haven't intensively
tested though). Just, when the postinstall script ran, I was able to read
a message saying that the domain controller wasn't found. Seems to me,
this message came from mkpasswd (is it called with the -d param in
postinstall?). Anyway, after the installation my /etc/passwd and
/etc/group files didn't exactly exceed my harddisk's capacity:
I should mention that this machine isn't member of a domain. The contents
of the files reflect the output of mk(passwd|group) -d:
$ mkpasswd -d
mkpasswd:  Domänencontroller für diese Domäne konnte nicht gefunden
(this means something like: DC for this domain couldn't be found.)
I did mk(passwd|group) -l manually and everything seems fine now.
Read/execute permission was set for owner and group (Users) for all files
in /bin. So i guess the problem of bash not finding some executables when
logged in with other credentials should be gone now. Most files seem to
have no permission for "other"s.
Since I did the installation logged in under an administrator account
there wasn't any need for setup to ask wether it should run as
Administrator - and it didn't ask.
An additional change in this release is the ability to use http proxies
that require a username with an empty password.
To download this version, simply click on the 'install cygwin now' link
on the cygwin homepage, or wait for setup.exe to be copied out to your
If there is more that you would like to see tested...
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html