On 2019-03-28 15:36, Bill Stewart wrote:
> I am trying to understand the limitations when running sshd using the
> SYSTEM account.
> Is the following complete and correct?
> ==
> OS_version* OS_bitness sshd_bitness Notes
> --
> < 6.3
On 2019-03-28 10:48, Michael Haubenwallner wrote:
> On 3/28/19 4:19 PM, Brian Inglis wrote:
>> On 2019-03-28 08:59, Michael Haubenwallner wrote:
>>> On 3/27/19 8:59 PM, Achim Gratz wrote:
Michael Haubenwallner writes:
> As far as I understand, rebasing is about touching already installed
On 3/28/2019 4:13 PM, Corinna Vinschen wrote:
> On Mar 28 19:01, Achim Gratz wrote:
>> Corinna Vinschen writes:
>>> Done. I also pushed out new dev snapshots.
>>
>> No good deed goes unpunished…
>>
>> Whith the 20190327 snapshot our main data processing application is
>> broken. It looks like it
On Thu, 28 Mar 2019 22:33:48, Thomas Wolff wrote:
It's a bit strange that you're telling my that *you* don't care about
*my* information.
I'm trying to raise some awareness about privacy on this occasion (which
is quite a topic nowadays) and if you don't care, you don't need to comment.
Yeah,
Am 28.03.2019 um 20:47 schrieb Achim Gratz:
Thomas Wolff writes:
I do not like the dual chaos of manual vs info pages, and I'm maybe a
bit old-fashioned to insist that manual pages should be complete, but
isn't that their purpose?
You are barking up the wrong tree, but if you're that bothered
I am trying to understand the limitations when running sshd using the
SYSTEM account.
Is the following complete and correct?
==
OS_version* OS_bitness sshd_bitness Notes
--
< 6.364-bit 32-bitNote 1
< 6.3
Am 28.03.2019 um 19:38 schrieb Vince Rice:
On Mar 28, 2019, at 1:33 PM, Thomas Wolff wrote:
Am 28.03.2019 um 19:16 schrieb Vince Rice:
On Mar 28, 2019, at 1:09 PM, Thomas Wolff wrote:
A potential solution is, add another user to your system named cygwin.
When you build you packages use the
Michael,
On Mar 28 12:48, Michael Haubenwallner wrote:
> On 3/28/19 10:58 AM, Corinna Vinschen wrote:
> > On Mar 28 10:17, Michael Haubenwallner wrote:
> >> As it is not some other dll being loaded at the colliding adress: any
> >> idea how to find out _what_ is allocated there (in the forked
On Mar 28 21:13, Corinna Vinschen wrote:
> On Mar 28 19:01, Achim Gratz wrote:
> > Corinna Vinschen writes:
> > > Done. I also pushed out new dev snapshots.
> >
> > No good deed goes unpunished…
> >
> > Whith the 20190327 snapshot our main data processing application is
> > broken. It looks
On Mar 28 19:01, Achim Gratz wrote:
> Corinna Vinschen writes:
> > Done. I also pushed out new dev snapshots.
>
> No good deed goes unpunished…
>
> Whith the 20190327 snapshot our main data processing application is
> broken. It looks like it should almost work, it doesn't crash or
> anything,
On Mar 28 19:36, Achim Gratz wrote:
> Thomas Wolff writes:
> > Am 28.03.2019 um 19:11 schrieb
> > cygwin-no-reply-rdbxbdvo6bxqt0dzr+a...@public.gmane.org:
> >> ERROR: file 'mintty-debuginfo-3.0.0-1.hint' in package 'mintty' contains
> >> '-' in version
> >> ERROR: file
Thomas Wolff writes:
> I do not like the dual chaos of manual vs info pages, and I'm maybe a
> bit old-fashioned to insist that manual pages should be complete, but
> isn't that their purpose?
You are barking up the wrong tree, but if you're that bothered by it,
you can file an RFE or bug report
adding the original sender as unlikely he is subscribed to this
mailing list
Am 28.03.2019 um 19:43 schrieb Björn Stabel:
Had you pasted the message like a normal human being, you would have a
reply by now since there's a bot for that.
And an faq entry:
Had you pasted the message like a normal human being, you would have a
reply by now since there's a bot for that.
And an faq entry:
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
And you could just throw the whole thing into google and it'll probably
lead you to the faq
> On Mar 28, 2019, at 1:33 PM, Thomas Wolff wrote:
>
> Am 28.03.2019 um 19:16 schrieb Vince Rice:
>>> On Mar 28, 2019, at 1:09 PM, Thomas Wolff wrote:
>>>
A potential solution is, add another user to your system named cygwin.
When you build you packages use the cygwin user. The debug
Am 28.03.2019 um 19:27 schrieb Thomas Wolff:
Am 28.03.2019 um 19:11 schrieb cygwin-no-re...@cygwin.com:
ERROR: file 'mintty-debuginfo-3.0.0-1.hint' in package 'mintty'
contains '-' in version
???
Just a guess, your tree is
x86/release/mintty/mintty-3.0.0-1-src.tar.xz
Thomas Wolff writes:
> Am 28.03.2019 um 19:11 schrieb
> cygwin-no-reply-rdbxbdvo6bxqt0dzr+a...@public.gmane.org:
>> ERROR: file 'mintty-debuginfo-3.0.0-1.hint' in package 'mintty' contains '-'
>> in version
>> ERROR: file 'mintty-debuginfo-3.0.0-1.hint' in package 'mintty' has a
>> version
Screen: https://ctrlv.cz/Kdic
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Am 28.03.2019 um 19:16 schrieb Vince Rice:
On Mar 28, 2019, at 1:09 PM, Thomas Wolff wrote:
A potential solution is, add another user to your system named cygwin.
When you build you packages use the cygwin user. The debug information
will reference your cygwin user, and not your real user
Am 28.03.2019 um 19:21 schrieb Achim Gratz:
Thomas Wolff writes:
In fact that seems to work, although there is no TAR_OPTIONS
documented in the manual page.
The already much too long manual page does tell you to consult the info
manual right at the top, does it not?
I do not like the dual
Am 28.03.2019 um 19:11 schrieb cygwin-no-re...@cygwin.com:
ERROR: file 'mintty-debuginfo-3.0.0-1.hint' in package 'mintty' contains '-' in
version
ERROR: file 'mintty-debuginfo-3.0.0-1.hint' in package 'mintty' has a version
which doesn't start with a digit
ERROR: file
On 2019-03-28 7:36 am, Steven Penny wrote:
On Thu, 28 Mar 2019 08:34:34, Thomas Wolff wrote:
Mintty can be used to run any command-line application directly (like
top, your editor, ...), a shell is not needed.
That may be true, the by default Mintty is configure to load Bash. So
it is
Thomas Wolff writes:
> In fact that seems to work, although there is no TAR_OPTIONS
> documented in the manual page.
The already much too long manual page does tell you to consult the info
manual right at the top, does it not?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb
> On Mar 28, 2019, at 1:09 PM, Thomas Wolff wrote:
>
>> A potential solution is, add another user to your system named cygwin.
>> When you build you packages use the cygwin user. The debug information
>> will reference your cygwin user, and not your real user account.
> Thanks for the suggestion,
On Fri, Mar 15, 2019 at 8:25 AM Brian Inglis wrote:
> ... corporate policies, proxies, firewalls, security products.
> Systems or images older than a year may need the new root CA installed - some
> enterprises are very selective about including support for anything in their
> images - and users
Am 28.03.2019 um 15:02 schrieb Jeffrey Walton:
On Thu, Mar 28, 2019 at 4:44 AM Thomas Wolff wrote:
...
Björn Stabel wrote:
On 27/03/2019 23:59, Yaakov Selkowitz wrote:
On Wed, 2019-03-27 at 21:02 +0100, Thomas Wolff wrote:
I used to use tar rather than cygport package to generate the
Am 28.03.2019 um 18:40 schrieb Achim Gratz:
Björn Stabel writes:
Sorry for commenting from the peanut gallery, but his problem may be
that he doesn't want to disclose his user name to anyone nosy enough to
snoop around in the package files.
Not tested, but something like
env
Corinna Vinschen writes:
> Done. I also pushed out new dev snapshots.
No good deed goes unpunished…
Whith the 20190327 snapshot our main data processing application is
broken. It looks like it should almost work, it doesn't crash or
anything, but the pipe that delivers a script+data into
Michael Haubenwallner writes:
> It will not help for conflicts between dlls within a single package while this
> package is built. I'm thinking of python modules built within the python
> package
> itself, where the just built modules are used within the very build process.
> Not
> sure if
Björn Stabel writes:
> Sorry for commenting from the peanut gallery, but his problem may be
> that he doesn't want to disclose his user name to anyone nosy enough to
> snoop around in the package files.
Not tested, but something like
env TAR_OPTIONS="--user=0 --group=0" cygport ...
should do
Thomas Wolff writes:
> Mintty can be used to run any command-line application directly (like
> top, your editor, ...), a shell is not needed.
Your _package_ has a dependency to the shell by way of including a shell
script. If you so desperately want to get rid of it (even though it's
always
On 3/28/19 4:19 PM, Brian Inglis wrote:
> On 2019-03-28 08:59, Michael Haubenwallner wrote:
>> On 3/27/19 8:59 PM, Achim Gratz wrote:
>>> Michael Haubenwallner writes:
As far as I understand, rebasing is about touching already installed
dlls as well, which would require to restart all
On Mar 28 16:02, Michael Haubenwallner wrote:
> On 3/28/19 10:15 AM, Corinna Vinschen wrote:
> > On Mar 28 09:34, Michael Haubenwallner wrote:
> >> Hi Corinna,
> >>
> >> On 3/27/19 10:16 AM, Corinna Vinschen wrote:
> >>> On Mar 27 09:26, Michael Haubenwallner wrote:
> On 3/26/19 7:28 PM,
Hi,
Hope all is well.
Would you be interested in procuring the Attendees list of RAPID + TCT- 2019
?
Fields of Information: Company Name, Contact Name, Title, Phone Number,
Website Address, Mailing Address, Industry, SIC Code, No of Employee,
Revenue Size, Contact Person Permission Based
On 2019-03-28 08:59, Michael Haubenwallner wrote:
> Hi Achim,
>
> On 3/27/19 8:59 PM, Achim Gratz wrote:
>> Michael Haubenwallner writes:
>>> As far as I understand, rebasing is about touching already installed
>>> dlls as well, which would require to restart all Cygwin processes.
>>> As the
On 2019-03-28 05:36, Steven Penny wrote:
> On Thu, 28 Mar 2019 08:34:34, Thomas Wolff wrote:
>> Mintty can be used to run any command-line application directly (like top,
>> your editor, ...), a shell is not needed.
>
> That may be true, the by default Mintty is configure to load Bash. So it is
>
On 3/28/19 10:15 AM, Corinna Vinschen wrote:
> On Mar 28 09:34, Michael Haubenwallner wrote:
>> Hi Corinna,
>>
>> On 3/27/19 10:16 AM, Corinna Vinschen wrote:
>>> On Mar 27 09:26, Michael Haubenwallner wrote:
On 3/26/19 7:28 PM, Corinna Vinschen wrote:
>>> Wait, let me understand what's going
Hi Achim,
On 3/27/19 8:59 PM, Achim Gratz wrote:
> Michael Haubenwallner writes:
>> As far as I understand, rebasing is about touching already installed
>> dlls as well, which would require to restart all Cygwin processes.
>> As the problem is about some dll built during a larger build job,
>>
On Thu, Mar 28, 2019 at 4:44 AM Thomas Wolff wrote:
> ...
> Björn Stabel wrote:
> > On 27/03/2019 23:59, Yaakov Selkowitz wrote:
> >> On Wed, 2019-03-27 at 21:02 +0100, Thomas Wolff wrote:
> >>> I used to use tar rather than cygport package to generate the packages.
> >>> One reason was that I
On Mar 28 12:48, Michael Haubenwallner wrote:
> On 3/28/19 10:58 AM, Corinna Vinschen wrote:
> > On Mar 28 10:17, Michael Haubenwallner wrote:
> >> As it is not some other dll being loaded at the colliding adress: any
> >> idea how to find out _what_ is allocated there (in the forked child),
> >>
On 3/28/19 10:58 AM, Corinna Vinschen wrote:
> On Mar 28 10:17, Michael Haubenwallner wrote:
>> As it is not some other dll being loaded at the colliding adress: any
>> idea how to find out _what_ is allocated there (in the forked child),
>> to find out whether we can reserve these areas even more
On Thu, 28 Mar 2019 08:34:34, Thomas Wolff wrote:
Mintty can be used to run any command-line application directly (like
top, your editor, ...), a shell is not needed.
That may be true, the by default Mintty is configure to load Bash. So it is
disingenuous so simply say that it does not require
On Mar 28 10:17, Michael Haubenwallner wrote:
> As it is not some other dll being loaded at the colliding adress: any
> idea how to find out _what_ is allocated there (in the forked child),
> to find out whether we can reserve these areas even more early?
I'm not sure what addresses you're
On Mar 28 09:43, Thomas Wolff wrote:
> Achim Gratz wrote:
> >
> > > Trying cygport package, a bunch of problems arise:
> > >
> > > I removed -s as suggested by Achim, added -g as advised by Corinna,
> > > but cygport still says:
> > > *** Info: No debug files, skipping debuginfo subpackage
> >
On 3/28/19 9:34 AM, Michael Haubenwallner wrote:
> On 3/27/19 10:16 AM, Corinna Vinschen wrote:
>> On Mar 27 09:26, Michael Haubenwallner wrote:
>>> On 3/26/19 7:28 PM, Corinna Vinschen wrote:
On Mar 26 19:25, Corinna Vinschen wrote:
> On Mar 26 18:10, Michael Haubenwallner wrote:
On Mar 27 21:29, Ken Brown wrote:
> Make fhandler_base::clear_readahead virtual, and implement
> fhandler_fifo::clear_readahead. This is called by
> dtable::fixup_after_exec; it clears the readahead in each client.
> ---
> winsup/cygwin/fhandler.h | 8 +++-
> 1 file changed, 7 insertions(+),
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=023c107a22ebd2f540fa3f4888535aad32839fe2
commit 023c107a22ebd2f540fa3f4888535aad32839fe2
Author: Michael Haubenwallner
Date: Tue Mar 26 17:38:36 2019 +0100
Cygwin: fork: reserve dynloaded dll areas earlier
In dll_crt0_0,
https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=e0fd15c91b206ff788148b8dd2a37a80c8cad175
commit e0fd15c91b206ff788148b8dd2a37a80c8cad175
Author: Ken Brown
Date: Wed Mar 27 21:29:21 2019 +
Cygwin: FIFO: implement clear_readahead
Make fhandler_base::clear_readahead
Achim Gratz wrote:
Trying cygport package, a bunch of problems arise:
I removed -s as suggested by Achim, added -g as advised by Corinna,
but cygport still says:
*** Info: No debug files, skipping debuginfo subpackage
Well, do not reset CFLAGS in your Makefile and cygport helpfully
provides
Hi Corinna,
On 3/27/19 10:16 AM, Corinna Vinschen wrote:
> On Mar 27 09:26, Michael Haubenwallner wrote:
>> On 3/26/19 7:28 PM, Corinna Vinschen wrote:
>>> On Mar 26 19:25, Corinna Vinschen wrote:
On Mar 26 18:10, Michael Haubenwallner wrote:
> Hi Corinna,
>
> as I do still
Am 28.03.2019 um 04:42 schrieb Steven Penny:
On Wed, 27 Mar 2019 20:44:44, Brian Inglis wrote:
Both dash and bash are in Base, installed by default, and both are login
shells, while dash requires only cygwin1.dll to run, and can be used
during
setup, before other libraries or utilities are
On 27/03/2019 23:59, Yaakov Selkowitz wrote:
> On Wed, 2019-03-27 at 21:02 +0100, Thomas Wolff wrote:
>> I used to use tar rather than cygport package to generate the packages.
>> One reason was that I didn’t want my local user/group to appear in them.
> They won't show up like that once
52 matches
Mail list logo
