[ITP] since 0.5 -- Tail work-alike that saves and uses state information
Included in Debian stable: http://packages.debian.org/since Jari sdesc: Tail work-alike that saves and uses state information ldesc: Program remembers how much of a file you have viewed and displays only what's new when you next view that file. Ideal for viewing log files. It'll only show what's new in the file since the last time it was run. category: Utils requires: cygwin a) manual wget\ http://cygwin.cante.net/since/since-0.5-1-src.tar.bz2 \ http://cygwin.cante.net/since/since-0.5-1.tar.bz2 \ http://cygwin.cante.net/since/setup.hint b) automated gpg --keyserver wwwkeys.pgp.net --recv-keys 955A92D8 mkdir since ; cd since rm -f get.sh get.sh.sig wgethttp://cygwin.cante.net/since/get.sh \ http://cygwin.cante.net/since/get.sh.sig gpg --verify get.sh.sig get.sh sh get.sh cd /usr/src/cygwin-packages/since less /usr/src/cygwin-packages/since/get.sh tar -jtvf /usr/src/cygwin-packages/since/since-0.5-1.tar.bz2 -- Welcome to FOSS revolution: we fix and modify until it shines
[ITP] o3read 0.0.4 -- Standalone converter for OpenOffice.org documents
Included in Debian stable: http://packages.debian.org/o3read Jari sdesc: Standalone converter for OpenOffice.org documents ldesc: A collection of utilities that helps convertion of OpenOffice.org Writer and Calc documents to the one of the three output formats: o3read - displays a dump of the parse tree; o3totxt - creates plain text; o3tohtml - creates html code. category: Doc requires: cygwin a) manual wget\ http://cygwin.cante.net/o3read/o3read-0.0.4-1-src.tar.bz2 \ http://cygwin.cante.net/o3read/o3read-0.0.4-1.tar.bz2 \ http://cygwin.cante.net/o3read/setup.hint b) automated gpg --keyserver wwwkeys.pgp.net --recv-keys 955A92D8 mkdir o3read ; cd o3read rm -f get.sh get.sh.sig wgethttp://cygwin.cante.net/o3read/get.sh \ http://cygwin.cante.net/o3read/get.sh.sig gpg --verify get.sh.sig get.sh sh get.sh -- Welcome to FOSS revolution: we fix and modify until it shines
[ITP] rdtool 0.6.20 -- Ruby RD document formatter
Included in Debian stable: http://packages.debian.org/rdtool Jari sdesc: RD document formatter ldesc: RD is multipurpose documentation format created for documentating Ruby and output of Ruby world. You can embed RD into Ruby script. And RD have neat syntax which help you to read document in Ruby script. On the other hand, RD have a feature for class reference. category: Text requires: cygwin ruby a) manual wget\ http://cygwin.cante.net/rdtool/rdtool-0.6.20-1-src.tar.bz2 \ http://cygwin.cante.net/rdtool/rdtool-0.6.20-1.tar.bz2 \ http://cygwin.cante.net/rdtool/setup.hint b) automated gpg --keyserver wwwkeys.pgp.net --recv-keys 955A92D8 mkdir rdtool ; cd rdtool rm -f get.sh get.sh.sig wgethttp://cygwin.cante.net/rdtool/get.sh \ http://cygwin.cante.net/rdtool/get.sh.sig gpg --verify get.sh.sig get.sh sh get.sh -- Welcome to FOSS revolution: we fix and modify until it shines
[ITP] renattach 1.2.4 -- Filter to rename or delete dangerous e-mail attachments
Included in Debian stable: http://packages.debian.org/renattach Jari sdesc: Filter to rename or delete dangerous e-mail attachments ldesc: A fast and efficient UNIX stream filter that can rename or delete potentially dangerous e-mail attachments. It's a highly effective way of protecting end-users from harmful mail content (worms/viruses) by disabling or removing attachments that may be accidentally executed by users. The filter is invoked as a simple pipe for use in a wide variety of systems. The 'kill' feature (which eliminates entire messages) can also help sites deal with resource strains caused by modern virus floods. category: Mail requires: cygwin a) manual wget\ http://cygwin.cante.net/renattach/setup.hint \ http://cygwin.cante.net/renattach/renattach-1.2.4-1-src.tar.bz2 \ http://cygwin.cante.net/renattach/renattach-1.2.4-1.tar.bz2 \ b) automated gpg --keyserver wwwkeys.pgp.net --recv-keys 955A92D8 mkdir renattach ; cd renattach rm -f get.sh get.sh.sig wgethttp://cygwin.cante.net/renattach/get.sh \ http://cygwin.cante.net/renattach/get.sh.sig gpg --verify get.sh.sig get.sh sh get.sh -- Welcome to FOSS revolution: we fix and modify until it shines
Re: tar and lzma
Eric Blake wrote: Although in this case, automake could (and probably should) add lzma as a dependency, since automake is not in Base either. Users who want automake already committed to more than the default. I added that dependency in 1.10.1-1 -- Chuck
ITA: gnupg
Current cygwin package seems pretty outdated (Upstream: 1.4.8, currently in cygwin distribution: 1.4.5). 1.4.8 compiles from the upstream source without any modifications. (Please excuse and correct me if I have missed something.)
src/winsup/cygwin ChangeLog fhandler_disk_file.cc
CVSROOT:/cvs/src Module name:src Branch: cr-0x5f1 Changes by: [EMAIL PROTECTED] 2008-02-29 16:38:02 Modified files: winsup/cygwin : ChangeLog fhandler_disk_file.cc Log message: * fhandler_disk_file.cc (fhandler_disk_file::fchmod): Call close_fs instead of close to avoid calling close from wrong class when changing a file system based device node. (fhandler_disk_file::fchown): Ditto. (fhandler_disk_file::facl): Ditto. (fhandler_base::utimes_fs): Ditto. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srconly_with_tag=cr-0x5f1r1=1.3582.2.55r2=1.3582.2.56 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fhandler_disk_file.cc.diff?cvsroot=srconly_with_tag=cr-0x5f1r1=1.185.4.8r2=1.185.4.9
Re: chown with not existing user/group
Hi, Dave Korn dave.korn at artimi.com writes: Because it has to emulate unix perms by relating uid/gid to windows RIDs, which are owned, allocated and controlled by the system, and not under the arbitrary choice of the user, so the semantics wouldn't be the same even if we did create ACLs with unrecognised SIDs on them. Another question, why isn't possible to mount the partition with a special flag (like managed mode), where the permision are stored in a database instead of trying to map them on windows perms. This mode will do something like what does fakeroot on Linux. Matthieu -- 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: another minor cygcheck nit
On Feb 28 21:47, Linda Walsh wrote: cygcheck doesn't handle the max arg length as shown by xargs... I.e. - cygcheck -f /bin/* bash: /usr/bin/cygcheck: Argument list too long echo /bin/*|xargs cygcheck -f xargs: cygcheck: Argument list too long #Note: cygcheck /bin/[a-r]* # works (wc -wc = 1780 32365) cygcheck /bin/[a-s]* # fails (wc -wc = 1874 33917) # -- looks like a 2^15 boundary prob? xargs --show-limits Your environment variables take up 3867 bytes POSIX upper limit on argument length (this system): 1042661 POSIX smallest allowable upper limit on argument length (all systems): 4096 Maximum length of command we could actually use: 1038794 Size of command buffer we are actually using: 1042661 Guess cygcheck isn't a POSIX app? cygcheck is a native app. 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: chown with not existing user/group
On Feb 29 09:16, Matthieu CASTET wrote: Hi, Dave Korn dave.korn at artimi.com writes: Because it has to emulate unix perms by relating uid/gid to windows RIDs, which are owned, allocated and controlled by the system, and not under the arbitrary choice of the user, so the semantics wouldn't be the same even if we did create ACLs with unrecognised SIDs on them. Another question, why isn't possible to mount the partition with a special flag (like managed mode), where the permision are stored in a database instead of trying to map them on windows perms. Why do you want to fake security when yoi can get the real thing? 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: Terminal control
Pham D. Loc, le Thu 28 Feb 2008 18:22:09 -0800, a écrit : I have C/C++ programs which printed the following characters via printf (which looks like terminal control): ^[[?1;2c In the xterm terminfo, that is User String #8 aka user8 aka u8. Maybe that's something else, see the output of infocmp. Samuel -- 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: Serial port using USB adaptor
On Feb 29 12:43, hce wrote: Hi, I have a linux serial port problem compiled by Cygwin on window, it runs fine if it connects a 9-pin serial cable and the device name is /dev/ttyS0 (it does not work with com1, I have to translate it to /dev/ttyS0). The problem is when I run the program in a PC without a physical 9-pin serial port on hardware: (1) If there is no USB Serial adaptor connected, it still opens /dev/ttyS0 without any errors. Then, it sends data to that port, and timeout (does not work). (2) If I plug a USB-Serial adaptor and change the device name to /dev/ttyUSB0, it opens that port witout problem but cannot connect to the serial device. /dev/ttyUSB0 works?!? It's no device name recognized by Cygwin, so I assume you created a file on the disk called /dev/ttyUSB0 when using it. My knowledge about serial I/O is rather clumsy, but isn't there a virtual COM port attached, or can't you attach a virtual COM port to your USB I/O? AFAIK, you should find something like, say, COM9, which would be available as /dev/com9 or /dev/ttyS8. 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/
EXPAT 1.95.8 build error undefined reference to [EMAIL PROTECTED]'
Hello, I'm trying to build expat 1.95.8 source code downloaded from cygwin mirror site in cygwin. When run make after running ./configure it gives following error: $ make /bin/sh ./libtool --silent --mode=compile gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -I./lib -I. -o lib/xmlp arse.lo -c lib/xmlparse.c /bin/sh ./libtool --silent --mode=compile gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -I./lib -I. -o lib/xmlt ok.lo -c lib/xmltok.c /bin/sh ./libtool --silent --mode=compile gcc -g -O2 -Wall -Wmissing-prototypes -Wstrict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -I./lib -I. -o lib/xmlr ole.lo -c lib/xmlrole.c /bin/sh ./libtool --silent --mode=link gcc -g -O2 -Wall -Wmissing-prototypes -Ws trict-prototypes -fexceptions -DHAVE_EXPAT_CONFIG_H -I./lib -I. -no-undefined -version-info 5:0:5 -rpath /usr/local/lib -o libexpat.la lib/xmlparse.lo lib/xm ltok.lo lib/xmlrole.lo /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../libcygwin.a(libcmain.o):(.text+0x ab): undefined reference to [EMAIL PROTECTED]' collect2: ld returned 1 exit status make: *** [libexpat.la] Error 1 before running make ./configure gives me following output: $ ./configure checking build system type... i686-pc-cygwin checking host system type... i686-pc-cygwin checking for gcc... gcc checking for C compiler default output... a.exe checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... .exe checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for ld used by GCC... /usr/i686-pc-cygwin/bin/ld.exe checking if the linker (/usr/i686-pc-cygwin/bin/ld.exe) is GNU ld.. checking for /usr/i686-pc-cygwin/bin/ld.exe option to reload object checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependant libraries... file_magic file fo 6(.*architecture: i386)? checking command to parse /usr/bin/nm -B output... ok checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for ranlib... ranlib checking for strip... strip checking for objdir... .libs checking for gcc option to produce PIC... -DDLL_EXPORT checking if gcc PIC flag -DDLL_EXPORT works... yes checking if gcc static flag -static works... yes checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.lo... yes checking if gcc supports -fno-rtti -fno-exceptions... yes checking whether the linker (/usr/i686-pc-cygwin/bin/ld.exe) suppor raries... yes checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking dynamic linker characteristics... Win32 ld.exe checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes creating libtool checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for a BSD-compatible install... /usr/bin/install -c checking whether gcc accepts -fexceptions... yes checking for ANSI C header files... (cached) yes checking whether byte ordering is bigendian... no checking for gcc option to accept ANSI C... none needed checking for an ANSI C-conforming const... yes checking for size_t... yes checking for memmove... yes checking for bcopy... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for unistd.h... (cached) yes checking for off_t... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... no checking check.h usability... no checking check.h presence... no checking for check.h... no checking for check.h... (cached) no configure: creating ./config.status config.status: creating Makefile config.status: creating expat_config.h config.status: expat_config.h is unchanged Anik Pal Schlumberger, Vadodara, India -- 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/
Attachment without nntp (was: Uuencoded cygcheck)
Marc Girod marc.girod at gmail.com writes: Larry Hall (Cygwin reply-to-list-only-lh at cygwin.com writes: Is this really a recommended way of transmitting this information? I note in addition: ... - that nobody replied anymore... Well, I tried now the alternative road, and installed TunderBird. I guess I got what I expected: neither nntp nor snntp (563) ports are drilled in my company's firewall. So, this road is blocked too, no? What next? Cry, yes, but then? Marc -- 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 with dev nodes in tar extract
I have created a gzipped compressed tar archive on Linux of an embedded Linux file system. It was compressed under Linux using fakeroot (so that everything is owned as root and dev nodes work). When I untar it under cygwin (tar-1.19-1: 1.19.90-1 hasn't made it out to the mirrors yet), it crashes part way through untarring the dev nodes - after about 64 dev nodes in fact. The dev nodes up to there untar correctly, with the correct permissions, major/minor numbers etc. There is nothing special about the dev node it falls over on - several others which differ only in major/minor number have successfully been untarred. It also untars under Linux OK (v1.18, on Centos 5) - under fakeroot (I don't have root access on the Linux machine). There error message I get is: 171 [main] tar 7900 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Segmentation fault (core dumped) Any ideas? [I'm doing this to serve up the file system over NFS] tar.exe.stackdump Description: tar.exe.stackdump -- 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: Serial port using USB adaptor
On 2/29/08, Corinna Vinschen [EMAIL PROTECTED] wrote: On Feb 29 12:43, hce wrote: Hi, I have a linux serial port problem compiled by Cygwin on window, it runs fine if it connects a 9-pin serial cable and the device name is /dev/ttyS0 (it does not work with com1, I have to translate it to /dev/ttyS0). The problem is when I run the program in a PC without a physical 9-pin serial port on hardware: (1) If there is no USB Serial adaptor connected, it still opens /dev/ttyS0 without any errors. Then, it sends data to that port, and timeout (does not work). (2) If I plug a USB-Serial adaptor and change the device name to /dev/ttyUSB0, it opens that port witout problem but cannot connect to the serial device. /dev/ttyUSB0 works?!? It's no device name recognized by Cygwin, so I assume you created a file on the disk called /dev/ttyUSB0 when using it. It was copied from Linux. My knowledge about serial I/O is rather clumsy, but isn't there a virtual COM port attached, or can't you attach a virtual COM port to your USB I/O? AFAIK, you should find something like, say, COM9, which would be available as /dev/com9 or /dev/ttyS8. My knowledge to Window machine is also limited. So, I should open /dev/com9 or /dev/ttyS8 regardless it is connected to a serial cable or a USB serial adaptor. I don't have the Window machine at home, I'll try next day. Thank you Corinna. Jim -- 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: Serial port using USB adaptor
On Feb 29 22:20, hce wrote: On 2/29/08, Corinna Vinschen [EMAIL PROTECTED] wrote: /dev/ttyUSB0 works?!? It's no device name recognized by Cygwin, so I assume you created a file on the disk called /dev/ttyUSB0 when using it. It was copied from Linux. Yeah, I assumed that much. As I said, that's not a device name Cygwin can do anything useful with. My knowledge about serial I/O is rather clumsy, but isn't there a virtual COM port attached, or can't you attach a virtual COM port to your USB I/O? AFAIK, you should find something like, say, COM9, which would be available as /dev/com9 or /dev/ttyS8. My knowledge to Window machine is also limited. So, I should open /dev/com9 or /dev/ttyS8 regardless it is connected to a serial cable or a USB serial adaptor. I don't have the Window machine at home, I'll try next day. I didn't say you should open /dev/ttyS8. This was just an example. You first have to find out (or set?) the number of the virtual COM port. For all I know it could be COM5 or COM12 or whatever. The important part is that, after you *know* the number X, you can use /dev/comX or /dev/tty[X-1] to access this serial port. Just don't access it using the Windows name, COMx or \\.\COMx, because then you will not get any POSIX serial I/O support from Cygwin. 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/
Rebase all sometimes solve the grace problem.
Hello This is just a record. The grace had not been executed on my cygwin. The suggestion from Goldschmidt, Yadin Y solved the problem. I summerised here. My problem could be seen at http://sourceware.org/ml/cygwin/2008-02/msg00228.html The prescription is the following Close all cygwin processes and if you have sshd running kill it with kill -9. Open a cmd command window (not cygwin window). type:cd (...)\cygwin\bin (default :C;\cygwin\bin but it depends on your install setting.) Then type: ash you will get a $ prompt. Type: ./rebaseall Wait till you get the $ prompt It will take a few minutes. (depends on the environments) After that the close cmd prompt. Start the X server and from the xterm or proper terminal for X. Finally type xmgrace Regards Tatsuro -- Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar http://pr.mail.yahoo.co.jp/toolbar/ -- 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 with dev nodes in tar extract
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Nigel Hathaway on 2/29/2008 4:36 AM: | I have created a gzipped compressed tar archive on Linux of an embedded | Linux file system. It was compressed under Linux using fakeroot (so that | everything is owned as root and dev nodes work). Dev nodes are OS specific. You will probably never get this to work, because cygwin's notions of which major device numbers map to which devices, while modeled after Linux, is not identical to Linux. You are trying to do something that is inherently non-portable. | There error message I get is: | | 171 [main] tar 7900 _cygtls::handle_exceptions: Error while dumping | state (probably corrupted stack) | | Segmentation fault (core dumped) Obviously, it would be nicer if we didn't crash the cygwin syscall, but this is not going to be my highest priority bug investigation. Strace may be helpful to you to find out what is going on just before the crash. And a simple, self-contained test case written in C will make it easier for the cygwin development team to look into this, if it is really that important to you (hint - pointing to tar's source code is not simple enough for honing in on the cause of the crash). - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] volunteer cygwin tar maintainer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyANS84KuGfSFAYARAtw4AJ9wpPzxaJX8lKuFrU+mWIK7ZxsUZgCgmzP0 dgeWrvdwmq2m1nUTUTa3768= =Jso7 -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/
Re: Attachment without nntp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Marc Girod on 2/29/2008 4:05 AM: | Well, I tried now the alternative road, and installed TunderBird. | I guess I got what I expected: neither nntp nor snntp (563) ports are | drilled in my company's firewall. | | So, this road is blocked too, no? I've been annoyed at gmane, too - they provide both http and nntp gateways, but only their nntp gateway allows attaching files. I may be shot for suggesting this, but there are other mail gateways out there besides gmane. For example, nabble.com provides an http gateway and allows attaching files when composing posts to a wrapped mailing list. Then again, nabble's idea of an attachment is sending a URL that requires web access on the reader's end to download the file, rather than sending a multipart message with the file attached in the message itself, so that idea doesn't really fly on this list, either. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyAVG84KuGfSFAYARApuaAJ9hIi/ffpRp++DQZ153osnLKZrIOgCePyKq Jgcv/3JAS4TST4KZG5aNw4A= =8caH -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/
Reference to absolute path seems broken.
I have a very strange issue in Cygwin, it seems that referring to an absolute path is sometimes broken. These examples will probably illustrate the problem: (from root directory) (OK) [EMAIL PROTECTED] / $ diff Cygwin.bat Thumbs.db Binary files Cygwin.bat and Thumbs.db differ (ERROR) [EMAIL PROTECTED] / $ diff /Cygwin.bat Thumbs.db /usr/bin/diff: /Cygwin.bat: No such file or directory Notice the slash before Cygwin.bat. Is this normal?? Other commands such as 'ls' work fine. (OK) [EMAIL PROTECTED] / $ diff /Cygwin.bat Thumbs.db /usr/bin/diff: /Cygwin.bat: No such file or directory I think this gives me problems when installing other software (caml). Can somebody help me? Thanks, Mathijs -- 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: Reference to absolute path seems broken.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Mathijs Romans on 2/29/2008 6:42 AM: | (ERROR) | [EMAIL PROTECTED] / | $ diff /Cygwin.bat Thumbs.db | /usr/bin/diff: /Cygwin.bat: No such file or directory | | Notice the slash before Cygwin.bat. Is this normal?? Other commands | such as 'ls' work fine. The slash before the file name in the error message is normal - diff uses the file name you typed in generating its message. However, why the diff was unable to find the file by its absolute name is not normal - I couldn't reproduce it, so there is something different about your / than there is for mine. Running strace may shed some light on this, as well. | Can somebody help me? | We need 'cygcheck -svr' output, as a text attachment, to learn more about your /. | Problem reports: http://cygwin.com/problems.html - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyA0284KuGfSFAYARArs/AKClMPXrjzU/3+25Fd9xsCVKyUpswgCfXHFy RXnJUpVyAPfaFKTv7AP3MjQ= =5dS4 -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/
Re: Problem with dev nodes in tar extract
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please don't top-post: http://cygwin.com/acronyms/#TOFU | From: Eric Blake [mailto:ebb9 AT byu.net] ~ And please don't feed the spammers: http://cygwin.com/acronyms/#PCYMTNQREAIYR | Dev nodes are OS specific. You will probably never get this to work, | because cygwin's notions of which major device numbers map to which | devices, while modeled after Linux, is not identical to Linux. You are | trying to do something that is inherently non-portable. | According to Nigel Hathaway on 2/29/2008 6:50 AM: | cygwin. Do 'mknod --help' and see what you get !! mknod --help prints the same under Linux or cygwin, because it comes from the same source code for mknod(1). It doesn't change the fact that the underlying mknod(2) between the two OS's is different, and there's nothing that mknod(1) can do about that. | | It turns out that the problem relates to one dev node in particular: | | $ chown root.root dev/ptmx | 7 [main] chown 7940 _cygtls::handle_exceptions: Error while | dumping state | (probably corrupted stack) Now we're getting somewhere. Again, this is a problem in cygwin1.dll, and not in coreutils, tar, or any other user-level program. - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyBF184KuGfSFAYARAi9RAJ4hCS3Adq/60e4WhJRKUZpjZvdhBACaA5tE JykDPXGz6q7O2MEm0wahJxo= =a5PY -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/
Re: Reference to absolute path seems broken.
On Fri, Feb 29, 2008 at 2:48 PM, Eric Blake [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Mathijs Romans on 2/29/2008 6:42 AM: | (ERROR) | [EMAIL PROTECTED] / | $ diff /Cygwin.bat Thumbs.db | /usr/bin/diff: /Cygwin.bat: No such file or directory | | Notice the slash before Cygwin.bat. Is this normal?? Other commands | such as 'ls' work fine. The slash before the file name in the error message is normal - diff uses the file name you typed in generating its message. However, why the diff was unable to find the file by its absolute name is not normal - I couldn't reproduce it, so there is something different about your / than there is for mine. Running strace may shed some light on this, as well. Thanks for your quick answer. I first tried to run strace which gave no output at all. Only then I realised there might be a windows command 'diff' and I was running that one. So I installed diffutils with the great Cygwin packagemanager. Then I got the strace output and the same error. Then I restarted Cygwin, and now the error is gone! (OK) [EMAIL PROTECTED] / $ diff /Cygwin.bat Cygwin.ico Files /Cygwin.bat and Cygwin.ico differ The combination of posix/windows is terribly confusing for me sometimes. Thanks again for your help! Mathijs | Can somebody help me? | We need 'cygcheck -svr' output, as a text attachment, to learn more about your /. | Problem reports: http://cygwin.com/problems.html - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyA0284KuGfSFAYARArs/AKClMPXrjzU/3+25Fd9xsCVKyUpswgCfXHFy RXnJUpVyAPfaFKTv7AP3MjQ= =5dS4 -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/
RE: Problem with dev nodes in tar extract
After a bit of investigation I have narrowed down the problem. Firstly though, the presence of dev nodes is not for the benefit cygwin or Windows. They are exported over NFS so that an embedded ARM-Linux system can use the NFS export as its root file system (for development). This is a very common usage of this kind of facility. It's almost certainly the main reason why (Linux) dev nodes are supported under cygwin. Do 'mknod --help' and see what you get !! It turns out that the problem relates to one dev node in particular: $ chown root.root dev/ptmx 7 [main] chown 7940 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Segmentation fault (core dumped) $ ls -l dev/ptmx crw-r--r-- 1 username groupname 5, 2 Feb 29 13:34 dev/ptmx In Linux this is the pseudo-terminal master device. Why cygwin should have a problem with it, I wouldn't know. Maybe the weirdness is more involved. -Original Message- From: Eric Blake [mailto:[EMAIL PROTECTED] Sent: 29 February 2008 13:06 To: cygwin@cygwin.com; Nigel Hathaway Subject: Re: Problem with dev nodes in tar extract -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Nigel Hathaway on 2/29/2008 4:36 AM: | I have created a gzipped compressed tar archive on Linux of an embedded | Linux file system. It was compressed under Linux using fakeroot (so that | everything is owned as root and dev nodes work). Dev nodes are OS specific. You will probably never get this to work, because cygwin's notions of which major device numbers map to which devices, while modeled after Linux, is not identical to Linux. You are trying to do something that is inherently non-portable. | There error message I get is: | | 171 [main] tar 7900 _cygtls::handle_exceptions: Error while dumping | state (probably corrupted stack) | | Segmentation fault (core dumped) Obviously, it would be nicer if we didn't crash the cygwin syscall, but this is not going to be my highest priority bug investigation. Strace may be helpful to you to find out what is going on just before the crash. And a simple, self-contained test case written in C will make it easier for the cygwin development team to look into this, if it is really that important to you (hint - pointing to tar's source code is not simple enough for honing in on the cause of the crash). - -- Don't work too hard, make some time for fun as well! Eric Blake [EMAIL PROTECTED] volunteer cygwin tar maintainer -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHyANS84KuGfSFAYARAtw4AJ9wpPzxaJX8lKuFrU+mWIK7ZxsUZgCgmzP0 dgeWrvdwmq2m1nUTUTa3768= =Jso7 -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/
Re: Reference to absolute path seems broken.
On Fri, 29 Feb 2008, Mathijs Romans wrote: On Fri, Feb 29, 2008 at 2:48 PM, Eric Blake [EMAIL PROTECTED] wrote: http://cygwin.com/acronyms/#PCYMTNQREAIYR. Thanks. According to Mathijs Romans on 2/29/2008 6:42 AM: | (ERROR) | [EMAIL PROTECTED] / | $ diff /Cygwin.bat Thumbs.db | /usr/bin/diff: /Cygwin.bat: No such file or directory | | Notice the slash before Cygwin.bat. Is this normal?? Other commands | such as 'ls' work fine. The slash before the file name in the error message is normal - diff uses the file name you typed in generating its message. However, why the diff was unable to find the file by its absolute name is not normal - I couldn't reproduce it, so there is something different about your / than there is for mine. Running strace may shed some light on this, as well. Thanks for your quick answer. I first tried to run strace which gave no output at all. Only then I realised there might be a windows command 'diff' and I was running that one. So I installed diffutils with the great Cygwin packagemanager. Then I got the strace output and the same error. Then I restarted Cygwin, and now the error is gone! (OK) [EMAIL PROTECTED] / $ diff /Cygwin.bat Cygwin.ico Files /Cygwin.bat and Cygwin.ico differ The combination of posix/windows is terribly confusing for me sometimes. Thanks again for your help! Mathijs | Can somebody help me? | We need 'cygcheck -svr' output, as a text attachment, to learn more about your /. Note that the above would have probably shown a different diff in your PATH. In general, if a command behaves in an unexpected way, check that you're using the Cygwin version of that command (by using which diff or, better yet, type diff in bash). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! That which is hateful to you, do not do to your neighbor. That is the whole Torah; the rest is commentary. Go and study it. -- Rabbi Hillel -- 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 with dev nodes in tar extract
On Feb 29 13:50, Nigel Hathaway wrote: After a bit of investigation I have narrowed down the problem. Firstly though, the presence of dev nodes is not for the benefit cygwin or Windows. They are exported over NFS so that an embedded ARM-Linux system can use the NFS export as its root file system (for development). This is a very common usage of this kind of facility. It's almost certainly the main reason why (Linux) dev nodes are supported under cygwin. Do 'mknod --help' and see what you get !! It turns out that the problem relates to one dev node in particular: $ chown root.root dev/ptmx 7 [main] chown 7940 _cygtls::handle_exceptions: Error while dumping state (probably corrupted stack) Segmentation fault (core dumped) I found the cause for this SEGV in Cygwin. Should be fixed in the next release. Thanks, 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: Access to Network Drive under ssh
Thanks Larry for your help. I managed to get the posted solution partially working and it is exactly what I was looking for. I only cannot get the shell script to run as a service. The service will attempt to start then fail, but it is really running. Does exec fork a process? I have tried both methods and .bash_login method although simpler is not a feasible solution in my situation. The reason is I am calling ssh sever command, so the auto scripts do not run as I never go into the bash shell. Thank you, Robin -Original Message- From: Larry Hall (Cygwin) [mailto:[EMAIL PROTECTED] Sent: Thursday, February 28, 2008 12:25 PM To: cygwin@cygwin.com Subject: Re: Access to Network Drive under ssh Dang, Robin wrote: http://cygwin.com/ml/cygwin/2006-06/msg00820.html I am having the same problems as in the discussion and would appreciate any help to resolve it. After I log into a ssh session, the drives are not automatically mapped and typing 'net use' gives me unavailable. I can map them manually, but I need them to be mapped automatically to setup the environment properly for my scripts. Anyway, the way I generally get things... well, closer to working, is to create a service that calls 'bash -c some-sshd-init-script', and have the script issue a bunch of 'net use foo bar' commands and then exec sshd. That way you don't have to worry about connections being remembered, because they will always be created for you when sshd starts up. In the post, there is a workaround for the problem, but I cannot write the sshd-init-script and create the service to run it, so it works. Would anyone provide anymore detail or instructions? I'd recommend: Problem reports: http://cygwin.com/problems.html The thread you reference isn't doing anything more to remap the drives than you are manually. It's just automating the process. If that's all you need , then just put the net use foo bar in your .bash_login or other convenient spot that gets run each time you login. The process described above is just a more complicated way of getting here, albeit with certain advantages (it won't remap your drives every time you invoke bash -l). -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- 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: missing shm_open and shm_unlink
On Feb 29 13:36, [EMAIL PROTECTED] wrote: In reply to Don Marquardt's initial question, Corinna indicated the shm_open and shm_unlink would be supported in the next release. I am using the followign version using the uname -a command CYGWIN_NT-5.1 1.5.25(0.156/4/2) 2007-12-14 19:21 i686 Cygwin The two commands do not seem to be supported yet. The version mentioned in Corinna's response is 1.5.24. I am what looks to be the next version. I looked in sys/mman.h and do not see these two function prototypes. Is there a plan to add this functionality? They will be supported in the next *major* release, which will be 1.7.0. The 1.5.x updates since 1.5.24 are basically only bugfixes. They don't get new functionalty over earlier releases. 1.7.0 will take some more time. No schedule yet. Feel free to test developer versions from http://cygwin.com/snapshots/ as long as you don't use them in production environments. 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: missing shm_open and shm_unlink
In reply to Don Marquardt's initial question, Corinna indicated the shm_open and shm_unlink would be supported in the next release. I am using the followign version using the uname -a command CYGWIN_NT-5.1 1.5.25(0.156/4/2) 2007-12-14 19:21 i686 Cygwin The two commands do not seem to be supported yet. The version mentioned in Corinna's response is 1.5.24. I am what looks to be the next version. I looked in sys/mman.h and do not see these two function prototypes. Is there a plan to add this functionality? Thanks Rex Hays rnbhays at rochester dot rr dot com On Mar 12 10:05, Don Marquardt wrote: I am building an application that will used shared memory and I have tried to compile the attached source file. I have version 3.4.4-3 of the gcc compiler and appropriate support libraries. If I use a simple gcc command it complains $ gcc -Wall -Werror writer.c writer.c: In function `main': writer.c:34: warning: implicit declaration of function `shm_open' writer.c:85: warning: implicit declaration of function `shm_unlink' POSIX shared memory objects are not implemented in Cygwin up to 1.5.24. The next release will contain an implementation, but for the time being just use standard anonymous shared memory. Corinna -- 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: missing shm_open and shm_unlink
Thank you for your quick response. Rex Hays Corinna Vinschen [EMAIL PROTECTED] wrote: On Feb 29 13:36, [EMAIL PROTECTED] wrote: In reply to Don Marquardt's initial question, Corinna indicated the shm_open and shm_unlink would be supported in the next release. I am using the followign version using the uname -a command CYGWIN_NT-5.1 1.5.25(0.156/4/2) 2007-12-14 19:21 i686 Cygwin The two commands do not seem to be supported yet. The version mentioned in Corinna's response is 1.5.24. I am what looks to be the next version. I looked in sys/mman.h and do not see these two function prototypes. Is there a plan to add this functionality? They will be supported in the next *major* release, which will be 1.7.0. The 1.5.x updates since 1.5.24 are basically only bugfixes. They don't get new functionalty over earlier releases. 1.7.0 will take some more time. No schedule yet. Feel free to test developer versions from http://cygwin.com/snapshots/ as long as you don't use them in production environments. 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: another minor cygcheck nit
On Fri, Feb 29, 2008 at 10:21:05AM +0100, Corinna Vinschen wrote: On Feb 28 21:47, Linda Walsh wrote: cygcheck doesn't handle the max arg length as shown by xargs... I.e. - cygcheck -f /bin/* bash: /usr/bin/cygcheck: Argument list too long echo /bin/*|xargs cygcheck -f xargs: cygcheck: Argument list too long #Note: cygcheck /bin/[a-r]* # works (wc -wc = 1780 32365) cygcheck /bin/[a-s]* # fails (wc -wc = 1874 33917) # -- looks like a 2^15 boundary prob? xargs --show-limits Your environment variables take up 3867 bytes POSIX upper limit on argument length (this system): 1042661 POSIX smallest allowable upper limit on argument length (all systems): 4096 Maximum length of command we could actually use: 1038794 Size of command buffer we are actually using: 1042661 Guess cygcheck isn't a POSIX app? cygcheck is a native app. For hopefully obvious reasons... 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: Attachment without nntp
Eric Blake wrote: According to Marc Girod on 2/29/2008 4:05 AM: | Well, I tried now the alternative road, and installed TunderBird. | I guess I got what I expected: neither nntp nor snntp (563) ports are | drilled in my company's firewall. | | So, this road is blocked too, no? I've been annoyed at gmane, too - they provide both http and nntp gateways, but only their nntp gateway allows attaching files. I may be shot for suggesting this, but there are other mail gateways out there besides gmane. For example, nabble.com provides an http gateway and allows attaching files when composing posts to a wrapped mailing list. Then again, nabble's idea of an attachment is sending a URL that requires web access on the reader's end to download the file, rather than sending a multipart message with the file attached in the message itself, so that idea doesn't really fly on this list, either. Perhaps I'd better say something here, since I am the one who suggested uuencoding the cygcheck output. I've done this in the past and gotten no complaints, and that's how I see other perople's attached cygcheck output. I can't speak for the OP, but my situation is as follows: 1) Being able to treat mailing lists as news groups is a huge gain, especially in the case of a high-volume list such as Cygwin's. 2) Besides the cygwin list, I follow a large number of other lists via Gmane. As far as I know, there is no good alternative to Gmain - Using Nabble via a web interface is simply unacceptable. 3) I don't like graphical news clients. I use slrn to read news (or mail turned into news), on all the platforms I use, both Unixy ones and Windows. When I post or respond to an article, slrn fires up the editor of my choice (in may case Emacs), and I compose a text message. There is no such thing as an attachment. 4) If using the uuencode method for attachments is not (or no longer?) desired, is there a preferred alternative? (And please don't suggest using Thunderbird.) - Will -- 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: Attachment without nntp
Will Parsons wrote: 4) If using the uuencode method for attachments is not (or no longer?) desired, is there a preferred alternative? (And please don't suggest using Thunderbird.) When posting your cygcheck output, you're asking for help from others and giving them some details that they can look at in order to better help you. If you make it hard or cumbersome for them to look at it, chances are they won't. I know I certainly would not take the time to manually copy and paste and uudecode somebody's cygcheck output, whereas it's trivial for me to look at an attachment. It's just like on busy patches lists where if you send a patch gzipped or with a content-type that's not plain text, people will tend to not review the patch because it takes extra annoying steps to view the file. So if you want to use uuencode that's fine as far as I'm concerned, as long as you are willing to accept that your question will more than likely get less exposure, given that the majority of people that would be inspecting cygcheck output are subscribed to the list and read it in its native email format. As a compromise, you could put the cygcheck output on a pastebin-like site and provide a URL. Brian -- 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: Attachment without nntp
Brian Dessent wrote: Will Parsons wrote: 4) If using the uuencode method for attachments is not (or no longer?) desired, is there a preferred alternative? (And please don't suggest using Thunderbird.) When posting your cygcheck output, you're asking for help from others and giving them some details that they can look at in order to better help you. If you make it hard or cumbersome for them to look at it, chances are they won't. I know I certainly would not take the time to manually copy and paste and uudecode somebody's cygcheck output, whereas it's trivial for me to look at an attachment. It's just like on busy patches lists where if you send a patch gzipped or with a content-type that's not plain text, people will tend to not review the patch because it takes extra annoying steps to view the file. I certainly don't *want* to make it inconvenient for potential responders - I simply thought that uuencoding was the way one attached using the nntp interface. If doing so is an annoyance rather than a help, I certainly won't do it in the future. What then is the recommendation - include it because it's better than no cygcheck output at all, or don't bother? So if you want to use uuencode that's fine as far as I'm concerned, as long as you are willing to accept that your question will more than likely get less exposure, given that the majority of people that would be inspecting cygcheck output are subscribed to the list and read it in its native email format. As a compromise, you could put the cygcheck output on a pastebin-like site and provide a URL. I'm not sure what a pastebin-like site is, but would it really be more convenient for someone to go to a web site to retrieve output than to uudecode the mail? (I don't know about the mail reader you use, but for me, uudecoding is a couple of keystrokes in slrn - no manual copying and pasting required.) - Will -- 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: Attachment without nntp
Will Parsons wrote: I certainly don't *want* to make it inconvenient for potential responders - I simply thought that uuencoding was the way one attached using the nntp interface. If doing so is an annoyance rather than a help, I certainly won't do it in the future. What then is the recommendation - include it because it's better than no cygcheck output at all, or don't bother? I'd say that including the cygcheck output inline is better than uuencoding it, even though that tends to be frowned up as it gives lots of false positives to future archive searchers. But that's just MHO. I'm not sure what a pastebin-like site is, but would it really be more http://pastebin.com/ convenient for someone to go to a web site to retrieve output than to uudecode the mail? (I don't know about the mail reader you use, but for me, uudecoding is a couple of keystrokes in slrn - no manual copying and pasting required.) It's most definitely easier for me to click on a URL than to save a message to a file, switch to a prompt, cd to the directory where I saved it, fire up an editor, remove the non-uue parts, figure out if I even have the uudecode program installed, realize that I don't, go install one, pipe it through uudecode, then finally view the file. It's easy for you in slrn because that's a newsreader, and uuencoded content in newsgroups are common. I don't use a newsreader, I use an email client and uuencoded content in email is fairly rare. Brian -- 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/
