Re: strange bug in gettimeofday function
I would like to add to my previous message that the test fails *sometimes*, approx. once for 7-8 runs. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: strange bug in gettimeofday function
>>>I detected a strange bug in the standard function gettimeofday.
>>>It *sometimes* reports the time which being expressed as the integer
>>>number of milliseconds is *less* than the time obtained *earlier* with
>>>the same function.
>>If you mean that you call gettimeofday twice and you get different
>>values at each call, with a difference of about 100 ms, then this is all
>>right. Read on...
> As the author of the function in question, I would still like to get
> a test case.
Looks like I do not understand something elementary :(
If I compile a test program (see below) with `gcc test.c', it works
fine. However, if I compile it with `gcc -O2 test.c', it fails.
Could anyone please explain me what is hapenning?
#include
#include
#include
double get_time(void)
{ struct timeval tv;
gettimeofday(&tv, NULL);
return (double)tv.tv_sec + 1e-6 * (double)tv.tv_usec;
}
int main(void)
{ double t0 = get_time(), t1 = get_time();
if (t0 > t1)
{ int *t;
printf("sizeof(double) = %d\n", sizeof(double));
t = (int *)&t0;
printf("t0 = %08X %08X\n", t[1], t[0]);
t = (int *)&t1;
printf("t1 = %08X %08X\n", t[1], t[0]);
printf("t1 - t0 = %.20g \n", t1 - t0);
exit(EXIT_FAILURE);
}
return 0;
}
In case of failure the output is the following:
sizeof(double) = 8
t0 = 41D174F7 4F2AE148
t1 = 41D174F7 4F2AE148
t1 - t0 = 0
Thank you,
Andrew Makhorin
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Using the snapshot 20070214
After installing and rebasing (-b 0x6500 as suggested) the current snapshot 20070214, using it I have found these problems. Usually I use Emacs built from CVS. I have found usefull to build it configuring as LDFLAGS='-Wl,--enable-auto-import -Wl,--enable-auto-image-base' \ ./configure... and with GCC 4.0.3 (with GCC-3.4.4-3 the build is unstable). In this way the result not only works fine with recent version of Cygwin (1.5-22,23,24), but is also independent from rebasing and from the base address (as you, perhaps, remember, the current version of Emacs in Cygwin, hangs after rebasing). Now with the snapshot, Emacs-CVS aborts leaving: emacs-22.0.93.exe.stackdump - Stack trace: Frame Function Args 0022B1A8 7C802532 (067C, EA60, 00A4, 0022B1F0) 0022B2C8 610AF43C (, , , ) 0022B3B8 610ACFBB (, 003B0023, 0023, ) 0022B418 610AD49B (0022B430, , 0094, 0095F000) 0022B4D8 610AD652 (0F94, 0006, 006DE801, 61026E43) 0022B508 610AA8B8 (0006, 60FF, 0022B638, 610AF4FC) 0022B5F8 61026F60 (067C, EA60, 00A4, 0022B640) 0022B718 610AF4FC (, 0022BE78, 0022BDF8, 610842B2) 0022B808 610ACFBB (, 0010, , 0044B400) 0022B868 610AD49B (0022B880, , 0094, 0022B8C8) 0022B928 610AD652 (0F94, 0006, 0022B958, 00552D10) 0022B938 610AA8B8 (, 00A9, 0022B958, 00AB2000) 0022B958 00552D10 (00AA16D8, 015316F8, 0840, ) 0022B998 00553788 (FFFDE000, 00A4ACF0, 0022BBA8, 0045C1B1) 0022B9F8 00551F31 (F7E8, 0037, 611BAA48, 61067AEC) 0022BA08 004F3E71 (F7E8, 002E, 0022BA68, 00452245) End of stack trace (more stack frames may be present) - After this, with the snapshot installed, I have tried to build a new checkout of Emacs-cvs, but it fails in linking: -- gcc40 -Wl,--enable-auto-import -Wl,--enable-auto-image-base -L/usr/X11R6/lib -o temacs ecrt0.o dispnew.o frame.o scroll.o xdisp.o xmenu.o window.o charset.o coding.o category.o ccl.o cm.o term.o xfaces.o xterm.o xfns.o xselect.o xrdb.o fontset.o xsmfns.o fringe.o image.o emacs.o keyboard.o macros.o keymap.o sysdep.o buffer.o filelock.o insdel.o marker.o minibuf.o fileio.o dired.o filemode.o cmds.o casetab.o casefiddle.o indent.o search.o regex.o undo.o alloc.o data.o doc.o editfns.o callint.o eval.o floatfns.o fns.o print.o lread.o abbrev.o syntax.o unexcw.o bytecode.o process.o callproc.o region-cache.o sound.o atimer.o doprnt.o strftime.o intervals.o textprop.o composite.o md5.o sheap.o terminfo.o gmalloc.o ralloc.o lastfile.o vm-limit.o widget.o mktime.o getloadavg.o ../lwlib/liblw.a -L/usr/X11R6/lib -lXaw3d -lXmu -lXt -lSM -lICE -lXext -ltiff -ljpeg -lpng -lz -lm -lungif -lXpm -lX11 -lcurses -lg `gcc40 -print-libgcc-file-name` -lm -lc `gcc40 -print-libgcc-file-name` /usr/bin/../lib/libg.a(lib_a-fwrite.o):(.text+0x49): undefined reference to `___cygwin_lock_lock' ... MANY "undefined reference to `___cygwin_lock_unlock'" /usr/bin/../lib/libg.a(lib_a-vfscanf.o):(.text+0x46a): undefined reference to `___cygwin_lock_unlock' collect2: ld returned 1 exit status make[2]: *** [temacs.exe] Error 1 make[2]: Leaving directory `/tmp/emacs/.build/src' make[1]: *** [bootstrap-build] Error 2 make[1]: Leaving directory `/tmp/emacs/.build' make: *** [bootstrap] Error 2 -- I have flagged the above problems because, perhaps, they hide problems in the snapshot that you can prove. I have XP-SP2, with a full, updated, Cygwin installation. Cheers, Angelo. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: IPX headers
Hmm, bummer... Well, after a bit of fiddling i got it to link with winsock even when compiling with cygwin. Not exactly what i wanted..., but heh, it works... Simon On 2/14/07, Corinna Vinschen <[EMAIL PROTECTED]> wrote: On Feb 14 20:43, Simon Sasburg wrote: > Ok so i'm trying to port a C winsock ipx application of mine to cygwin. > > problem is i can't find the needed IPX constants (or headers that contain > them). > > with winsock this works: >SOCKET ipx_sock = socket(AF_IPX, SOCK_DGRAM, NSPROTO_IPX); > when including >#include >#include > > now in cygwin it can't find the AF_IPX and NSPROTO_IPX constants (i > typedeffed SOCKET to int already) [...] > from looking around google i found that these constants might be found > in these headers on a 'real' unix system : >#include >#include >#include > > but when compiling with cygwin it can't find any of these headers. > > Where might the needed headers/constants be found on a cygwin system? > do i need to install any special packages for this? These headers don't exists. Cygwin doesn't support IPX, sorry. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] EOL for Windows 95/86/Me
Brian Ford wrote: On Wed, 14 Feb 2007, Matthew Woehlke wrote: Ok, but then, is the problem that the auth dll *is* cygwin1.dll, or else why wouldn't the reboot only be needed when you update the auth dll? (Does the auth dll need cygwin1.dll or would it be possible to make it only the other way around? Maybe the auth dll can have a hook to allow "stopping" and "starting" it so it can let go of cygwin1.dll and allow an update?) ...is there a link somewhere with general information on "Authentication DLL's"? To save Corinna some typing, it would help if you'd review the following thread: http://cygwin.com/ml/cygwin-developers/2006-11/msg0.html Thanks for pointing that out. So, to make sure I understand, if I upgrade from e.g. cygwin-1.7.1-1 to cygwin-1.7.1-4, I do *not* need to reboot (but from e.g. 1.7.1-1 to 1.7.2-1 I do)? Also, what enforces that (and more to the point, is it something a user might choose to circumvent)? -- Matthew -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] EOL for Windows 95/86/Me
On Wed, 14 Feb 2007, Matthew Woehlke wrote: > Ok, but then, is the problem that the auth dll *is* cygwin1.dll, or else > why wouldn't the reboot only be needed when you update the auth dll? > (Does the auth dll need cygwin1.dll or would it be possible to make it > only the other way around? Maybe the auth dll can have a hook to allow > "stopping" and "starting" it so it can let go of cygwin1.dll and allow > an update?) > > ...is there a link somewhere with general information on "Authentication > DLL's"? To save Corinna some typing, it would help if you'd review the following thread: http://cygwin.com/ml/cygwin-developers/2006-11/msg0.html -- Brian Ford Lead Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International the best safety device in any aircraft is a well-trained crew... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: syntax error near unexpected token `{
petermosca wrote:
I am attempting to create a bash script with a function definition. When I
execute the script with the function, I get:
'my_bash_script: line 3: syntax error near unexpected token `{".
'my_bash_script: line 3: ` {
If I type the function in the command line, it works fine.
Judging from your other mail, the answers are:
1. d2u
2. Don't use a broken editor
3. RTFRA and STFLA first.
--
Matthew
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] EOL for Windows 95/86/Me
Corinna Vinschen wrote: On Feb 14 13:11, Matthew Woehlke wrote: Corinna Vinschen wrote: [snip] And in the long run you will have to reboot your machine each time you install a new Cygwin release when using this feature. That's a fairly major bummer. Is that because this is something that depends on cygwin.dll and can't be unloaded, or...? Authentication DLLs can't be replaced without reboot in Windows for security reasons. Ok, but then, is the problem that the auth dll *is* cygwin1.dll, or else why wouldn't the reboot only be needed when you update the auth dll? (Does the auth dll need cygwin1.dll or would it be possible to make it only the other way around? Maybe the auth dll can have a hook to allow "stopping" and "starting" it so it can let go of cygwin1.dll and allow an update?) ...is there a link somewhere with general information on "Authentication DLL's"? -- Matthew -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ls command not outputting file names.
Ken Shaffer wrote: >>> Any other ideas? Anyone? > > Perhaps your filenames have special characters in them which do funny > things to your terminal. > > Try "ls -ad .* * | cat -v". Doesn't show anything unusual. > > Are the serial numbers on the physical drives unique? There's only one physical drive. All of the network mapped drives have the same serial # but they all map to the same server too, just different shares. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ls command not outputting file names.
Frodak Baksik wrote: > On 2/14/07, Chuck <[EMAIL PROTECTED]> wrote: >> > > What is actually in your home folder? > Also how did you create this trace? It appears to be truncated. Or > at least ls never got past the point where it reads the contents of > the directory. You'll notice that it never finished reading the > directory and perform a closedir and then start to print to stdout. > > --Frodak > Here's what it looks like when the ls finally works. It's just a few files, a few directories, and one or two symlinks. ./ ../ .ICEauthority* .XSM-Default* .Xdefaults* .addressbook* .addressbook.lu* .aspell.en.prepl* .aspell.en.pwd* .aspell.en.pws* .bash_history .fonts.cache-1 .gnupg@ .keychain/ .ncftp/ .nedit/ .netrc .pdksh_history* .profile* .rnd* .sh_history .ssh/ .tin/ .unison/ Download@ MyDocuments@ ProgramFiles@ afiedt.buf* bin/ change_passwords/ cleanup_rman/ cygcheck.out etc/ fix_Export_DB/ fix_Startup_DB/ getpw/ mail/ scripts/ strace.out* sync_files.sh* -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: IPX headers
On Feb 14 20:43, Simon Sasburg wrote: > Ok so i'm trying to port a C winsock ipx application of mine to cygwin. > > problem is i can't find the needed IPX constants (or headers that contain > them). > > with winsock this works: >SOCKET ipx_sock = socket(AF_IPX, SOCK_DGRAM, NSPROTO_IPX); > when including >#include >#include > > now in cygwin it can't find the AF_IPX and NSPROTO_IPX constants (i > typedeffed SOCKET to int already) [...] > from looking around google i found that these constants might be found > in these headers on a 'real' unix system : >#include >#include >#include > > but when compiling with cygwin it can't find any of these headers. > > Where might the needed headers/constants be found on a cygwin system? > do i need to install any special packages for this? These headers don't exists. Cygwin doesn't support IPX, sorry. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] EOL for Windows 95/86/Me
On Feb 14 13:11, Matthew Woehlke wrote: > Corinna Vinschen wrote: > >On Feb 14 10:22, Matthew Woehlke wrote: > >>Corinna Vinschen wrote: > >>>Exciting new stuff so far (IMHO): > >>>[snip] > >>>- New setuid method which allows to logon without password and being > >>> recognized correctly also by native Windows applications > >>Does this mean ssh might *finally* work right with password-less login? > >>:-) > > > >[snip] And in the long run you will have to reboot > >your machine each time you install a new Cygwin release when using this > >feature. > > That's a fairly major bummer. Is that because this is something that > depends on cygwin.dll and can't be unloaded, or...? Authentication DLLs can't be replaced without reboot in Windows for security reasons. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: shell commands won't run from within a shell script bash version 3.2.9-11
Please don't put "ANNOUNCEMENT" on messages that are not actually announcements. On Wed, Feb 14, 2007 at 11:27:56AM -0800, petermosca wrote: >I get a slightly different result: > >: command not foundnv > >It's as if the "e" in "env" is gobbled up somehow. If you scan the cygwin-announce mailing list archives for recent bash announcements you probably will see the reason for this behavior and how to correct it. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Unable to run even simple batch scripts any more
On Tue, 13 Feb 2007 00:56:24 Eric Backus wrote:
>
> Obviously, the horse is still alive and attempting to limp along. I predict
> it'll stay alive for quite some time longer.
>
[snip]
>
> * Workaround inserting "set -o igncr" is impractical when there are lots of
> scripts.
[snip]
Among my many scripts, there are some with DOS (i.e. CR LF) ending
that I prefer to leave as is (mostly to be able to edit them with
notpad).
I wrote a little script that can fix bash scripts with CRs by adding
the required "set -o igncr" line.
Notes:
1. You can, of course, replace the `awk' with a simple `d2u' if
you don't need the CRs at all.
2. Change the `grep' arguments (mostly the "-r" and the files list)
to suit your needs.
3. This script will fail on a file with ":" in its name (which can
occur only on manged mounts, because of the OS limitations)
Ehud.
cut here
#! /bin/bash -ex
chk_it ()
{
while read HEAD
do
echo "Checking $HEAD" # show some progress
case "$HEAD" in
*":1:#"*"^M" ) # ONLY (ba)sh files with
CR ending
SNM=`echo "$HEAD" | cut "-d:" -f1` # extract script name
echo "Fixing $SNM "
cp -p "$SNM" "$SNM"-new # copy with permissions
awk '
BEGIN { IA = 0 }
$0 ~ /^[ ]*#/ { print $0 ; next }
{
if ( IA == 0 )
{
print "set -o igncr #\r" ;
IA = 1 ;
}
print $0 ;
}
' < "$SNM" > "$SNM"-new # add "set -o igncr"
after initial comments
mv "$SNM" "$SNM"-old# save old script
mv "$SNM"-new "$SNM"# rename new to current
esac
done
}
# --
grep -E -H -I -m 1 -n -U -r -e '^#![ ]*/bin/(ba)?sh' * \
| cat -v | chk_it # check & replace CR
scripts
# end of fix-cr.sh script
--
Ehud Karni Tel: +972-3-7966-561 /"\
Mivtach - Simon Fax: +972-3-7966-667 \ / ASCII Ribbon Campaign
Insurance agencies (USA) voice mail and X Against HTML Mail
http://www.mvs.co.il FAX: 1-815-5509341 / \
GnuPG: 98EA398D
IPX headers
Ok so i'm trying to port a C winsock ipx application of mine to cygwin. problem is i can't find the needed IPX constants (or headers that contain them). with winsock this works: SOCKET ipx_sock = socket(AF_IPX, SOCK_DGRAM, NSPROTO_IPX); when including #include #include now in cygwin it can't find the AF_IPX and NSPROTO_IPX constants (i typedeffed SOCKET to int already) this are the headers I included: (i dont include the winsock ones when compiling with cygwin) #include #include #include #include #include #include from looking around google i found that these constants might be found in these headers on a 'real' unix system : #include #include #include but when compiling with cygwin it can't find any of these headers. Where might the needed headers/constants be found on a cygwin system? do i need to install any special packages for this? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
syntax error near unexpected token `{
Please help if you can.
I am attempting to create a bash script with a function definition. When I
execute the script with the function, I get:
'my_bash_script: line 3: syntax error near unexpected token `{".
'my_bash_script: line 3: ` {
If I type the function in the command line, it works fine.
My function:
#!/bin/bash
function afunc
{
echo $0 $1 $2
}
afunc one two
--
View this message in context:
http://www.nabble.com/syntax-error-near-unexpected-token-%60%7B-tf3229216.html#a8971939
Sent from the Cygwin Users mailing list archive at Nabble.com.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] shell commands won't run from within a shell script bash version 3.2.9-11
I get a slightly different result: : command not foundnv It's as if the "e" in "env" is gobbled up somehow. Randy-37 wrote: > > When I start the cygwin window I can run commands such > as env and cd or anything else i have tried. however when > i try to run a shell script with commands inside it, none of > the commands within the script will execute properly. > > for instance > > test.sh contains 1 line > env > > when it executes the following message is produced: > > : command not found env > > I just did a scratch install today. > > > Thanks, > > Randy Rainwater > > > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > > -- View this message in context: http://www.nabble.com/shell-commands-won%27t-run-from-within-a-shell-script-bash-version-3.2.9-11-tf3221512.html#a8971714 Sent from the Cygwin Users mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] EOL for Windows 95/86/Me
Corinna Vinschen wrote: On Feb 14 10:22, Matthew Woehlke wrote: Corinna Vinschen wrote: Exciting new stuff so far (IMHO): [snip] - New setuid method which allows to logon without password and being recognized correctly also by native Windows applications Does this mean ssh might *finally* work right with password-less login? :-) [snip] And in the long run you will have to reboot your machine each time you install a new Cygwin release when using this feature. That's a fairly major bummer. Is that because this is something that depends on cygwin.dll and can't be unloaded, or...? -- Matthew -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ls command not outputting file names.
Any other ideas? Anyone? Perhaps your filenames have special characters in them which do funny things to your terminal. Try "ls -ad .* * | cat -v". Are the serial numbers on the physical drives unique? From a DOS window, enter "dir": Volume in drive C has no label. Volume Serial Number is F0EC-C392 pushd \\somecomputer\someshare dir Volume in drive Z has no label. Volume Serial Number is FC59-2888 popd Ken -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ls command not outputting file names.
On 2/14/07, Chuck <[EMAIL PROTECTED]> wrote: Chuck wrote: > Shankar Unni wrote: > >> Obviously something odd about that share. Chuck: can you tell if there's >> something unusual about the server that exports that share (as opposed >> to the other drives you have, like K: and G:)? >> >> > > Nothing unusual about that share. I can even reproduce the problem on a > local directory. > > Attached is another strace.out file, this time it was for a simple ls of my home directory which is on the local HD. ** Program name: C:\cygwin\bin\ls.exe (pid 1972, ppid 1) App version: 1005.23, api: 0.156 DLL version: 1005.24, api: 0.156 DLL build:2007-01-31 10:57 OS version: Windows NT-5.1 Heap size:402653184 Date/Time:2007-02-14 11:30:48 ** 72 944 [main] ls 1972 set_myself: myself->dwProcessId 1972 701014 [main] ls 1972 time: 1171470648 = time (0) 6091623 [main] ls 1972 environ_init: GetEnvironmentStrings returned 0x2452C0 - "ALLUSERSPROFILE=C:\Documents and Settings\All Users" 2531876 [main] ls 1972 environ_init: 0x670238: ALLUSERSPROFILE=C:\Documents and Settings\All Users 1091985 [main] ls 1972 environ_init: 0x670270: APPDATA=C:\Documents and Settings\CHamilto\Application Data 1022087 [main] ls 1972 environ_init: 0x6702B0: CLASSPATH=.;C:\Program Files\Java\jre1.5.0_09\lib\ext\QTJava.zip 2042291 [main] ls 1972 environ_init: 0x6702F8: COLUMNS=95 1052396 [main] ls 1972 environ_init: 0x670308: COMMONPROGRAMFILES=C:\Program Files\Common Files 1022498 [main] ls 1972 environ_init: 0x670340: COMPUTERNAME=CHAMILTON-DEL 1532651 [main] ls 1972 environ_init: 0x670360: COMSPEC=C:\WINDOWS\system32\cmd.exe 1042755 [main] ls 1972 environ_init: 0x670388: CVSROOT=c:\program files\PuTTY 1172872 [main] ls 1972 environ_init: 0x6703B0: CVS_RSH=/bin/ssh 3193191 [main] ls 1972 environ_init: 0x6703C8: CYGWIN_ROOT=\cygwin 1063297 [main] ls 1972 environ_init: 0x6703E0: DISPLAY=127.0.0.1:0.0 1013398 [main] ls 1972 environ_init: 0x670400: FP_NO_HOST_CHECK=NO 2543652 [main] ls 1972 getwinenv: can't set native for HOME= since no environ yet 1113763 [main] ls 1972 mount_info::conv_to_posix_path: conv_to_posix_path (C:\cygwin\home\CHamilto, no-keep-rel, no-add-slash) 973860 [main] ls 1972 normalize_win32_path: C:\cygwin\home\CHamilto = normalize_win32_path (C:\cygwin\home\CHamilto) 743934 [main] ls 1972 mount_info::conv_to_posix_path: /home/CHamilto = conv_to_posix_path (C:\cygwin\home\CHamilto) 3594293 [main] ls 1972 win_env::add_cache: posix /home/CHamilto 664359 [main] ls 1972 win_env::add_cache: native HOME=C:\cygwin\home\CHamilto 634422 [main] ls 1972 posify: env var converted to HOME=/home/CHamilto 1024524 [main] ls 1972 environ_init: 0x670440: HOME=/home/CHamilto 1034627 [main] ls 1972 environ_init: 0x670418: HOMEDRIVE=C: 1014728 [main] ls 1972 environ_init: 0x670590: HOMEPATH=\Documents and Settings\CHamilto 2304958 [main] ls 1972 environ_init: 0x6705C0: INFOPATH=/usr/local/info:/usr/share/info:/usr/info: 1125070 [main] ls 1972 environ_init: 0x6705F8: LDMS_LOCAL_DIR=C:\Program Files\LANDesk\LDClient\Data 1035173 [main] ls 1972 environ_init: 0x670430: LINES=30 2385411 [main] ls 1972 environ_init: 0x670638: LOGNAME=CHamilto 1095520 [main] ls 1972 environ_init: 0x670650: LOGONSERVER=\\SAMGDEN02 1025622 [main] ls 1972 environ_init: 0x670670: MAKE_MODE=unix 1025724 [main] ls 1972 environ_init: 0x670688: MANPATH=/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man 1305854 [main] ls 1972 environ_init: 0x6706D0: NLS_DATE_FORMAT=DD-MON-YY hh24:mi:ss 1035957 [main] ls 1972 environ_init: 0x670700: NUMBER_OF_PROCESSORS=1 3116268 [main] ls 1972 environ_init: 0x670720: ORACLE_BASE=c:/oracle 1126380 [main] ls 1972 environ_init: 0x670740: ORACLE_HOME=c:/oracle/ora92 1016481 [main] ls 1972 environ_init: 0x670760: OS=Windows_NT 1066587 [main] ls 1972 getwinenv: can't set native for PATH= since no environ yet 686655 [main] ls 1972 normalize_posix_path: src . 746729 [main] ls 1972 mount_info::conv_to_posix_path: conv_to_posix_path (C:\cygwin\home\CHamilto, no-keep-rel, no-add-slash) 896818 [main] ls 1972 normalize_win32_path: C:\cygwin\home\CHamilto = normalize_win32_path (C:\cygwin\home\CHamilto) 666884 [main] ls 1972 mount_info::conv_to_posix_path: /home/CHamilto = conv_to_posix_path (C:\cygwin\home\CHamilto) 1307014 [main] ls 1972 cwdstuff::get: posix /home/CHamilto 2707284 [main] ls 1972 cwdstuff::get: (/home/CHamilto) = cwdstuff::get (0x22C890, 260, 1, 0), errno 0 757359 [main] ls 1972 normalize_posix_path: /home/CHamilto/ = normalize_posix_path (.) 657424 [main] ls 1972 mount_info::conv_to_win32_path: conv_to_win32_path (/home/CHamilto) 72
Setup package list duplication and crash
For a while I've been downloading from http://mirrors.dotsrc.org. I switched a few days ago when it started acting strangely. Several packages were displayed as Not Installed--bashdb3, gcc-gm2, libglade, libltdl6, and libploticus. When I clicked on "Skip" to try to install one of them, Setup crashed. So I switched back to http://mirror.mcs.anl.gov/, which didn't display that problem. anl.gov hasn't had any updates in a few days, so I thought I'd check back to dotsrc.org. I saw the exact same behaviour. However, now, if I go to dotsrc.org, to the package chooser, back to the mirrors list, select another mirror (it doesn't seem to matter which one), and back to the package chooser, there are multiple copies of each of the Not Installed packages listed above.Going back and forth, another copy is added each time I return to the package chooser. This only seems to happen if I go to dotsrc.org first. On the other mirrors I tried (which is only calvin.edu as well as the anl.gov), I only see two Not Installed packages; those always show up and are never duplicated. I'm willing to believe that dotsrc.org has some sort of problem, but setup presumably shouldn't be duplicated packages like that. Actually, I just tried it again, and it didn't happen the first time I went into the package chooser from dotsrc.org, but if I switched to "Not Installed" view, back to mirrors, then back to the package chooser, the spurious packages showed up. I am using Setup version 2.510.2.2. I'm not enclosing cygcheck output because I'm not sure it would be relevant. The setup.ini file in the dotsrc.org folder is no different from that in the calvin.edu folder. setup.log.full and setup.log don't seem to have been modified by the time the crash occurs, so no information there. Any other information I can provide? -- --Alfvaen (Web page: http://www.telusplanet.net/public/alfvaen/ ) Current Album--Rush:Counterparts Current Book--Glen Cook:Ceremony Casting bread upon swine -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] EOL for Windows 95/86/Me
On Feb 14 10:22, Matthew Woehlke wrote: > Corinna Vinschen wrote: > >Exciting new stuff so far (IMHO): > >[snip] > >- New setuid method which allows to logon without password and being > > recognized correctly also by native Windows applications > > Does this mean ssh might *finally* work right with password-less login? :-) You have to install an authentication DLL and change a registry key, but otherwise, yes. There's a installer script called /bin/cyglsa-config which does that for you. And in the long run you will have to reboot your machine each time you install a new Cygwin release when using this feature. Nothing's without a price ;) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ls command not outputting file names.
Chuck wrote: > Shankar Unni wrote: > >> Obviously something odd about that share. Chuck: can you tell if there's >> something unusual about the server that exports that share (as opposed >> to the other drives you have, like K: and G:)? >> >> > > Nothing unusual about that share. I can even reproduce the problem on a > local directory. > > Attached is another strace.out file, this time it was for a simple ls of my home directory which is on the local HD. ** Program name: C:\cygwin\bin\ls.exe (pid 1972, ppid 1) App version: 1005.23, api: 0.156 DLL version: 1005.24, api: 0.156 DLL build:2007-01-31 10:57 OS version: Windows NT-5.1 Heap size:402653184 Date/Time:2007-02-14 11:30:48 ** 72 944 [main] ls 1972 set_myself: myself->dwProcessId 1972 701014 [main] ls 1972 time: 1171470648 = time (0) 6091623 [main] ls 1972 environ_init: GetEnvironmentStrings returned 0x2452C0 - "ALLUSERSPROFILE=C:\Documents and Settings\All Users" 2531876 [main] ls 1972 environ_init: 0x670238: ALLUSERSPROFILE=C:\Documents and Settings\All Users 1091985 [main] ls 1972 environ_init: 0x670270: APPDATA=C:\Documents and Settings\CHamilto\Application Data 1022087 [main] ls 1972 environ_init: 0x6702B0: CLASSPATH=.;C:\Program Files\Java\jre1.5.0_09\lib\ext\QTJava.zip 2042291 [main] ls 1972 environ_init: 0x6702F8: COLUMNS=95 1052396 [main] ls 1972 environ_init: 0x670308: COMMONPROGRAMFILES=C:\Program Files\Common Files 1022498 [main] ls 1972 environ_init: 0x670340: COMPUTERNAME=CHAMILTON-DEL 1532651 [main] ls 1972 environ_init: 0x670360: COMSPEC=C:\WINDOWS\system32\cmd.exe 1042755 [main] ls 1972 environ_init: 0x670388: CVSROOT=c:\program files\PuTTY 1172872 [main] ls 1972 environ_init: 0x6703B0: CVS_RSH=/bin/ssh 3193191 [main] ls 1972 environ_init: 0x6703C8: CYGWIN_ROOT=\cygwin 1063297 [main] ls 1972 environ_init: 0x6703E0: DISPLAY=127.0.0.1:0.0 1013398 [main] ls 1972 environ_init: 0x670400: FP_NO_HOST_CHECK=NO 2543652 [main] ls 1972 getwinenv: can't set native for HOME= since no environ yet 1113763 [main] ls 1972 mount_info::conv_to_posix_path: conv_to_posix_path (C:\cygwin\home\CHamilto, no-keep-rel, no-add-slash) 973860 [main] ls 1972 normalize_win32_path: C:\cygwin\home\CHamilto = normalize_win32_path (C:\cygwin\home\CHamilto) 743934 [main] ls 1972 mount_info::conv_to_posix_path: /home/CHamilto = conv_to_posix_path (C:\cygwin\home\CHamilto) 3594293 [main] ls 1972 win_env::add_cache: posix /home/CHamilto 664359 [main] ls 1972 win_env::add_cache: native HOME=C:\cygwin\home\CHamilto 634422 [main] ls 1972 posify: env var converted to HOME=/home/CHamilto 1024524 [main] ls 1972 environ_init: 0x670440: HOME=/home/CHamilto 1034627 [main] ls 1972 environ_init: 0x670418: HOMEDRIVE=C: 1014728 [main] ls 1972 environ_init: 0x670590: HOMEPATH=\Documents and Settings\CHamilto 2304958 [main] ls 1972 environ_init: 0x6705C0: INFOPATH=/usr/local/info:/usr/share/info:/usr/info: 1125070 [main] ls 1972 environ_init: 0x6705F8: LDMS_LOCAL_DIR=C:\Program Files\LANDesk\LDClient\Data 1035173 [main] ls 1972 environ_init: 0x670430: LINES=30 2385411 [main] ls 1972 environ_init: 0x670638: LOGNAME=CHamilto 1095520 [main] ls 1972 environ_init: 0x670650: LOGONSERVER=\\SAMGDEN02 1025622 [main] ls 1972 environ_init: 0x670670: MAKE_MODE=unix 1025724 [main] ls 1972 environ_init: 0x670688: MANPATH=/usr/local/man:/usr/share/man:/usr/man::/usr/ssl/man 1305854 [main] ls 1972 environ_init: 0x6706D0: NLS_DATE_FORMAT=DD-MON-YY hh24:mi:ss 1035957 [main] ls 1972 environ_init: 0x670700: NUMBER_OF_PROCESSORS=1 3116268 [main] ls 1972 environ_init: 0x670720: ORACLE_BASE=c:/oracle 1126380 [main] ls 1972 environ_init: 0x670740: ORACLE_HOME=c:/oracle/ora92 1016481 [main] ls 1972 environ_init: 0x670760: OS=Windows_NT 1066587 [main] ls 1972 getwinenv: can't set native for PATH= since no environ yet 686655 [main] ls 1972 normalize_posix_path: src . 746729 [main] ls 1972 mount_info::conv_to_posix_path: conv_to_posix_path (C:\cygwin\home\CHamilto, no-keep-rel, no-add-slash) 896818 [main] ls 1972 normalize_win32_path: C:\cygwin\home\CHamilto = normalize_win32_path (C:\cygwin\home\CHamilto) 666884 [main] ls 1972 mount_info::conv_to_posix_path: /home/CHamilto = conv_to_posix_path (C:\cygwin\home\CHamilto) 1307014 [main] ls 1972 cwdstuff::get: posix /home/CHamilto 2707284 [main] ls 1972 cwdstuff::get: (/home/CHamilto) = cwdstuff::get (0x22C890, 260, 1, 0), errno 0 757359 [main] ls 1972 normalize_posix_path: /home/CHamilto/ = normalize_posix_path (.) 657424 [main] ls 1972 mount_info::conv_to_win32_path: conv_to_win32_path (/home/CHamilto) 727496 [main] ls 1972 set_flags: flags: binary
Re: [ANNOUNCEMENT] EOL for Windows 95/86/Me
Corinna Vinschen wrote: Exciting new stuff so far (IMHO): [snip] - New setuid method which allows to logon without password and being recognized correctly also by native Windows applications Does this mean ssh might *finally* work right with password-less login? :-) -- Matthew -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ls command not outputting file names.
Shankar Unni wrote: > > Obviously something odd about that share. Chuck: can you tell if there's > something unusual about the server that exports that share (as opposed > to the other drives you have, like K: and G:)? > > Nothing unusual about that share. I can even reproduce the problem on a local directory. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: ls not showing anything - sometimes
Shankar Unni wrote: > Chuck wrote: > >> Any other ideas? Anyone? > > Have you followed the problem reporting guidelines at > http://cygwin.com/problems.html ? > > Also, if you are familiar with "strace", you may want to run "strace > /bin/ls" in your /cygdrive directory, and see if anything obvious (to > you) pops up. > > Else, you could try posting a followup (to your full problem report as > above) with the strace output. > > yes. I did all that under a new thread "ls command not outputting file names" -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: tar --exclude not working
On Wed, Feb 14, 2007 at 02:52:53PM +, Eric Blake wrote: >> I'm using tar (GNU tar) 1.16.1 and have an archive with the following >> entries. >> Files/report1.html >> Files/report2.html >> Files/report3.html >> Files/report4.html >> D:/Bkp/sol/ >> D:/Bkp/sol/test1.pl >> D:/Bkp/sol/test2.pl >> D:/Bkp/sol/test3.pl >> >> Whenever, I try to exclude files starting with "D:/" its not working >> as expected. > >Tar has special treatment of command-line arguments with colons, >trying to treat it as a path to a remote machine. Tar archives created >with drive letters are inherently non-portable, and under cygwin, you >should create tar archives using a POSIX name such as /cygdrive/d >rather than d:/ (or whatever you mount your cygdrive as). > >> >> Is this a bug? Can it be worked atound? > >I have done nothing in this regards that is cygwin-specific. If it is >a bug, then it is an upstream one. But more likely, it is merely a >matter of your using drive letters when tar tries to interpret them >as remote machine names. Maybe this should be a FAQ. It sure comes up enough. Do we have anyone whose willing to update the FAQ with this info? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: tar --exclude not working
> I'm using tar (GNU tar) 1.16.1 and have an archive with the following entries. > Files/report1.html > Files/report2.html > Files/report3.html > Files/report4.html > D:/Bkp/sol/ > D:/Bkp/sol/test1.pl > D:/Bkp/sol/test2.pl > D:/Bkp/sol/test3.pl > > Whenever, I try to exclude files starting with "D:/" its not working > as expected. Tar has special treatment of command-line arguments with colons, trying to treat it as a path to a remote machine. Tar archives created with drive letters are inherently non-portable, and under cygwin, you should create tar archives using a POSIX name such as /cygdrive/d rather than d:/ (or whatever you mount your cygdrive as). > > Is this a bug? Can it be worked atound? I have done nothing in this regards that is cygwin-specific. If it is a bug, then it is an upstream one. But more likely, it is merely a matter of your using drive letters when tar tries to interpret them as remote machine names. -- Eric Blake volunteer cygwin tar maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Re: Using a DLL built with cygwin in VC++
>First of all, have you read the Cygwin FAQ (specifically, *all* the >questions in the Programming FAQ? Read the caveats about linking Cygwin >DLLs >into VC++ programs. Specifically, Q 16. >After you have understood what you're actually trying to do, you may want >to >try to follow the instructions in Q 16 to generate your .lib and .def >files, >and then make sure to put in the correct crt hooks, etc. I've read all of the Cygwin's programming faq, I've tried the method they described in "How can I build a relocatable dll?", first of all, there's no __imp_reent_data symbol in Cygwin dll, but there's reent_data, I used it instead, I've successfuly compiled and linked, but when I run my app I get an access violation writing at address 0x0, VS2005's debugger says that it's cygwin.dll is trying to do so. Then, I tried to remove all Cygwin API calls from my gcc compiled DLL and recompiled my app, everything worked fine. This exception occurs only if there're Cygwin API calls in DLL. So, what shall I do ? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] EOL for Windows 95/86/Me
On Feb 14 03:17, Yitzchak Scott-Thoennes wrote: > Corinna Vinschen wrote: > > On Feb 13 21:02, Yaakov (Cygwin Ports) wrote: > >> And approximately what is the timeframe to 1.7.0; weeks, months, next > >> year? Is HEAD stable enough for those not working on cygwin1.dll to be > >> testing? > > > > Months. It's stable enough now but it's constantly changing. Stability > > in snapshots is not guaranteed. > > > > Exciting new stuff so far (IMHO): > [snip] > > - More POSIXy unlink/rmdir behaviour > > Can you expand on that? What changes? You can remove a file or directory which has an open file descriptor. You can remove a directory which is the current working directory of a Cygwin process. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: tar --exclude not working
tar tf test.tar --anchored --exclude="D:/" temp$ tar tf tartest.tar -P c:/temp/file1 file2 temp$ tar tf tartest.tar -P --anchored --exclude='/temp' file2 So, if you really want to exclude your D:/Bkp files, you could enter: tar tf test.tar --anchored --exclude='/Bkp' The -P option used on my test tar file forced absolute paths and I didn't get the message "tar: Removing leading `c:/' from member names". In fact, this message clued me to how I might exclude the desired file. Even though it says it removed "c:/", it appears it only removed "c:" since I had to provide the leading / to exclude the file. mount points may also have something to do with the behaviour: c:\temp on /tmp type system (binmode) c: on /c type system (binmode) But, in any event, I'd also agree there's something up with --exclude. Ken -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Win2k + Cygwin + Rsync + OpenSSH = hang
Hello all- I'm trying to pull data from a Windows 2000 Server to a Debian Linux server using rsync over ssh. If I initiate the transfer from Linux it hangs when transferring data, though it works when I push it from the Windows server. This appears to be a known issue. In August 2006, Darryl Miles wrote to this list "I am actively working on a solution, but at current work rate it maybe a few weeks to a month before any preliminary patch will be posted here." Does anyone know of a fix for this problem? I'm using Cygwin 1.5.24, Rsync 2.6.9, and OpenSSH 4.5p1. Thanks -Justin -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] EOL for Windows 95/86/Me
Corinna Vinschen wrote: > On Feb 13 21:02, Yaakov (Cygwin Ports) wrote: >> And approximately what is the timeframe to 1.7.0; weeks, months, next >> year? Is HEAD stable enough for those not working on cygwin1.dll to be >> testing? > > Months. It's stable enough now but it's constantly changing. Stability > in snapshots is not guaranteed. > > Exciting new stuff so far (IMHO): [snip] > - More POSIXy unlink/rmdir behaviour Can you expand on that? What changes? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] EOL for Windows 95/86/Me
Corinna Vinschen skrev: On Feb 13 21:02, Yaakov (Cygwin Ports) wrote: Christopher Faylor wrote: So, barring any catastrophic problems with the current released version of the Cygwin DLL, the last Cygwin version with support for non-Windows-NT class versions of Windows will be 1.5.24-2. And approximately what is the timeframe to 1.7.0; weeks, months, next year? Is HEAD stable enough for those not working on cygwin1.dll to be testing? Months. It's stable enough now but it's constantly changing. Stability in snapshots is not guaranteed. Exciting new stuff so far (IMHO): - New blocking socket code - getaddrinfo/getnameinfo/freeaddrinfo - IPv6 (>= XP, 2K w/ IPv6 Helper Lib) - POSIX advisory functions (posix_fallocate, posix_fadvise, posix_memalign, posix_madvise) - Treat directory reparse points and native symlinks as symlinks - Up to 128 SCSI disk block devices - New setuid method which allows to logon without password and being recognized correctly also by native Windows applications - More POSIXy unlink/rmdir behaviour - Resolver functions from minires now part of Cygwin - New struct ifconf, plus /proc/net/if_inet6 using unambiguos interface GUID name of Windows (>= XP SP1) - Multicast support (>= XP SP1) - POSIX shared memory objects - POSIX message queues (coming today) More to come. Corinna Corinna, I love you! I'm so excited about these changes! - Eric -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] LS_COLORS has no effect
On Feb 14 00:50, KClaisse wrote: > Thorsten Kampe wrote: > > * KClaisse (Tue, 13 Feb 2007 04:43:22 -0800 (PST)) > >> I have tried just about everything to get the LS_COLORS to work but they > >> just > >> don't seem to have any effect. I'm using $ echo $LS_COLORS ex=0;31:ln=0;32:di=0;34 $ alias ls ls --color=tty and it works fine for me. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] EOL for Windows 95/86/Me
On Feb 13 21:02, Yaakov (Cygwin Ports) wrote: > Christopher Faylor wrote: > > So, barring any catastrophic problems with the current released version > > of the Cygwin DLL, the last Cygwin version with support for > > non-Windows-NT class versions of Windows will be 1.5.24-2. > > And approximately what is the timeframe to 1.7.0; weeks, months, next > year? Is HEAD stable enough for those not working on cygwin1.dll to be > testing? Months. It's stable enough now but it's constantly changing. Stability in snapshots is not guaranteed. Exciting new stuff so far (IMHO): - New blocking socket code - getaddrinfo/getnameinfo/freeaddrinfo - IPv6 (>= XP, 2K w/ IPv6 Helper Lib) - POSIX advisory functions (posix_fallocate, posix_fadvise, posix_memalign, posix_madvise) - Treat directory reparse points and native symlinks as symlinks - Up to 128 SCSI disk block devices - New setuid method which allows to logon without password and being recognized correctly also by native Windows applications - More POSIXy unlink/rmdir behaviour - Resolver functions from minires now part of Cygwin - New struct ifconf, plus /proc/net/if_inet6 using unambiguos interface GUID name of Windows (>= XP SP1) - Multicast support (>= XP SP1) - POSIX shared memory objects - POSIX message queues (coming today) More to come. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] LS_COLORS has no effect
Thorsten Kampe wrote: > > * KClaisse (Tue, 13 Feb 2007 04:43:22 -0800 (PST)) >> >> I have tried just about everything to get the LS_COLORS to work but they >> just >> don't seem to have any effect. > > eval $(dircolors -b ~/.dir_colors) > > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://cygwin.com/docs.html > FAQ: http://cygwin.com/faq/ > > > That didn't either. I have something very similar in my .bashrc file too. It seems that LS isn't using the LS_COLORS variable. -- View this message in context: http://www.nabble.com/LS_COLORS-has-no-effect-tf3220407.html#a8960819 Sent from the Cygwin Users mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: LS_COLORS has no effect
* KClaisse (Tue, 13 Feb 2007 04:43:22 -0800 (PST)) > > I have tried just about everything to get the LS_COLORS to work but they just > don't seem to have any effect. eval $(dircolors -b ~/.dir_colors) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] Updated:lftp-3.5.9-1
* Thorsten Kampe (Tue, 13 Feb 2007 17:53:52 -) > > (2) lftp is fairly complex and I'm still learning it. For future bug > > reports I'll ask users to attach their .lftprc files and look first in the > > settings, of which there are about 200. > > Probably asking to start lftp with the .lftrc would even be wiser... Oops, of course I meant starting lftp \without\ the .lftprc... T. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
