>> -Original Message-
>> From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
Behalf
>> Of Dave Korn
>> Sent: Tuesday, February 03, 2009 12:40 PM
>> To: cygwin@cygwin.com
>> Subject: Re: date generates a "\r"
>>
>>Well this stuff don't look good:
>>
>> Missing file: /usr
hi,
How about if i make SYSTEM user as root in cygwin and
Administrators
Group as root Group, even install Cygwin 1.7 by SYSTEM
user, Does it
effect on Cygwin working in any way.
Add more friends to your messenger and enjoy! Go to
http://messenger.yahoo.com/invite/
--
Unsubscribe
Arun Biyani wrote:
No, the fix is to quit using linefeeds in your script files unless you
are
willing to teach bash to ignore those line feeds. d2u is your friend.
Attached are the relevant files. I don't see where the problem is.
Well this stuff don't look good:
Missing file: /usr/bin
Charles Wilson wrote:
I ran across an oddity in the cygwin headers today.
has
typedef long int32_t
typedef unsigned long uint32_t
Now, on cygwin, there's no real harm. But from the C standard, long and
int are distinct types, so the following:
This is the 32-bit equivalent of the exact
Hey Guys,
I just Love the Cygwin Work by cygnus, even if nobody here replies or in
any way answer to my Question/Problems. Its really good what i realy like
was how it gets windows into linux like enviorment, Coz of this i almost
created WCAMP Layout on Windows XP and even did that Webmin+Virtua
> No, the fix is to quit using linefeeds in your script files unless you
are
> willing to teach bash to ignore those line feeds. d2u is your friend.
Attached are the relevant files. I don't see where the problem is.
cygcheck.log
Description: cygcheck.log
crontab.log
Description: crontab.log
>> No, the fix is to quit using linefeeds in your script files
>> unless you are willing to teach bash to ignore those line
>> feeds. d2u is your friend.
I ran dos2unix on that script. Its not the script.
I use emacs as editor. "crontab -e" invokes emacs. Maybe the crontab
file has something in
On Tue, Feb 3, 2009 at 12:39 PM, Arun Biyani wrote:
>>Please don't commandeer threads.
>
> A little puzzled. Are there parts to the message I did not see?
Yes. Every email message has many headers with metadata. Your mail
program may provide an option to view them ("show all headers", "show
ori
>-Original Message-
>From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On
Behalf Of >Eric Blake
>Sent: Tuesday, February 03, 2009 11:16 AM
>To: cygwin@cygwin.com
>Subject: Re: date generates a "\r"
>>Arun Biyani dickey-john.com> writes:
>> [log$:513] name=$(date +tiny-%b-%d
Arun Biyani dickey-john.com> writes:
> [log$:513] name=$(date +tiny-%b-%d-%g)
> [log$:514] bakup=$name.tz
>
> The assignments above result in bakup being
> "/c/home/bak/tiny-Feb-02-g\r.tz". I'd like to understand why this
> happens
Please don't commandeer threads. The answer to your question
On Tue, Feb 03, 2009 at 12:06:49PM -0500, Charles Wilson wrote:
>I ran across an oddity in the cygwin headers today.
This boils down to "What does linux do?". If we are doing something
different then PTC.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports:
I ran across an oddity in the cygwin headers today.
has
typedef signed int __int32_t;
unsigned int __uint32_t;
has
typedef long int32_t
typedef unsigned long uint32_t
has
typedef __uint32_t u_int32_t;
What this means is that these public types don't match (exactly)
uint32_t == unsigned long
I find that every time I upgrade openssh it breaks and I have to run:
chmod 755 /usr/sbin/* /usr/bin/*
It seems silly, but this is something I end up having to do on all/any
of my machines every time for years (my notes are dated 2004).
I can't help but think that there's something I'm missing
I read with interest the problems with getting good time stamps from modern
PC Systems that hibernate.
I've been working on a different problem, and it occurs to me that a
utility of Windows can be used to solve this problem, if you don't mind
doing it in a non-GNUish way.
There's a console prog
[log$:513] name=$(date +tiny-%b-%d-%g)
[log$:514] bakup=$name.tz
The assignments above result in bakup being
"/c/home/bak/tiny-Feb-02-g\r.tz". I'd like to understand why this
happens
when the script is being run from cron (but not when I run it in a bash
shell). Is the fix is to put "/usr/bin/da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A new version of the asciidoc package, asciidoc 8.3.5-1, is now available
for download, replacing 8.3.1-2 as current.
NEWS:
=
This is a new upstream release; upstream changes are listed below. See
also the package documentation in /usr/share/doc/
16 matches
Mail list logo
