ask-2.5.0 - a new package for review
(a Debian) Python Project http://www.paganini.net/ask/ has bee ported. Please review. http://tierra.dyndns.org:81/cygwin/ask/ask-2.5.0-1-src.tar.bz2 http://tierra.dyndns.org:81/cygwin/ask/ask-2.5.0-1.tar.bz2 Jari @ ask sdesc: Active Spam Killer in python. Uses opt-in method. ldesc: Python based ASK, Active Spam Killer, takes an active approach in solving the problem: Everytime an email is received, a message is sent back to the sender asking for confirmation. If that sender does not confirm the message, it remains queued for delivery. skip: curr: version # prev: version # test: version category: Mail requires: python # external-source: package drwxr-xr-x root/None 0 2003-06-29 19:47:46 usr/ drwxr-xr-x root/None 0 2003-06-29 19:47:46 usr/doc/ drwxr-xr-x root/None 0 2003-06-29 19:47:46 usr/doc/ask-2.5.0/ -rw-r--r-- root/None 18009 2003-06-29 19:47:46 usr/doc/ask-2.5.0/COPYING -rw-r--r-- root/None 2356 2003-06-29 19:47:46 usr/doc/ask-2.5.0/TODO -rw-r--r-- root/None 12873 2003-06-29 19:47:46 usr/doc/ask-2.5.0/ChangeLog drwxr-xr-x root/None 0 2003-06-29 19:47:48 usr/doc/Cygwin/ -rw-r--r-- root/None 2953 2003-06-29 19:47:48 usr/doc/Cygwin/ask-2.5.0.README drwxr-xr-x root/None 0 2003-06-29 19:47:50 usr/usr/ drwxr-xr-x root/None 0 2003-06-29 19:47:50 usr/usr/bin/ -rwxr-xr-x root/None 3547 2003-06-29 19:47:50 usr/usr/bin/ask.py -rwxr-xr-x root/None 6410 2003-06-29 19:47:52 usr/usr/bin/asksetup.py -rwxr-xr-x root/None 1436 2003-06-29 19:47:52 usr/usr/bin/askversion.py -rwxr-xr-x root/None 3359 2003-06-29 19:47:52 usr/usr/bin/asksenders.py drwxr-xr-x root/None 0 2003-06-29 19:47:50 usr/usr/lib/ drwxr-xr-x root/None 0 2003-06-29 19:47:50 usr/usr/lib/ask/ -rw-r--r-- root/None 14036 2003-06-29 19:47:52 usr/usr/lib/ask/askconfig.py -rw-r--r-- root/None 2459 2003-06-29 19:47:52 usr/usr/lib/ask/asklock.py -rw-r--r-- root/None 2290 2003-06-29 19:47:52 usr/usr/lib/ask/asklog.py -rw-r--r-- root/None 16254 2003-06-29 19:47:52 usr/usr/lib/ask/askmail.py -rw-r--r-- root/None 9359 2003-06-29 19:47:52 usr/usr/lib/ask/askmain.py -rw-r--r-- root/None 34484 2003-06-29 19:47:52 usr/usr/lib/ask/askmessage.py -rw-r--r-- root/None 22795 2003-06-29 19:47:52 usr/usr/lib/ask/askremote.py drwxr-xr-x root/None 0 2003-06-29 19:47:50 usr/usr/share/ drwxr-xr-x root/None 0 2003-06-29 19:47:50 usr/usr/share/man/ drwxr-xr-x root/None 0 2003-06-29 19:47:50 usr/usr/share/man/man1/ -rw-r--r-- root/None 2135 2003-06-29 19:47:56 usr/usr/share/man/man1/ask.py.1 -rw-r--r-- root/None 1171 2003-06-29 19:47:56 usr/usr/share/man/man1/asksenders.py.1 -rw-r--r-- root/None 1202 2003-06-29 19:47:56 usr/usr/share/man/man1/asksetup.py.1 -rw-r--r-- root/None 673 2003-06-29 19:47:56 usr/usr/share/man/man1/askversion.py.1 drwxr-xr-x root/None 0 2003-06-29 19:47:50 usr/usr/share/ask/ drwxr-xr-x root/None 0 2003-06-29 19:47:50 usr/usr/share/ask/samples/ -rw-r--r-- root/None89 2003-06-29 19:47:52 usr/usr/share/ask/samples/blacklist.txt -rw-r--r-- root/None90 2003-06-29 19:47:52 usr/usr/share/ask/samples/ignorelist.txt -rw-r--r-- root/None 10027 2003-06-29 19:47:54 usr/usr/share/ask/samples/sample_askrc -rw-r--r-- root/None89 2003-06-29 19:47:54 usr/usr/share/ask/samples/whitelist.txt drwxr-xr-x root/None 0 2003-06-29 19:47:50 usr/usr/share/ask/templates/ -rw-r--r-- root/None 394 2003-06-29 19:47:54 usr/usr/share/ask/templates/blacklist_da.txt -rw-r--r-- root/None 568 2003-06-29 19:47:54 usr/usr/share/ask/templates/blacklist_de.txt -rw-r--r-- root/None 493 2003-06-29 19:47:54 usr/usr/share/ask/templates/blacklist_en.txt -rw-r--r-- root/None 537 2003-06-29 19:47:54 usr/usr/share/ask/templates/blacklist_es.txt -rw-r--r-- root/None 700 2003-06-29 19:47:54 usr/usr/share/ask/templates/blacklist_fi.txt -rw-r--r-- root/None 673 2003-06-29 19:47:54 usr/usr/share/ask/templates/blacklist_fr.txt -rw-r--r-- root/None 523 2003-06-29 19:47:54 usr/usr/share/ask/templates/blacklist_it.txt -rw-r--r-- root/None 524 2003-06-29 19:47:54 usr/usr/share/ask/templates/blacklist_nl.txt -rw-r--r-- root/None 476 2003-06-29 19:47:54 usr/usr/share/ask/templates/blacklist_ptbr.txt -rw-r--r-- root/None 406 2003-06-29 19:47:54 usr/usr/share/ask/templates/confirm_da.txt -rw-r--r-- root/None 495 2003-06-29 19:47:54 usr/usr/share/ask/templates/confirm_de.txt -rw-r--r-- root/None 344 2003-06-29 19:47:54 usr/usr/share/ask/templates/confirm_en.txt -rw-r--r-- root/None 371 2003-06-29 19:47:54 usr/usr/share/ask/templates/confirm_es.txt -rw-r--r-- root/None 905 2003-06-29 19:47:56 usr/usr/share/ask/templates/confirm_fi.txt -rw-r--r-- root/None 412 2003-06-29 19:47:56 usr/usr/share/ask/templates/confirm_fr.txt -rw-r--r-- root/None 395 2003-06-29 19:47:56
Re: ask-2.5.0 - a new package for review
Jari Aalto+mail.linux wrote: (a Debian) Python Project http://www.paganini.net/ask/ has bee ported. Please review. http://tierra.dyndns.org:81/cygwin/ask/ask-2.5.0-1-src.tar.bz2 http://tierra.dyndns.org:81/cygwin/ask/ask-2.5.0-1.tar.bz2 Before you ITP any more packages, you should address the fact that cygbuild has been vetoed, and therefore, since all your packages use it, they are blocked until this issue is solved. I strongly suspect that patches to incrementally enhance generic-build-script will be welcomed. The objection is that you are trying to introduce yet another packaging method into an already too-diverse landscape. @ ask sdesc: Active Spam Killer in python. Uses opt-in method. ldesc: Python based ASK, Active Spam Killer, takes an active approach in solving the problem: Everytime an email is received, a message is sent back to the sender asking for confirmation. If that sender does not confirm the message, it remains queued for delivery. skip: curr: version # prev: version # test: version category: Mail requires: python # external-source: package The commented unnecessary lines are annoying, and your use of @, skip: and curr: show that need to read and learn http://cygwin.com/setup.html#setup.hint . drwxr-xr-x root/None 0 2003-06-29 19:47:50 usr/usr/ Obvious packaging error right there. Max.
Re: ask-2.5.0 - a new package for review
Charles Wilson wrote: Max Bowsher wrote: Jari Aalto+mail.linux wrote: (a Debian) Python Project http://www.paganini.net/ask/ has bee ported. Please review. http://tierra.dyndns.org:81/cygwin/ask/ask-2.5.0-1-src.tar.bz2 http://tierra.dyndns.org:81/cygwin/ask/ask-2.5.0-1.tar.bz2 Before you ITP any more packages, you should address the fact that cygbuild has been vetoed, and therefore, since all your packages use it, they are blocked until this issue is solved. Not necessarily. But, you realize Max that neither generic-build-script nor mknetrel are available as packages either? So IMO it doesn't really matter that cygbuild isn't an official package, as long as it is available somewhere... I could have misinterpreted cgf's veto. I'm not entirely sure whether he was vetoing the package, or the use of yet another build system. Max.
Re: ask-2.5.0 - a new package for review
On Mon, 2003-06-30 at 07:21, Max Bowsher wrote: I could have misinterpreted cgf's veto. I'm not entirely sure whether he was vetoing the package, or the use of yet another build system. The build system per se doesn't matter. We hashed this out waay back. What matters is: The binary layout. The source layout. To that end we had two acceptable source layouts, and one acceptable binary layout, documented at http://www.cygwin.com/setup.html. I don't know why cgf veto'd the cygbuild package - and I'm not going to guess. I can't imagine the use of 'cygbuild' being veto'd - we'd have to pull quite a few packages if the build scripts are controlled... all of mine among them. That said, I really don't think we want to formalise the package creation script. If we -really- are heading to compatibility with any existing format, surely our efforts are bested directed to achieving that, not to (relatively minor) fiddling within our adhoc format. Rob -- GPG key available at: http://members.aardvark.net.au/lifeless/keys.txt. signature.asc Description: This is a digitally signed message part
Re: ask-2.5.0 - a new package for review
On Sun, Jun 29, 2003 at 10:21:18PM +0100, Max Bowsher wrote: Charles Wilson wrote: Max Bowsher wrote: Jari Aalto+mail.linux wrote: (a Debian) Python Project http://www.paganini.net/ask/ has bee ported. Please review. http://tierra.dyndns.org:81/cygwin/ask/ask-2.5.0-1-src.tar.bz2 http://tierra.dyndns.org:81/cygwin/ask/ask-2.5.0-1.tar.bz2 Before you ITP any more packages, you should address the fact that cygbuild has been vetoed, and therefore, since all your packages use it, they are blocked until this issue is solved. Not necessarily. But, you realize Max that neither generic-build-script nor mknetrel are available as packages either? So IMO it doesn't really matter that cygbuild isn't an official package, as long as it is available somewhere... I could have misinterpreted cgf's veto. I'm not entirely sure whether he was vetoing the package, or the use of yet another build system. I was vetoing the package for inclusion in cygwin. I was actually nodding my head when I read your objection to packages being submitted which use cygbuild, but Chuck is right. Since there is no official package in the distribution, it would be inconsistent to block a package because it uses a build system not in the distribution. So, IMO, there's no reason to block packages which use diverse build systems as long as the build system itself is available somewhere. cgf
Re: ask-2.5.0 - a new package for review
Robert Collins wrote: That said, I really don't think we want to formalise the package creation script. If we -really- are heading to compatibility with any existing format, surely our efforts are bested directed to achieving that, not to (relatively minor) fiddling within our adhoc format. Agreed. In my dream world, setup.exe will interoperate with both deb and rpm packages. There will be tools (or libraries) that allow synchronization of the various databases (deb's installed, /var/rpm/*, and /etc/setup/*). Setup.exe will update all of them. Cygwinized rpm and apt tools will update all of them. And we will be able to use any of those tools to install stuff: setup, rpmderivatives, aptderivatives. And we (package maintainers) will be able to use debian or rpm tools to package our stuff, and we'll eventually migrate away from tarballs. That's my dream. But it'll take years to get there, and I'm not in a hurry. To tell you the truth, I think a nice interim step would be a tool of some sort that leveraged deb/rpm packages, to create setup-compatible tarballs, complete with taking rpm-style post/pre scripts and putting them in the right place so that setup will do the right thing. Then, for instance, we could simply use rpm tools to create an rpm -- and then run rpm2setup to create the distributable tarball and src tarball. Ditto .deb. I think this is a better path to take than worrying about cygbuild vs mknetrel vs generic-pkg-script vs --Chuck
Re: ask-2.5.0 - a new package for review
On Sun, Jun 29, 2003 at 06:18:17PM -0400, Christopher Faylor wrote: I was vetoing the package for inclusion in cygwin. I was actually nodding my head when I read your objection to packages being submitted which use cygbuild, but Chuck is right. Since there is no official package in the distribution, it would be inconsistent to block a package ^^^ build package system in the cygwin distribution. because it uses a build system not in the distribution. cgf
patch to generic-build-script
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I backported the changed I was already using in my latest packages the
full diff is in attach (trying to avoid the mailer change it I'm using
an extension DIFFERENT from .txt or anything that could be interpreted
as text/plain...).
Here goes the comment:
| --- templates/generic-build-script2003-06-13 21:46:59.0 +0200
| +++ generic.sh2003-06-29 23:05:58.0 +0200
| @@ -3,8 +3,8 @@
| tdir=`echo $0 | sed 's%[\\/][^\\/][^\\/]*$%%'`
| test x$tdir = x$0 tdir=.
| scriptdir=`cd $tdir; pwd`
| -# find src directory.
| -# If scriptdir ends in SPECS, then topdir is $scriptdir/..
| +# find src directory.
| +# If scriptdir ends in SPECS, then topdir is $scriptdir/..
| # If scriptdir ends in CYGWIN-PATCHES, then topdir is $scriptdir/../..
| # Otherwise, we assume that topdir = scriptdir
| topdir1=`echo ${scriptdir} | sed 's%/SPECS$%%'`
Just some trailing spaces stripping paranoia.
I hate 'em ;-)
| @@ -26,15 +26,25 @@
| export FULLPKG=${PKG}-${VER}-${REL}
|
| # determine correct decompression option and tarball filename
| -if [ -e ${PKG}-${VER}.tar.gz ] ; then
| - export opt_decomp=z
| - export src_orig_pkg_ext=gz
| -elif [ -e ${PKG}-${VER}.tar.bz2 ] ; then
| +export BASEPKG=${PKG}-${VER}
| +if [ -e ${BASEPKG}.tar.bz2 ] ; then
|export opt_decomp=j
| - export src_orig_pkg_ext=bz2
| + export src_orig_pkg_name=${BASEPKG}.tar.bz2
| +elif [ -e ${BASEPKG}.tar.gz ] ; then
| + export opt_decomp=z
| + export src_orig_pkg_name=${BASEPKG}.tar.gz
| +elif [ -e ${BASEPKG}.tgz ] ; then
| + export opt_decomp=z
| + export src_orig_pkg_name=${BASEPKG}.tgz
| +elif [ -e ${BASEPKG}.tar ] ; then
| + export opt_decomp=
| + export src_orig_pkg_name=${BASEPKG}.tar
| +else
| + echo Cannot find original package.
| + exit 1
| fi
|
| -export src_orig_pkg_name=${PKG}-${VER}.tar.${src_orig_pkg_ext}
| +# determine correct names for generated files
| export src_pkg_name=${FULLPKG}-src.tar.bz2
| export src_patch_name=${FULLPKG}.patch
| export bin_pkg_name=${FULLPKG}.tar.bz2
Seems a little more general to me.
Moreover the past script had the problem if not having a else case,
so if neither .tar.gz nor .tar.bz2 was found it would have continued
with errors.
| @@ -68,7 +78,7 @@
|(cd ${topdir} \
|tar xv${opt_decomp}f ${src_orig_pkg} ; \
|cd ${topdir} \
| - patch -p0 ${src_patch}
| + patch -p0 ${src_patch}
| mkdirs )
| }
| conf() {
Again, trailing spaces paranoia.
| @@ -79,8 +89,7 @@
|--exec-prefix=${prefix} --sysconfdir=${sysconfdir} \
|--libdir=${prefix}/lib --includedir=${prefix}/include \
|--libexecdir='${sbindir}' --localstatedir=/var \
| - --datadir='${prefix}/share'
| -)
| + --datadir='${prefix}/share' )
| }
| build() {
|(cd ${objdir} \
alla the other closed parens are in line consistency paranoia.
| @@ -96,7 +105,7 @@
| }
| install() {
|(cd ${objdir} \
| - make install DESTDIR=${instdir}
| + make install DESTDIR=${instdir}
|if [ -f ${instdir}${prefix}/info/dir ] ; then \
| rm ${instdir}${prefix}/info/dir ; \
|fi \
I guess trailing space paranoia.
| @@ -106,9 +115,6 @@
|if [ ! -d ${instdir}${prefix}/doc/Cygwin ]; then \
| mkdir -p ${instdir}${prefix}/doc/Cygwin ; \
|fi \
| - if [ ! -d ${instdir}${sysconfdir}/postinstall ]; then \
| -mkdir -p ${instdir}${sysconfdir}/postinstall ; \
| - fi \
|templist=; \
|for f in ${srcdir}/ANNOUNCE ${srcdir}/CHANGES ${srcdir}/INSTALL \
| ${srcdir}/KNOWNBUG ${srcdir}/LICENSE ${srcdir}/README \
| @@ -131,14 +137,16 @@
| fi ;\
|fi ;\
|if [ -f ${srcdir}/CYGWIN-PATCHES/postinstall.sh ] ; then \
| - /usr/bin/install -m 755 ${srcdir}/CYGWIN-PATCHES/postinstall.sh \
| +if [ ! -d ${instdir}${sysconfdir}/postinstall ]; then \
| + mkdir -p ${instdir}${sysconfdir}/postinstall ; \
| +fi \
| +/usr/bin/install -m 755 ${srcdir}/CYGWIN-PATCHES/postinstall.sh \
|${instdir}${sysconfdir}/postinstall/${PKG}.sh
|fi )
| }
So that postinstall directory is created only if needed.
| strip() {
|(cd ${instdir} \
| - find . -name *.dll | xargs strip /dev/null 21
| - find . -name *.exe | xargs strip /dev/null 21
| + find . -name *.dll -or -name *.exe | xargs strip /dev/null 21
|true )
| }
| pkg() {
let's save one line and two command execution paranoia.
| @@ -157,32 +165,70 @@
| }
| spkg() {
|(mkpatch \
| + if [ ${SIG} ]; then name=${srcinstdir}/${src_patch_name}
text=PATCH sigfile; fi \
|cp ${src_orig_pkg} ${srcinstdir}/${src_orig_pkg_name} \
| + if [ -e ${src_orig_pkg}.sig ]; then cp ${src_orig_pkg}.sig
${srcinstdir}/; fi \
|cp $0 ${srcinstdir}/`basename $0` \
| + if [ \( ${SIG} \) -a \( -e $0.sig \) ]; then cp $0.sig
${srcinstdir}/; fi \
|cd ${srcinstdir} \
|tar cvjf ${src_pkg} * )
| }
Part of my optional package signature by mantainer.
(used only when env SIG is defined)
| finish() {
| - rm -rf ${srcdir}
| + rm -rf
Re: xinit: No such file or directory
I only run into this problem as nonadministrator. I don't know if this will help in your case, but maybe during instalation process you have selected Install for: Only me instead of All users? -- Tomasz Rojek
Re: EIO error on background tty reads
On Sun, Jun 29, 2003 at 11:41:56AM -0400, Rafael Kitover wrote: While working on my port of screen for cygwin, I have tracked down the issue that did not allow me to reattach detached screens. A detached screen process owns a certain tty to which the new, attaching screen process connects to and reads/writes to. Recent builds of cygwin return an EIO on a read from the tty, the following small change fixes this, but I have to admit that this is my first time swimming in the bowels of cygwin itself and I don't know if this makes sense or not. This isn't a cygwin internals special case knowledge type of thing. A grep of cygwin sources shows that bg_check is called with one of two arguments: either SIGTTOU or SIGTTIN is used. So, your change effectively makes the final goto seEIO a no-op since it specifically checks for both inputs and bypasses the final goto. Sorry, but if this fixes the problem it is a band-aid. cgf 2003-06-29 Rafael Kitover [EMAIL PROTECTED] * Fix EIO errors on background reads from a tty. Index: cygwin/fhandler_termios.cc === RCS file: /cvs/src/src/winsup/cygwin/fhandler_termios.cc,v retrieving revision 1.46 diff -u -p -r1.46 fhandler_termios.cc --- cygwin/fhandler_termios.cc 16 Jun 2003 03:24:10 - 1.46 +++ cygwin/fhandler_termios.cc 29 Jun 2003 14:59:13 - @@ -160,7 +160,7 @@ fhandler_termios::bg_check (int sig) goto setEIO; else if (!sigs_ignored) /* nothing */; - else if (sig == SIGTTOU) + else if (sig == SIGTTOU || sig == SIGTTIN) return bg_ok; /* Just allow the output */ else goto setEIO; /* This is an output error */
Re: newbie shell-users howto, guide, cheatsheet, or reference?
on Fri, Jun 27, 2003 at 08:31:40PM +0100, Karsten M. Self ([EMAIL PROTECTED]) wrote: on Thu, Jun 26, 2003 at 10:55:17PM +0200, Hannu E K Nevalainen (garbage mail) ([EMAIL PROTECTED]) wrote: From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Karsten M. Self - The shell. Bash. - Directories. '/' rather than '\'. Cygwin naming conventions. Accessing legacy MS Windows paths. - Essential commands. Likely: ls, cd, pwd, rm, less, cat. - Getting help. man, apropos. IIRC there is a HOWTO with a certain Linux distro (they use a Red Hat as a logo ;) that should fulfill at least part of your needs (can't remember the name right now... MSDOS-HOWTO?). Useful, but not sufficiently focused. Given my research and responses (both on and off list), I'll be putting together something shortly at http://twiki.iwethey.org/, which the Cygwin project will be free to use. For better or worse, started as: http://twiki.iwethey.org/Main/CygwinEndUserQuickReference Peace. -- Karsten M. Self [EMAIL PROTECTED]http://kmself.home.netcom.com/ What Part of Gestalt don't you understand? Backgrounder on the Caldera/SCO vs. IBM and Linux dispute. http://sco.iwethey.org/ pgp0.pgp Description: PGP signature
Re: example needed pls: `cygpath -c HANDLE'
Hallo Soren,
you also wrote:
I am trying to finish a test script that uses ActivePerl to call `cygpath`
from itself (a system call, by open()-ing a pipe to capture the output of
the tool ...
{... stuff ...}
open(CTH, '-|', C:/cygwin/bin/cygpath $MS_path_filename)
or die Could not open() call to 'cygpath', what is up?;
$cygstyle_path = CTH;
chomp $cygstyle_path;
{... stuff ...}
#!/bin/perl
$MS_path_filename = 'H:\bin';
$MS_path_filename = quotemeta($MS_path_filename);
open(CTH, '-|', H:/bin/cygpath $MS_path_filename)
or die Could not open() call to 'cygpath', what is up?;
$cygstyle_path = CTH;
chomp $cygstyle_path;
print $cygstyle_path\n;
# SCRIPT_END
$ /bin/soren_problem.pl
/bin
What is the problem?
Gerrit
--
=^..^=
--
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: newbie shell-users howto, guide, cheatsheet, or reference?
On Sun, Jun 29, 2003 at 10:12:32AM +0100, Karsten M. Self wrote: on Fri, Jun 27, 2003 at 08:31:40PM +0100, Karsten M. Self ([EMAIL PROTECTED]) wrote: on Thu, Jun 26, 2003 at 10:55:17PM +0200, Hannu E K Nevalainen (garbage mail) ([EMAIL PROTECTED]) wrote: From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Karsten M. Self - The shell. Bash. - Directories. '/' rather than '\'. Cygwin naming conventions. Accessing legacy MS Windows paths. - Essential commands. Likely: ls, cd, pwd, rm, less, cat. - Getting help. man, apropos. IIRC there is a HOWTO with a certain Linux distro (they use a Red Hat as a logo ;) that should fulfill at least part of your needs (can't remember the name right now... MSDOS-HOWTO?). Useful, but not sufficiently focused. Given my research and responses (both on and off list), I'll be putting together something shortly at http://twiki.iwethey.org/, which the Cygwin project will be free to use. For better or worse, started as: http://twiki.iwethey.org/Main/CygwinEndUserQuickReference Peace. Rather than throwing your efforts out there and expecting the cygwin project to use them, why don't you investigate what is required to change the actual documentation? A getting started section could be added to the actual documentation. As a general rule, your efforts will have a much wider audience and will benefit more people if you direct them towards the actual distribution rather than putting them on a personal web page. cgf -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to [EMAIL PROTECTED] and be permanently blocked from mailing lists at sources.redhat.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: free pascal cross compiler from windows to linux working.
Harald Houppermans wrote: So other weird red hat linux server behaviour... I have to use: ./hello ( just hello does work on knoppix ) That's probably a red hat linux server setting... ./ means current folder... Just wondering what that is all about. . is not in the PATH by default on most Unixes, as that introduces a security hole. Why is putting the current path in the path variable a security hole ? That's really a question for another list. Still, just think about all the exploit possibilities that exist if you have a path with a constantly changing state and without a defined set of permissions. I don't think it's a stretch to state that this is a less secure environment than the reverse. IMHO, it's unlikely that Linux can destroy NTFS partitions that it only has read-only access to. I've been wrong before, though... Well it sounds to scary for me :D Don't be scared. The read-only NTFS driver for Linux has been stable for years. With the exception of disk partitioning tools, which are expected to manipulate partitions and therefore very likely will destroy existing data, there's nothing in Linux that's going to damage your NTFS partition. The read-write version of the NTFS driver is another story however. Still, this all seems pretty off-topic for this list as well. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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: request: add hive unload functionality
[EMAIL PROTECTED] wrote:
after browsing the source, I gathered that whenever a new process is spawned(spawn.cc) the user's hive is loaded and linked to HKEY_CURRENT_USER. but, the user's hive is never unloaded i.e. whenever the last process running as that user terminates.
so I humbly suggest adding an unload function to the registry like:
void unload_registry_hive (PSID psid){ ... }
then wait until the last process running as that user exits and then unload the hive.
the reason for the request is I have a couple of programs that monitor user logon/logoffs. they work by monitoring the HKEY_USERS hive and with cygwin-sshd, the hives never unload even after I kill sshd...
Hm, a worthwhile idea. FWIW, if you'd like to see this change happen in
a timely manner, I'd suggest submitting a patch for this. If you're
interested, see http://cygwin.com/contrib.html.
Thanks,
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
--
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: newbie shell-users howto, guide, cheatsheet, or reference?
on Sun, Jun 29, 2003 at 11:26:14AM -0400, Christopher Faylor ([EMAIL PROTECTED]) wrote: On Sun, Jun 29, 2003 at 10:12:32AM +0100, Karsten M. Self wrote: on Fri, Jun 27, 2003 at 08:31:40PM +0100, Karsten M. Self ([EMAIL PROTECTED]) wrote: Given my research and responses (both on and off list), I'll be putting together something shortly at http://twiki.iwethey.org/, which the Cygwin project will be free to use. For better or worse, started as: http://twiki.iwethey.org/Main/CygwinEndUserQuickReference Peace. Rather than throwing your efforts out there and expecting the cygwin project to use them, why don't you investigate what is required to change the actual documentation? A getting started section could be added to the actual documentation. As a general rule, your efforts will have a much wider audience and will benefit more people if you direct them towards the actual distribution rather than putting them on a personal web page. I've been through the existing Cygwin docs. I don't see anything specifically answering this need. The page isn't a personal web page. IWeThey is a group of tech professionals who've been loosely associated for over five years, and have run a number of web and other Internet-based services for much of this time. I've got a big hand in the TWiki. It's not by any means limited to me alone, only my product. I'm developing this documentation as much for my own use as for the community's. Which is to say, I'll want to be able to update and modify the docs as time goes by. Consider the interim docs a work in progress. I've found the Wiki model to be useful and valuable for developing online resources. An example of this is http://sco.iwethey.org/, a compendium on information regarding the Caldera/SCO vs. IBM Linux lawsuit. This started just a month ago as three Google search links. It's now well over 60 pages of printed material (probably closer to 100), most of it not written by me. It's a powerful mechanism for collaborative documentation development. The document I'm developing presently is just that -- a document in development. When it's at a stage I feel it's suitable for inclusion in the core Cygwin docs, I'll contact whomever is appropriate and y'all can cleave off a snapshot. I'll likely continue to use the TWiki as a development tool however, for extending this and related docs. Peace. -- Karsten M. Self [EMAIL PROTECTED]http://kmself.home.netcom.com/ What Part of Gestalt don't you understand? TWikIWeThey: An experiment in collective intelligence. Stupidity. Whatever. Technical docs, discussion, reviews, opinion. http://twiki.iwethey.org/ pgp0.pgp Description: PGP signature
Re: newbie shell-users howto, guide, cheatsheet, or reference?
On Sun, Jun 29, 2003 at 10:58:25PM +0100, Karsten M. Self wrote: on Sun, Jun 29, 2003 at 11:26:14AM -0400, Christopher Faylor ([EMAIL PROTECTED]) wrote: On Sun, Jun 29, 2003 at 10:12:32AM +0100, Karsten M. Self wrote: on Fri, Jun 27, 2003 at 08:31:40PM +0100, Karsten M. Self ([EMAIL PROTECTED]) wrote: Given my research and responses (both on and off list), I'll be putting together something shortly at http://twiki.iwethey.org/, which the Cygwin project will be free to use. For better or worse, started as: http://twiki.iwethey.org/Main/CygwinEndUserQuickReference Peace. Rather than throwing your efforts out there and expecting the cygwin project to use them, why don't you investigate what is required to change the actual documentation? A getting started section could be added to the actual documentation. As a general rule, your efforts will have a much wider audience and will benefit more people if you direct them towards the actual distribution rather than putting them on a personal web page. I've been through the existing Cygwin docs. I don't see anything specifically answering this need. Huh? Addressing what need? Did I say that there wasn't a need to address? Is this really hard to understand? If you want people to benefit from your work, you try to get said work into the main cygwin web site and cygwin distribution. The page isn't a personal web page. IWeThey is a group of tech professionals who've been loosely associated for over five years, and have run a number of web and other Internet-based services for much of this time. I've got a big hand in the TWiki. It's not by any means limited to me alone, only my product. As far as the cygwin project is concerned, it is a personal web page. It is not located on the cygwin site. It is not incorporated with the rest of the documentation. The fact that there is a group of people associated with your effort is irrelevant. The document I'm developing presently is just that -- a document in development. When it's at a stage I feel it's suitable for inclusion in the core Cygwin docs, I'll contact whomever is appropriate and y'all can cleave off a snapshot. I'll likely continue to use the TWiki as a development tool however, for extending this and related docs. Ok. This is not what you said at first. If you are willing to do some work to get this into the cygwin documentation, it will be appreciated. If you are expecting that you can just say It's over there take it or leave it then I suspect that this will always exist on a non-cygwin-project web site and we'll be seeing a lot of I followed the directions over at... followed by The ... site is not affiliated with the cygwin project. We take no responsibility for the information there. If you have questions please contact the people at ... directly. 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: ssh
on Fri, Jun 27, 2003 at 10:38:52AM +0200, Julien VARLET ([EMAIL PROTECTED]) wrote: I have created a RSA pair of keys.it's ok. But i want to automate passphrase. In tclsh : I have the following command line : ssh-agent $SHELL -- can't read SHELL : no such variable ssh-add -- Could not open connection to your authentication agent Child process exited abnormally Can you help me please ? man ssh-agent Typically, ssh-agent *either* runs as the parent process of a Window session login, _or_ from within individual shells. It's a bit tricky working out how to share a single ssh-agent server among independently launched shells. Peace. -- Karsten M. Self [EMAIL PROTECTED]http://kmself.home.netcom.com/ What Part of Gestalt don't you understand? Geek for hire: http://kmself.home.netcom.com/resume.html pgp0.pgp Description: PGP signature
Re: newbie shell-users howto, guide, cheatsheet, or reference?
on Sun, Jun 29, 2003 at 06:30:24PM -0400, Christopher Faylor ([EMAIL PROTECTED]) wrote: On Sun, Jun 29, 2003 at 10:58:25PM +0100, Karsten M. Self wrote: on Sun, Jun 29, 2003 at 11:26:14AM -0400, Christopher Faylor ([EMAIL PROTECTED]) wrote: On Sun, Jun 29, 2003 at 10:12:32AM +0100, Karsten M. Self wrote: on Fri, Jun 27, 2003 at 08:31:40PM +0100, Karsten M. Self ([EMAIL PROTECTED]) wrote: Given my research and responses (both on and off list), I'll be putting together something shortly at http://twiki.iwethey.org/, which the Cygwin project will be free to use. For better or worse, started as: http://twiki.iwethey.org/Main/CygwinEndUserQuickReference Peace. Rather than throwing your efforts out there and expecting the cygwin project to use them, why don't you investigate what is required to change the actual documentation? A getting started section could be added to the actual documentation. As a general rule, your efforts will have a much wider audience and will benefit more people if you direct them towards the actual distribution rather than putting them on a personal web page. I've been through the existing Cygwin docs. I don't see anything specifically answering this need. Huh? Addressing what need? A guide to legacy MS Windows-centric users for using the Cygwin environment, as opposed to installation or programmers guides (both exist for Cygwin), or general Unix quickstart guides (covered elsewhere). Did I say that there wasn't a need to address? Is this really hard to understand? Arguments are two doors down the hall. Informed discussion is what I'm after here. If you want people to benefit from your work, you try to get said work into the main cygwin web site and cygwin distribution. Suggestion: write you response after reading the entire message you're replying too, and remove extraneous argumentative bits contradicted subsequently, such as this one. The page isn't a personal web page. IWeThey is a group of tech professionals who've been loosely associated for over five years, and have run a number of web and other Internet-based services for much of this time. I've got a big hand in the TWiki. It's not by any means limited to me alone, only my product. As far as the cygwin project is concerned, it is a personal web page. It is not located on the cygwin site. It is not incorporated with the rest of the documentation. The fact that there is a group of people associated with your effort is irrelevant. Your skill in cutting off your nose to spite your face is admirable. If you've viewed the site, rather than simply engaged in criticism to someone for attempting to develop somethin useful, you'll note that use of contents is permitted, with attribution and a copy of the copyright notice. I've already had docs developed at the site incorporated into several other documents, most notably the Debian installation instructions, based on my chroot install method. The document I'm developing presently is just that -- a document in development. When it's at a stage I feel it's suitable for inclusion in the core Cygwin docs, I'll contact whomever is appropriate and y'all can cleave off a snapshot. I'll likely continue to use the TWiki as a development tool however, for extending this and related docs. Ok. This is not what you said at first. If you are willing to do some work to get this into the cygwin documentation, it will be appreciated. How charmingly gracious of you. If you are expecting that you can just say It's over there take it or leave it then I suspect that this will always exist on a non-cygwin-project web site and we'll be seeing a lot of I followed the directions over at... followed by The ... site is not affiliated with the cygwin project. We take no responsibility for the information there. If you have questions please contact the people at ... directly. Fair enough. However there are external docs available for Cygwin and numerous other free software projects at various points on the Web. In the case of Cygwin, I'll not particularly Mike Erdely's sshd-on-Cygwin documentation at http://tech.erdelynet.com/cygwin-sshd.html which is de-facto authoritative on the topic. You'd best deal with the fact that good docs will emerge at various points, and do what you can to avail yourself and/or the Cygwin project of them. I'd further recommend you refresh yourself on beggers, choosers, gifts offered, reading with comprehension, and demonstrating a modicum of appreciation. Peace. -- Karsten M. Self [EMAIL PROTECTED]http://kmself.home.netcom.com/ What Part of Gestalt don't you understand? Keep software free. Oppose the CBDTPA. Kill S.2048 dead. http://www.eff.org/alerts/20020322_eff_cbdtpa_alert.html pgp0.pgp Description: PGP signature
Re: About the 'su' command
Is this, or could this be made, part of the standard Cygwin docs and/or FAQ? Very nice explanation, Bill. Peace. on Wed, Jun 18, 2003 at 08:51:24AM -0400, Bill C. Riemers ([EMAIL PROTECTED]) wrote: The second says the command wont work unless I have appropriate privileges. Do you know someone on an XP station that has more powers than the Administrator or an Administrators member ? On most Unix systems, if you create a user with UID 65535 you will find that user is unable to run 'suid' commands including 'su'. This is result of 65535 mapping to -1 as a short, and -1 having special meaning. For awhile there was a trend to make the nobody user 65535. But then with the dawn of the web, programmers started wanting to make SUID cgi-bin scripts, while still using nobody as the default user for web connections. As such, the practice using 65535 for nobody has for the most part been abandoned in the Unix world. However, someone at Microsoft must have thought this was an extremely good idea. And why just have one account which is not allowed to SUID? So instead, Microsoft wrote XP so any account != UID 18 is prohibited from SUID. (OK. I over simplified, you can actually grant other accounts privilege to SUID on XP professional...) At first thought, the idea of restricting SUID to SYSTEM seems to give XP much stronger security than most unix systems. Until, you stop and consider, if only SYSTEM can SUID, and I can't login as SYSTEM, how does anything ever get installed to run under SYSTEM? It turns out SYSTEM is the account used for running services. Anyone with Administrators privilege can add a new service. Consequently, all Administrators can run any program they like as SYSTEM, including of course 'su'. So, you ask, if it is so easy for Administrator to run a process as SYSTEM, why doesn't 'su' use this trick? Quite simple. You can not change an existing process to SYSTEM privileges, nor can you do a direct exec() so you can pass your open file descriptors and environment to the new process. Consequently, you would find that if su used this trick your process would be running under a new TTY without access to existing file descriptors. So a command like, 'su root -c bar.sh /tmp/foo' would not work as expected. Now you ask, Well then, why can ssh do pipes. Very simple, 'ssh' sticks around after starting the child process starts passing data from open file descriptors though sockets. Finally you ask, If ssh can do that, why doesn't su? Simple. Why rewrite 'su' to do those types of tricks, when 'ssh' already exists? Bill -- 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/ -- Karsten M. Self [EMAIL PROTECTED]http://kmself.home.netcom.com/ What Part of Gestalt don't you understand? Spread the real scoop on Xenu and The Church of Scientology, link a href=http://xenu.org/;;Scientology/a on your website. pgp0.pgp Description: PGP signature
Re: newbie shell-users howto, guide, cheatsheet, or reference?
On Mon, Jun 30, 2003 at 12:32:55AM +0100, Karsten M. Self wrote: I've been through the existing Cygwin docs. I don't see anything specifically answering this need. Huh? Addressing what need? A guide to legacy MS Windows-centric users for using the Cygwin environment, as opposed to installation or programmers guides (both exist for Cygwin), or general Unix quickstart guides (covered elsewhere). Did I say that there wasn't a need to address? Is this really hard to understand? Arguments are two doors down the hall. Informed discussion is what I'm after here. Let's get this straight. Your intent was clear. I was addressing the fact that you were apparently starting a separate effort divorced from cygwin documentation. I never said or implied that the effort wasn't needed. I was trying to convince you to change existing cygwin documentation rather than starting your own separate effort. I don't see any need to keep repeating this fact. I'm sorry that you took my suggestion as an attack. FWIW, the situation with separate ssh documentation on Michael Erdeley's site is precisely what I was trying to avoid. This is why I provided an account on sources.redhat.com to Michael Erdeley so that he could modify the cygwin documentation/web site. That never happened but I still believe that putting important documentation at the project web site makes sense and directly contributing efforts to the project rather than to an offshoot is more profitable for the community. 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/
~^Z hangs ssh
Hello, I'm finding that ~^Z hangs the cygwin session rather than suspending my connection. I'm using cygwin to ssh into a solaris box. I've confirmed that suspension works properly when using ssh from sun box to sun box. Can't find any mention of this problem in the mailing list or Google. Does anyone else have this problem, or a fix? Fred -- Fred Ma, [EMAIL PROTECTED] Carleton University, Dept. of Electronics 1125 Colonel By Drive, Ottawa, Ontario Canada, K1S 5B6 -- 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: newbie shell-users howto, guide, cheatsheet, or reference?
On Mon, Jun 30, 2003 at 12:32:55AM +0100, Karsten M. Self wrote: I've been through the existing Cygwin docs. I don't see anything specifically answering this need. Huh? Addressing what need? A guide to legacy MS Windows-centric users for using the Cygwin environment, as opposed to installation or programmers guides (both exist for Cygwin), or general Unix quickstart guides (covered elsewhere). Did I say that there wasn't a need to address? Is this really hard to understand? Arguments are two doors down the hall. Informed discussion is what I'm after here. Let's get this straight. Your intent was clear. I was addressing the fact that you were apparently starting a separate effort divorced from cygwin documentation. I never said or implied that the effort wasn't needed. I was trying to convince you to change existing cygwin documentation rather than starting your own separate effort. Is this really hard to understand? Let's get this straight. Your intent was clear. You were yet again trying to be a jerk when it was completely and utterly unwarranted, and completely contrary to convincing anybody of doing anything for the Cygwin project. I don't see any need to keep repeating this fact. Did anybody say you need to keep repeating this fact? Is this really hard to understand? Oh wait, that's your line. I'm sorry that you took my suggestion as an attack. Chris, maybe if you didn't phrase your suggestions in the form of an attack people wouldn't take them that way. Is this really hard to understand? No personal emails please, lets throw our tantrums in public. -- Gary R. Van Sickle Brewer. Patriot. -- 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/
ls.exe slow down in cygwin 1.3.13 (a followup from the ls problem thread last november 2002)
Good Day Cygwineers (cygwin engineers), Last November 2002, I've upgraded cygwin and encountered a variation in the behaviour of ls. ls, when invoked as ls -l takes a bit longer to execute than the previous cygwin version. (I've attached the output of cygehck.) I haven't upgraded cygwin since November 2002 last year since I'm content with my installation now. The current variation in the behaviour of ls is not really a problem but I'd be glad if I could let it behave as it used to. I've posted the this observation last year in the list (under the thread ls -problem http://cygwin.com/ml/cygwin/2002-11/msg00921.html) and I thank everyone for their replies. Sorry if I just did a follow-up now (after 6 months) since I didn't have time to worry about my cygwin setup several days after I posted my observation. After some days of doing some research on what could be the solution to make ls behave as it used to, I finally said I'd just be content with the way it is. But now that I've got time to answer all the replies, I hope we could find a solution to the issue. I don't plan to upgrade my cygwin installation since it behaves very well and my current needs do not demand that I upgrade cygwin yet. Here's the gist of the problem: Whenever ls is invoked as ls -l, the output takes somewhat longer. I tried timing the output and here are the results: I'm working on my ~/foo directory. The directory contains 2 items: bar and strace.txt. bar is an empty directory and strace.txt is a regular text file. case 1) ls invoked plainly [EMAIL PROTECTED] ~/foo $ time ls bar strace.txt real0m0.028s user0m0.030s sys 0m0.015s case 2) ls is invoked as ls -l [EMAIL PROTECTED] ~/foo $ time ls -l total 49 drwxr-xr-x2 fcarlo None0 Jun 30 11:20 bar -rw-r--r--1 fcarlo None49394 Jun 30 11:08 strace.txt real0m1.924s user0m0.030s sys 0m0.046s I've tried repeating the invocation of ls -l in the hope that the list would be cached. After invoking it several times, there is no significant change in the time it takes to execute. I've tried stracing the output of ls -l and I've attached the output of strace too. An observation on the output of strace is that the delay starts when line 442 is printed. Line 442 of the strace output is: 104 1970355 [main] ls 2012 _open: -1 = open (/usr/local/etc/zoneinfo/posixrules, 0x1) I'm wondering what this zoneinfo/posixrules is. The file does not exist in my installation. Here are my responses to the replies by the gurus: Reply to Igor: It would have been more helpful if you had provided your cygwin version, but even without it I could venture a guess... The latest versions of cygwin have ntsec on by default, and doing 'ls -l' will result in the user lookup in the /etc/passwd (and /etc/group) file. An easy way to test that is to time 'ls -ln' and see if it's faster. Another test would be to *temporarily* turn off ntsec (by adding nontsec to your CYGWIN environment variable and reloading cygwin1.dll by exiting all running cygwin processes). I say temporarily because ntsec is actually a very useful feature to have on, and this is suggested only as a means to find out whether it's the culprit. You can restore the state by either changing nontsec to ntsec, or leaving it off altogether, as it's the default now, and reloading cygwin1.dll again. - Carlo Florendo Astra Philippines, Inc. URL:: www.astra.ph www.astra.co.jp ** Program name: F:\cygwin\bin\ls.exe (2012) App version: 1001.8, api: 0.34 DLL version: 1003.13, api: 0.62 DLL build:2002-10-13 23:15 OS version: Windows NT-5.0 Date/Time:2003-06-30 11:07:07 ** 9672103 [main] ls 2012 environ_init: 0xA010430: !C:=C:\ 1902293 [main] ls 2012 environ_init: 0xA010440: ALLUSERSPROFILE=C:\Documents and Settings\All Users 1692462 [main] ls 2012 environ_init: 0xA010478: APPDATA=C:\Documents and Settings\fcarlo\Application Data 1762638 [main] ls 2012 environ_init: 0xA0104B8: BASH_ENV=/etc/bashrc 1682806 [main] ls 2012 environ_init: 0xA0104D8: CLASSPATH=D:\Exceed.nt\hcljrcsv.jar;D:\Exceed.nt\hcljrcsv.jar;; 1662972 [main] ls 2012 environ_init: 0xA010520: COLORFGBG=15;default;0 1653137 [main] ls 2012 environ_init: 0xA010540: COLORTERM=rxvt-xpm 1673304 [main] ls 2012 environ_init: 0xA010558: COMMONPROGRAMFILES=C:\Program Files\Common Files 1713475 [main] ls 2012 environ_init: 0xA010590: COMPUTERNAME=THORIN 1633638 [main] ls 2012 environ_init: 0xA0105A8: COMSPEC=C:\WINNT\system32\cmd.exe 1713809 [main] ls 2012 parse_options: ntsec 0 2224031 [main] ls 2012 parse_options: returning 884119 [main] ls 2012 environ_init: 0xA0105D0: CYGWIN=nontsec 1654284 [main] ls 2012 environ_init: 0xA0105F8: DISPLAY=:0 2594543 [main] ls 2012 environ_init:
