Re: util-linux vs. coreutils
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Eric Blake wrote: > The next upstream release of coreutils will provide arch: > http://www.nabble.com/adding-%22arch%22-%28aka-uname--m%29-to-the-coreutils- > tf3871420.html > > But this is currently provided by util-linux, so there will need to be some > coordination between the two packages to make the handoff smooth. (Moving to cygwin-apps, as this is an issue between maintainers.) Thanks for the heads-up. util-linux is mine; what is the timeframe? Yaakov -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGZg07piWmPGlmQSMRCA96AJwL9lOBtsEYN0I5zwTRzGN5H81eTACfUQJk 394iqMlPgXlrr9GfsnSzh18= =mtSS -END PGP SIGNATURE- -- 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/
[ANNOUNCEMENT] New package: brltty 3.8
Version 3.8 of "brltty" has been uploaded. Access software for a blind person using a soft braille terminal. Brltty is a background process (daemon) providing access to the Windows Console for a blind person using a refreshable braille display. If you have questions or comments, please send them to the Cygwin mailing list at: cygwin@cygwin.com . *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/
util-linux vs. coreutils
The next upstream release of coreutils will provide arch: http://www.nabble.com/adding-%22arch%22-%28aka-uname--m%29-to-the-coreutils- tf3871420.html But this is currently provided by util-linux, so there will need to be some coordination between the two packages to make the handoff smooth. -- Eric Blake -- 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: directory listing differences
Joseph Michaud wrote: [EMAIL PROTECTED] /cygdrive/c/windows/system32 $ ls -al tsdiscon.exe tsecimp.exe ls: cannot access tsdiscon.exe: No such file or directory That's probably because the file is exclusively locked, and the "stat" performed by "ls" fails. See if you see the file if you pass in the "-f" option to ls: $ ls -f tsdiscon.exe tsecimp.exe If you can, then this is the issue. Looks like CMD.EXE is able to examine whatever it needs from such files, but stat() in the cygwin library cannot (uses different APIs). I see similar behavior in a file that PointSec drops in my C:\\ (PROT_INS.SYS). In fact, even "ls -f" is not able to get any info on that file! % cmd /c dir /AH c:\\prot_ins.sys Volume in drive C has no label. Volume Serial Number is A8B1-8402 Directory of c:\ 03/22/2007 11:03 AM 2,097,152 PROT_INS.SYS 1 File(s) 2,097,152 bytes 0 Dir(s) 4,296,351,744 bytes free % ls -ln c:\\prot_ins.sys ls: cannot access c:\prot_ins.sys: Input/Output error % ls -f c:\\prot_ins.sys ls: cannot access c:\prot_ins.sys: Input/Output error -- 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: Problem compiling cygwin-1.5.24-2
Olivier Langlois wrote: Hi, I kinda isolated the weird file access problem. The corruption seems to come from the setup.exe program as if I download manually cygwin-1.5.24-2-src.tar.bz2, unzip and untar it manually, the permissions for all files are ok. Greetings, Olivier Langlois http://www.streamtheworld.com "Corruption" isn't quite accurate. When you download source files, setup.exe puts them in /usr/src, which is a managed mount, to insure that Windows-incompatible file names can still be preserved. If you copy files from /usr/src outside of cygwin, then the filenames will become mangled. If you use cygwin's cp to copy them, then there should be no problems unless some of the filenames are not legal Windows filenames. That's probably what was happening here. -Lewis -- 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: Problem compiling cygwin-1.5.24-2
Hi, I kinda isolated the weird file access problem. The corruption seems to come from the setup.exe program as if I download manually cygwin-1.5.24-2-src.tar.bz2, unzip and untar it manually, the permissions for all files are ok. Greetings, Olivier Langlois http://www.streamtheworld.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/
Problem compiling cygwin-1.5.24-2
When I execute ./configure I get this error: configure: creating ./config.status config.status: error: cannot find input file: Makefile.in There seem to be some problems with the permissions since the file Makefile.in is there but if I do ls -la, I have these errors: $ ls -la ls: cannot access ChangeLog: No such file or directory ls: cannot access COPYING: No such file or directory ls: cannot access COPYING.LIB: No such file or directory ls: cannot access COPYING.LIBGLOSS: No such file or directory ls: cannot access COPYING.NEWLIB: No such file or directory ls: cannot access MAINTAINERS: No such file or directory ls: cannot access Makefile.def: No such file or directory ls: cannot access Makefile.in: No such file or directory ls: cannot access Makefile.tpl: No such file or directory ls: cannot access README: No such file or directory ls: cannot access README-maintainer-mode: No such file or directory total 1031 drwxrwx---+ 9 Administrator Users 0 Jun 5 15:59 . drwxrwx---+ 5 Administrator Users 0 Jun 5 15:28 .. ??? ? ? ? ?? COPYING ??? ? ? ? ?? COPYING.LIB ??? ? ? ? ?? COPYING.LIBGLOSS ??? ? ? ? ?? COPYING.NEWLIB ??? ? ? ? ?? ChangeLog ??? ? ? ? ?? MAINTAINERS -rw-r--r-- 1 Administrator None 0 Jun 5 15:14 Makefile ??? ? ? ? ?? Makefile.def ??? ? ? ? ?? Makefile.in Can someone help me? Thank you, Olivier Langlois http://www.streamtheworld.com cygcheck.out Description: Binary data -- 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/
directory listing differences
I noticed the following problem because c:\windows\system32\telnet.exe was one of the files affected... A directory listing shows different files if I compare the windows DIR command to the cygwin "ls". For example, I look in c:\windows\system32 for two files (tsdiscon.exe and tsecimp.exe) using both the windows DIR command in a CMD shell and "ls" in a bash shell. tsdiscon.exe is missing under cygwin. C:\WINDOWS\system32> C:\WINDOWS\system32>dir /q tsdiscon.exe tsecimp.exe Volume in drive C has no label. Volume Serial Number is 2857-9183 Directory of C:\WINDOWS\system32 02/18/2007 05:00 AM24,064 BUILTIN\Administrators tsdiscon.exe Directory of C:\WINDOWS\system32 02/18/2007 05:00 AM38,400 BUILTIN\Administrators tsecimp.exe 2 File(s) 62,464 bytes 0 Dir(s) 132,988,616,704 bytes free C:\WINDOWS\system32> C:\WINDOWS\system32> [EMAIL PROTECTED] /cygdrive/c/windows/system32 $ ls -al tsdiscon.exe tsecimp.exe ls: cannot access tsdiscon.exe: No such file or directory -rwxrwx--- 1 Administrators SYSTEM 26624 Feb 18 04:00 tsecimp.exe* $ The ACLs for the two files seem to be the same: C:\WINDOWS\system32>cacls tsdiscon.exe C:\WINDOWS\system32\tsdiscon.exe NT AUTHORITY\INTERACTIVE:R NT AUTHORITY\SERVICE:R NT AUTHORITY\BATCH:R BUILTIN\Administrators:F NT AUTHORITY\SYSTEM:F BUILTIN\Administrators:F C:\WINDOWS\system32>cacls tsecimp.exe C:\WINDOWS\system32\tsecimp.exe NT AUTHORITY\INTERACTIVE:R NT AUTHORITY\SERVICE:R NT AUTHORITY\BATCH:R BUILTIN\Administrators:F NT AUTHORITY\SYSTEM:F BUILTIN\Administrators:F C:\WINDOWS\system32> And here is the id for administrator under cygwin: [EMAIL PROTECTED] /cygdrive/c/windows/system32 $ id uid=500(Administrator) gid=513(Domain Users) groups=0(root),513(Domain Users),544(Administrators),554(Pre-Windows 2000 Compatible Ac cess),545(Users),1002(TelnetClients),10545(mkgroup_l_d) Any ideas? Joe -- 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: running vim on cygwin
On Tue, 2007-06-05 at 07:27 -0700, Kamaraju Kusumanchi wrote: > Hi > > I installed vim 7.1 via cygwin on Windows XP machine. However, when I run > vim on the bash shell of cygwin, I am getting the following error. > > E558: Terminal entry not found in terminfo > 'cygwin' not known. Available builtin terminals are: > builtin_riscos > builtin_amiga > builtin_beos-ansi > builtin_ansi > builtin_pcansi > builtin_win32 > builtin_vt320 > builtin_vt52 > builtin_xterm > builtin_iris-ansi > builtin_debug > builtin_dumb > defaulting to 'ansi' > > I initially asked about this on the vim mailing list > http://tech.groups.yahoo.com/group/vim/message/80886 > > In that discussion, it was determined that my terminfo database is not > properly installed and readable. > > For example, if I do > bash-3.2$infocmp > infocmp: couldn't open terminfo file . > > However, I do not know how to solve the problem. The termcap 20050421-1, > terminfo 5.5_20061104-1 are already installed on this system via cygwin. > > All the software is installed via cygwin installer using the > http://mirrors.xmission.com mirror. I have neither installed any source > packages nor compiled any software on this system. All the packages that were > installed are binary. > > The output of > > cygcheck -s -v -r 2>&1 | tee cygcheck.out > > is attached in this email. Please let me know if any other info is needed. > > Any suggestion/ideas would be really appreciated. > > thanks > raju > Sorry, I thought that i'd replied to the vim mailing list request to run cygwin's setup.exe again and re-install the problem packages... -- 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/
running vim on cygwin
Hi I installed vim 7.1 via cygwin on Windows XP machine. However, when I run vim on the bash shell of cygwin, I am getting the following error. E558: Terminal entry not found in terminfo 'cygwin' not known. Available builtin terminals are: builtin_riscos builtin_amiga builtin_beos-ansi builtin_ansi builtin_pcansi builtin_win32 builtin_vt320 builtin_vt52 builtin_xterm builtin_iris-ansi builtin_debug builtin_dumb defaulting to 'ansi' I initially asked about this on the vim mailing list http://tech.groups.yahoo.com/group/vim/message/80886 In that discussion, it was determined that my terminfo database is not properly installed and readable. For example, if I do bash-3.2$infocmp infocmp: couldn't open terminfo file . However, I do not know how to solve the problem. The termcap 20050421-1, terminfo 5.5_20061104-1 are already installed on this system via cygwin. All the software is installed via cygwin installer using the http://mirrors.xmission.com mirror. I have neither installed any source packages nor compiled any software on this system. All the packages that were installed are binary. The output of cygcheck -s -v -r 2>&1 | tee cygcheck.out is attached in this email. Please let me know if any other info is needed. Any suggestion/ideas would be really appreciated. thanks raju -- Finally - A spam blocker that actually works. http://www.bluebottle.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/
