Hi
The following is a list of packaging bugs/anomalies I discovered after a
complete fresh installation of cygwin64 on Windows 7:
Packaging bugs:
o tig-2.0.2-1
/usr/etc/tigrc -> /etc/tigrc (should use /etc/defaults mechanisms)
o docbook-utils-0.6.14-2
/usr/doc/html -> /usr/share/
On Tue, 2015-02-24 at 22:33 +0100, Teun Burgers wrote:
> the libgmon.a is an empty archive. These are the contents of
> /usr/i686-pc-mingw32/sys-root/mingw/lib/libgmon.a
>
> This becomes a problem when attempting to prepare an executable for profiling
> with gprof
>
> /bin/i686-pc-mingw32-gcc.ex
Corinna Vinschen writes:
> Having discussed this, I can understand that it may be desirable to
> skip the permissions of the SYSTEM account in these circumstances:
>
> - Computing the POSIX ACL mask and default mask value and thus in
> the permission mask as printed by `ls -l'.
>
> - Changing SYS
Umm... Sorry! I hope it's clear to all, I meant Corinna !
On 2/26/2015 9:27 PM, random user wrote:
>> Regarding Corrinne's proposal to treat SYSTEM's ACE distinct from others
>> in forming the apparent group permission "mask":
>>
>> Might it be sensible to do somewhat similar for the case where a
Regarding Corrinne's proposal to treat SYSTEM's ACE distinct from others
in forming the apparent group permission "mask":
Might it be sensible to do somewhat similar for the case where a file's
owner is the same as its primary group (i.e., same SID)? It has seemed
the chmod behavior for this case
Thank you for your response. It may sound plausible but:
> you tell Cygwin that you want posix semantics
I can't remember seeing that posix semantics require a C library call
to modify arguments in the way the shell does; since when cygwin a
shell?
> split arg 2 into two args: "DIR" and "C:\\"
I'm not sure exactly where the bug is, but here's what happens (STC at the end):
1. I use freopen to open a file "foo" and associate it with stdin.
2. I use fread to read a byte from foo.
3. I call popen, expecting the child process to have foo as its stdin, with the
file-position indicator po
Greetings, Corinna Vinschen!
>> Having discussed this, I can understand that it may be desirable to
>> skip the permissions of the SYSTEM account in these circumstances:
>>
>> - Computing the POSIX ACL mask and default mask value and thus in
>> the permission mask as printed by `ls -l'.
SYSTEM
Greetings, Corinna Vinschen!
> given that SYSTEM has permissions to read and write all files
> anyway.
Not true.
If SYSTEM don't have access to files, it can't do anything at all.
This is not Linux, system isn't run from root.
> I don't see that a rule to add SYSTEM permissions to all files
> ac
>> Crucial vote starting... now.
Given my original post, I'm obviously fan of ignoring SYSTEM
(S-1-5-18) explicitly. As much as the absolutist programmer in me
doesn't like nuanced exceptions like this, I think it's the pragmatic
thing to do.
--
Problem reports: http://cygwin.com/problems.
On Feb 26, 2015, at 3:39 PM, Darik Horn wrote:
>
> Note that GPG signatures are published for the Cygwin setup binaries:
If someone can MITM the *.exe files, they can MITM the GPG sigs, too.
You could try and be diligent and check that the signature was made with a GPG
key you trust, but I’ll
On 2/26/2015 2:34 PM, Corinna Vinschen wrote:
On Feb 26 14:21, Andrew DeFaria wrote:
On 2/26/2015 12:24 PM, Corinna Vinschen wrote:
On Feb 26 12:04, Andrew DeFaria wrote:
On 2/25/2015 4:12 PM, Yaakov Selkowitz wrote:
On Wed, 2015-02-25 at 15:52 -0800, Andrew DeFaria wrote:
Can somebody summa
On Thu, 26 Feb 2015 23:37:37 +0100, Corinna Vinschen
wrote:
> On Feb 26 17:31, David A. Wheeler wrote:
> > The Cygwin front web page ( https://www.cygwin.com/ ) says:
> > "Install it by running setup-x86.exe (32-bit installation) or
> > setup-x86_64.exe (64-bit installation)."
> >
> Did you noti
On 02/26/2015 03:31 PM, Corinna Vinschen wrote:
> On Feb 26 14:19, Eric Blake wrote:
>> On 02/26/2015 01:24 PM, Corinna Vinschen wrote:
> Fixes are in snapshots, as well as test releases (currently 1.7.35-0.4)
> which can be installed with setup*.exe.
Hmmm... https://cygwin.com/fa
On Feb 26 23:29, Corinna Vinschen wrote:
> Having discussed this, I can understand that it may be desirable to
> skip the permissions of the SYSTEM account in these circumstances:
>
> - Computing the POSIX ACL mask and default mask value and thus in
> the permission mask as printed by `ls -l'.
Note that GPG signatures are published for the Cygwin setup binaries:
* http://cygwin.com/setup-x86.exe.sig
* http://cygwin.com/setup-x86_64.exe.sig
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/doc
On Feb 26 17:31, David A. Wheeler wrote:
> The Cygwin front web page ( https://www.cygwin.com/ ) says:
> "Install it by running setup-x86.exe (32-bit installation) or
> setup-x86_64.exe (64-bit installation)."
>
> However, both of the links to those .exe executables explicitly use
> "http://";, an
On Feb 26 14:21, Andrew DeFaria wrote:
> On 2/26/2015 12:24 PM, Corinna Vinschen wrote:
> >On Feb 26 12:04, Andrew DeFaria wrote:
> >>On 2/25/2015 4:12 PM, Yaakov Selkowitz wrote:
> >>>On Wed, 2015-02-25 at 15:52 -0800, Andrew DeFaria wrote:
> Can somebody summarize where we're at here. I've be
On Feb 26 16:27, Bryan Berns wrote:
> > You just have to enable the SeBackupName and SeRestoreName privs.
> > Try in Cygwin. It does that automatically.
> >
> > For cases where you need to stick to the Windows ACLs, use noacl
> > mounts.
>
> Understood --- I can probably set SeBackupPrivilege /
>
On Feb 26 14:19, Eric Blake wrote:
> On 02/26/2015 01:24 PM, Corinna Vinschen wrote:
> >>> Fixes are in snapshots, as well as test releases (currently 1.7.35-0.4)
> >>> which can be installed with setup*.exe.
> >>
> >> Hmmm... https://cygwin.com/faq-nochunks.html#faq.setup.snapshots says:
> >>
> >>
The Cygwin front web page ( https://www.cygwin.com/ ) says:
"Install it by running setup-x86.exe (32-bit installation) or setup-x86_64.exe
(64-bit installation)."
However, both of the links to those .exe executables explicitly use "http://";,
and not "https://";, even when you go to the https ve
On 2/26/2015 12:24 PM, Corinna Vinschen wrote:
On Feb 26 12:04, Andrew DeFaria wrote:
On 2/25/2015 4:12 PM, Yaakov Selkowitz wrote:
On Wed, 2015-02-25 at 15:52 -0800, Andrew DeFaria wrote:
Can somebody summarize where we're at here. I've been noticing all this
email about slow startup and I'm
On 2015-02-26 21:59, A L wrote:
> Hi,
> Yesterday I asked about the double slash, but my question has got no
> attention (despite some other activity
> on the list). I deem the behavior as a bug. To make things more
> evident (that it's a bug) one can replace "DIR"
> with "ECHO" in the code I pos
> That's an administrator account, not SYSTEM.
The BERNS-WINDOWS$ is the account the process was being run under
(launched via psexec -i -s) and is indeed the system account. I ran
icacls just to display the current ACL on the directory (which does
not include the system account for the purpose o
> You just have to enable the SeBackupName and SeRestoreName privs.
> Try in Cygwin. It does that automatically.
>
> For cases where you need to stick to the Windows ACLs, use noacl
> mounts.
Understood --- I can probably set SeBackupPrivilege /
SeRestorePrivilege as 'RequiredPriveleges' for the
On 02/26/2015 01:24 PM, Corinna Vinschen wrote:
>>> Fixes are in snapshots, as well as test releases (currently 1.7.35-0.4)
>>> which can be installed with setup*.exe.
>>
>> Hmmm... https://cygwin.com/faq-nochunks.html#faq.setup.snapshots says:
>>
>> You cannot use Cygwin Setup to install a snapsho
Hi,
Yesterday I asked about the double slash, but my question has got no
attention (despite some other activity
on the list). I deem the behavior as a bug. To make things more
evident (that it's a bug) one can replace "DIR"
with "ECHO" in the code I posted, and compare the outputs with and
withou
On Feb 26 15:51, Bryan Berns wrote:
> > That's not really a goal. The SYSTEM permissions are kind of useless
> > anyway, given that SYSTEM has permissions to read and write all files
> > anyway. I don't see that a rule to add SYSTEM permissions to all files
> > accomplishes anything which isn't a
Bryan Berns writes:
> I don't think this is true; see below when running as the system account:
That's an administrator account, not SYSTEM.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Sy
> That's not really a goal. The SYSTEM permissions are kind of useless
> anyway, given that SYSTEM has permissions to read and write all files
> anyway. I don't see that a rule to add SYSTEM permissions to all files
> accomplishes anything which isn't already available anyway.
I don't think this
Corinna Vinschen writes:
> That's not really a goal. The SYSTEM permissions are kind of useless
> anyway, given that SYSTEM has permissions to read and write all files
> anyway. I don't see that a rule to add SYSTEM permissions to all files
> accomplishes anything which isn't already available an
On Feb 26 20:47, Achim Gratz wrote:
> Bryan Berns writes:
> > I honestly haven't read up exactly how Cygwin interprets NTFS
> > ACL/ACEs, but I remember seeing on the mailing list that a change was
> > made in 1.7.35 was made to permission handling. It is preferable in
> > my organization that the
On Feb 26 12:04, Andrew DeFaria wrote:
> On 2/25/2015 4:12 PM, Yaakov Selkowitz wrote:
> >On Wed, 2015-02-25 at 15:52 -0800, Andrew DeFaria wrote:
> >>Can somebody summarize where we're at here. I've been noticing all this
> >>email about slow startup and I'm excited by the inclusion of domain
> >>
Greetings, Bryan Berns!
> I honestly haven't read up exactly how Cygwin interprets NTFS
> ACL/ACEs, but I remember seeing on the mailing list that a change was
> made in 1.7.35 was made to permission handling. It is preferable in
> my organization that the SYSTEM account always have full control
On 2/25/2015 4:12 PM, Yaakov Selkowitz wrote:
On Wed, 2015-02-25 at 15:52 -0800, Andrew DeFaria wrote:
Can somebody summarize where we're at here. I've been noticing all this
email about slow startup and I'm excited by the inclusion of domain
accounts using /etc/nsswitch.conf, etc. I downloaded
Bryan Berns writes:
> I honestly haven't read up exactly how Cygwin interprets NTFS
> ACL/ACEs, but I remember seeing on the mailing list that a change was
> made in 1.7.35 was made to permission handling. It is preferable in
> my organization that the SYSTEM account always have full control the
>
On 2015-02-26 17:03, Corinna Vinschen wrote:
>
> On Feb 20 09:25, Achim Gratz wrote:
>> Another thing I noticed is that pasting into an SSH connection often
>> leaves the last few characters off and you need to hit another key to
>> get them displayed. Not sure if this is related, but I seem to r
I honestly haven't read up exactly how Cygwin interprets NTFS
ACL/ACEs, but I remember seeing on the mailing list that a change was
made in 1.7.35 was made to permission handling. It is preferable in
my organization that the SYSTEM account always have full control the
local file system. When usin
On Feb 26 17:19, Achim Gratz wrote:
> Corinna Vinschen writes:
> > On Feb 20 09:25, Achim Gratz wrote:
> >> Another thing I noticed is that pasting into an SSH connection often
> >> leaves the last few characters off and you need to hit another key to
> >> get them displayed. Not sure if this is r
Corinna Vinschen writes:
> On Feb 20 09:25, Achim Gratz wrote:
>> Another thing I noticed is that pasting into an SSH connection often
>> leaves the last few characters off and you need to hit another key to
>> get them displayed. Not sure if this is related, but I seem to remember
>> that this ha
On Feb 20 09:25, Achim Gratz wrote:
> Another thing I noticed is that pasting into an SSH connection often
> leaves the last few characters off and you need to hit another key to
> get them displayed. Not sure if this is related, but I seem to remember
> that this had been reported before and may
On 2015-02-24 Corinna Vinschen wrote:
> On Feb 24 16:16, Lasse Collin wrote:
> > I'm going to release xz 5.2.1 in a day or two. Should that release
> > have a workaround for this Cygwin bug? The workaround would avoid
> > using O_NONBLOCK on stdout. It adds a race condition to signal
> > handling i
On Feb 25 22:20, Roger Orr wrote:
> Good work -- at least in my environment ;-)
>
> 20150225 DLL:
> mkgroup 0.63s
> mkpasswd 0.289s
>
> compared to
>
> 20150220 DLL:
> mkgroup 45.8s
> mkpasswd: 4572.7s
>
> Output is
> mkgroup: 53kb, 681 lines
> mkpasswd: 132kb, 1081 lines.
>
> And the output
43 matches
Mail list logo
