Re: [RFC] SWIG package
On Thu, Apr 18, 2002 at 03:06:03PM -0400, Gerald S. Williams wrote: I'm not familiar with the netiquette here. Should this actually be an RFP or ITP? Anyway, I'd like to volunteer to maintain a SWIG package for Cygwin. Proposed setup.hint: --- category: Devel requires: cygwin sdesc: Simplified Wrapper Interface Generator ldesc: Simplified Wrapper Interface Generator. Generates wrappers for C/C++ modules, allowing them to be accessed from a variety of scripting languages. See http://www.swig.org for details. I'm missing links to the binary and source package... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
RE: FW: libtool devel package still dll crippled.
1. When someone build a shared lib on linux and uses a static lib, are the symbols of the static lib automatically exported ? Yes, using a static lib is no different than compiling that code directly into your codebase. Thats the behavior we have on cygwin, isn't it 2a. If yes, and if someone build a second dll with the same static lib, the symbols of the static libs are in both shared lib defined. Then if someone uses these two shared libs to build for example an application, ld fails with duplicated symbol errors. How does ld prevent this ? ld checks the symbols in the shared libs during compile time to see if it can resolve all symbols and appearantly also detects duplicated symbols. On Linux it is not necassery impossible to have two libs that define the same symbols. E.g. this feature can be used to override the malloc implementation of libc. Of course when this happens inadvertently it can lead to unexpected behaviour/crashes. ELF (The linking format used on Linux) has rather complex rules for determining which symbol should be used if it is defined multiple times. It also distinguishes between weak and strong symbols. It might be that it is only possible to override weak-symbols and that multiple strong-symbols result in link-errors. Does the cygwin ld has some similar rules ?
Re: When to release a threaded cygwin Python?
On Fri, Apr 19, 2002 at 07:44:17AM -0400, Jason Tishler wrote: Chris, On Fri, Mar 29, 2002 at 12:44:18PM -0500, Christopher Faylor wrote: On Fri, Mar 29, 2002 at 08:03:55AM -0500, Jason Tishler wrote: Here's the deal. Although a threaded Cygwin Python runs just fine under Cygwin 1.3.10, one cannot build one themselves without the following patch to sys/features.h: http://sources.redhat.com/ml/newlib/2002/msg00122.html So, should I hold off releasing a new Python until 1.3.11? Yes. I'll release 1.3.11 when Corinna comes back from vacation. Is Corinna back from vacation? :,) Physically or psychically? ;-) Corinna
RE: strange source packaging?
-Original Message- From: Earnie Boyd [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 3:13 AM I'll add another penny to make it 2c. I agree with Chris that I'd rather already have the patch applied. Why? If it's for ease of use, then fine - I agree that what the user receives should be patched. However that is somewhat orthogonal to how the download is accomplished. I differences from pristine supplied would be nice but if I really care I would go and find the originals. That's not actually the point. The point is that with some minor setup.exe tweaking, the source download can be done it two parts: 'pristine' + (patch[es] scripts). Then when a local adjustment is made, but the upstream hasn't released a new version, users can get the new source trivially - setup should be smart enough to see the pristine tarball in the /usr/src (or wherever) directory and just download the appropriate patch set. Rob
RE: strange source packaging?
-Original Message- From: Charles Wilson [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 12:44 AM of the antecedent project. There is no way, given just gcc-2.95.3-5-src.tar.bz2, to revert to the 'original' source -- short of also downloading the 2.95.3 source from www.gcc.org, unpacking both, and doing 'diff -r cygwin-version-of-gcc gnu-version-of-gcc'. And the GPL requires us to document the changes made - if we have the patch pre-applied, with no reverse patch, then this isn't the case. Asking folk to go elsewhere to get that 'pristine' source puts the onus on the upstream to make that available, which we can't do - for the same reason that folk that ship cygwin1.dll need to host their own copy of the source. Rob
Re: strange source packaging?
Robert Collins wrote: And the GPL requires us to document the changes made - if we have the patch pre-applied, with no reverse patch, then this isn't the case. Asking folk to go elsewhere to get that 'pristine' source puts the onus on the upstream to make that available, which we can't do - for the same reason that folk that ship cygwin1.dll need to host their own copy of the source. At the risk of wading into yet another GPL argument -- I don't think the GPL requires documentation of the entire provenance of changes relative to some external source; it's just the polite thing to do. All the GPL requires is that you distribute THE source that YOU used to build THE binary YOU distribute. That's it. --Chuck
RE: strange source packaging?
-Original Message- From: Charles Wilson [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 10:57 PM To: Robert Collins Cc: Corinna Vinschen Subject: Re: strange source packaging? Robert Collins wrote: And the GPL requires us to document the changes made - if we have the patch pre-applied, with no reverse patch, then this isn't the case. Asking folk to go elsewhere to get that 'pristine' source puts the onus on the upstream to make that available, which we can't do - for the same reason that folk that ship cygwin1.dll need to host their own copy of the source. At the risk of wading into yet another GPL argument -- I don't think the GPL requires documentation of the entire provenance of changes relative to some external source; it's just the polite thing to do. Section 2a is pretty clear. Rob
Re: strange source packaging?
Charles Wilson wrote: Robert Collins wrote: And the GPL requires us to document the changes made - if we have the patch pre-applied, with no reverse patch, then this isn't the case. Asking folk to go elsewhere to get that 'pristine' source puts the onus on the upstream to make that available, which we can't do - for the same reason that folk that ship cygwin1.dll need to host their own copy of the source. At the risk of wading into yet another GPL argument -- I don't think the GPL requires documentation of the entire provenance of changes relative to some external source; it's just the polite thing to do. All the GPL requires is that you distribute THE source that YOU used to build THE binary YOU distribute. That's it. Section 2.a You must cause the modified files to carry prominent notices stating that you chaned the files and the date of any change. /Section 2.a A differences file alone doesn't accomplish. You must state in the file header (a prominent place of notice) that you changed the file. Now how many of us do that? Instead we use a ChangeLog to note the changes to the files. The GPL itself doesn't give exception for this method. However, since the Copyright holder, Redhat, uses the ChangeLog method for file change notification then it can be argued that the Copyright holder gave the exception to the license so it can continue without change as far as Cygwin is concerned. But the FSF is the copyright holder the most of the other packages we distribute, have the changed files been given appropriate prominent notice? Back to the subject at hand, source packaging and the con to Robert's argument. I can in my wisdom download the individual binary and accompaning source. At that point I should be able to rebuild an exacting duplicate from the source package with supplied scripts found within the source package (autoconfiguration). Therefore having setup.exe perform any patches by downloading only the patch doesn't meet the criteria layed out by the GPL. Nice thought, but not workable within the wording of the GPL. Section 3, para. 5 These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. /Section 3, para 5 Earnie. _ Do You Yahoo!? Get your free yahoo.com address at http://mail.yahoo.com
RE: [RFC] SWIG package
That's because I haven't built them yet (actually I have, but I want to do a clean rebuild with the latest official SWIG, which I'll probably do early next week). I interpreted the instructions at http://cygwin.com/setup.html#submitting as indicating that I should first propose the package, in case there's some reason why the package isn't already available. I don't currently have a public FTP site set up. In the past, I've posted things to world.std.com (now ftp://ftp.std.com), although the public uploads section seems to have gone away, so I'll have to find another or break down and set up the web page my dial-up ISP supposedly provides. (Unfortunately, that will be going away shortly when I finally get my cable modem hookup.) :-) -Jerry -O Gerald S. Williams, 55A-134A-E : mailto:[EMAIL PROTECTED] O- -O AGERE SYSTEMS, 6755 SNOWDRIFT RD : office:610-712-8661 O- -O ALLENTOWN, PA, USA 18106-9353: mobile:908-672-7592 O- -Original Message- From: Corinna Vinschen [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 3:08 AM To: [EMAIL PROTECTED] Subject: Re: [RFC] SWIG package On Thu, Apr 18, 2002 at 03:06:03PM -0400, Gerald S. Williams wrote: I'm not familiar with the netiquette here. Should this actually be an RFP or ITP? Anyway, I'd like to volunteer to maintain a SWIG package for Cygwin. Proposed setup.hint: --- category: Devel requires: cygwin sdesc: Simplified Wrapper Interface Generator ldesc: Simplified Wrapper Interface Generator. Generates wrappers for C/C++ modules, allowing them to be accessed from a variety of scripting languages. See http://www.swig.org for details. I'm missing links to the binary and source package... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: [RFC] SWIG package
On Fri, Apr 19, 2002 at 01:56:39PM -0400, Gerald S. Williams wrote: That's because I haven't built them yet (actually I have, but I want to do a clean rebuild with the latest official SWIG, which I'll probably do early next week). I interpreted the instructions at http://cygwin.com/setup.html#submitting as indicating that I should first propose the package, in case there's some reason why the package isn't already available. I don't currently have a public FTP site set up. In the past, I've posted things to world.std.com (now ftp://ftp.std.com), although the public uploads section seems to have gone away, so I'll have to find another or break down and set up the web page my dial-up ISP supposedly provides. (Unfortunately, that will be going away shortly when I finally get my cable modem hookup.) :-) Do as you like but we need a link to take a look if you did pack it correctly (well, sort of, see the latest discussion about source packaging...) and all that. Don't panic, next week is early enough ;-) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developermailto:[EMAIL PROTECTED] Red Hat, Inc.
Re: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
On Fri, Apr 19, 2002 at 12:52:27PM -0400, Christopher Faylor wrote: On Fri, Apr 19, 2002 at 01:24:48AM -0400, Harold Hunt wrote: Chris, Shall we add this to the cygwin distro or are we still waiting for some postinstall shell script work? These will forever be known as Harold's Famous Last Words: Sure Chris, why not? Go ahead and add the packages to the distro. Be aware, I just updated XFree86-xserv to 4.2.0-2, so you'll need to grab the latest packages off of ftp://huntharo-4.user.msu.edu/pub/cygwin/ That's all for now. I can't wait to see how many people use Cygwin/XFree86 now! Ditto. Hope you're ready for this. It's up there. Should be on mirrors shortly. One thing I just noticed, though (by looking at http://cygwin.com/packages/), was that the source tar.bz2 files don't seem to be part of this. There should probably be fewer source tar balls than binary but they should be part of the distribution, right? If not, we'll inevitably get questions. cgf
RE: strange source packaging?
-Original Message- From: Earnie Boyd [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 12:20 AM Section 2.a You must cause the modified files to carry prominent notices stating that you chaned the files and the date of any change. /Section 2.a A differences file alone doesn't accomplish. You must state in the file header (a prominent place of notice) that you changed the file. Given the definition of a prominent place of notice, it can be argued that a difference file is just that. It's prominent and states the exact changes made - in both human and computer readable form no less. Back to the subject at hand, source packaging and the con to Robert's argument. I can in my wisdom download the individual binary and accompaning source. At that point I should be able to rebuild an exacting duplicate from the source package with supplied scripts found within the source package Exactly. 'source package' here can mean more than one file. There is no requirement in the GPL that the source be provided as a single entity, just that it be provided in it's entirety. So I don't understand your reasoning for why a pristine source + patches + cygwin build script does not meet the criteria. Certianly debian + *BSD ports systems seem to find it feasible. Section 3, para. 5 These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. /Section 3, para 5 Yup. That's what we are conforming with. Rob
Re: attn cgf - single build integration
On Sat, Apr 20, 2002 at 09:49:34AM +1000, Robert Collins wrote: Chris, I'm approaching a point with libgetopt++ that I'll want to roll it into setup. This will (obviously) affect the single-build procress, so I'm hoping that you can confirm or suggest alterations to my plan: I think that as a general purpose library, it should sit at winsup/libgetopt++ or even a level above. However the binary linked into setup.exe needs to be built knowing about setup's String class (as opposed to the C++ standard basic_string). So here's my idea: we put the library at winsup/libgetopt++ we make a symlink in the source tree at cinstall/libgetopt++ to ../libgetopt++ During configure time setup sub-configures libgetopt++ as a static only library in cinstall/libgetopt++ In the future if any other programs want to start using it, we make winsup subconfigure winsup/libgetopt++. What do you think? I think that libgetopt++ probably belongs at the same level as winsup but there are some, er, political issues that need to be dealt with if that is the case. So, for now, I guess making it a winsup/cygwin sibling makes sense. Btw, if you want to set up a web page off the cygwin directory, that's ok, too. I don't think I could justify a new top-level web page given the fact that I've rejected some other attempts to start up new projects on sourceware due to resource limitations but adding it into the cygwin hierarchy should be ok. cgf
Re: cygwin/xfree86 setup.exe packages available for comments and testing
Harold Hunt [EMAIL PROTECTED] writes: Excellent idea. Now I just need someone to write that script. Shouldn't be too hard. Any takers? How about fontdir=/usr/X11R6/lib/X11/fonts wfontdir=`cygpath -w $fontdir` mount -bfs $wfontdir $fontdir 2 /dev/null || mount -bfu $wfontdir $fontdir IOW, create a system mount in binary mode on the font directory, disregarding any existing mount on the same place. If the user is not allowed to create a system mount, create a user mount instead. This would break when there already is a user mount in text mode. That seems pretty unlikely, though. so long, benny
RE: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
-Original Message- From: Harold Hunt [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 6:56 AM In a related question that has to do with my laziness, I need a way to tarball a CVS tree without including the CVS directories. I'm sure this can be done with a simple script, but I'm a programmer not a script writer. Anyone want to point me to an existing script that does this, or write one for me? Grab the -src for one of the packages that Chuck or I maintain - say libxslt. There is a tar command in the .sh that filters out various directories... I'm sure you can adapt it easily. Rob
Re: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
On Fri, Apr 19, 2002 at 04:55:57PM -0400, Harold Hunt wrote: The main problem with -src packages for us is that almost nothing will change after an XFree86 release except for the xc/programs/Xserver/hw/xwin directory, where I make modifications to the XWin server. So, what do I do for packaging? Which of the XFree86-* packages do I include source with? Do I include one huge tarball with everything and another small tarball that has just the hw/xwin directory so that it can be easily updated? I'm confused. I had the same thoughts and hoped you'd have a brilliant solution. :-) I didn't quite gather from the earlier discussions whether we can have a source package seperate from any binary packages. i.e., could we have XFree86-full-src without an associated binary package? Or would we have to make XFree86-base-src the package that contained the full source archive. Hmm. Yes. I think this would work. That might be the best solution. In fact, it may be a nice trend setter. In a related question that has to do with my laziness, I need a way to tarball a CVS tree without including the CVS directories. I'm sure this can be done with a simple script, but I'm a programmer not a script writer. Anyone want to point me to an existing script that does this, or write one for me? From my generate a package script: find $package_src/* -print -follow | egrep -v '\.cvsignore|\.bak$|\.orig$|~$|^.#|CVS|%redact|/tags$' | egrep -v $src_exclude | sort | tar -T - --no-recursion -cjf $tarstem-src.tar.bz2 cgf
Re: cygwin/xfree86 setup.exe packages available for comments and testing
On Fri, Apr 19, 2002 at 11:17:56PM +0200, Benjamin Riefenstahl wrote: Harold Hunt [EMAIL PROTECTED] writes: Excellent idea. Now I just need someone to write that script. Shouldn't be too hard. Any takers? How about fontdir=/usr/X11R6/lib/X11/fonts wfontdir=`cygpath -w $fontdir` mount -bfs $wfontdir $fontdir 2 /dev/null || mount -bfu $wfontdir $fontdir IOW, create a system mount in binary mode on the font directory, disregarding any existing mount on the same place. If the user is not allowed to create a system mount, create a user mount instead. This would break when there already is a user mount in text mode. That seems pretty unlikely, though. This looks pretty good to me. How about something like this, though: fontdir=/usr/X11R6/lib/X11/fonts wfontdir=`cygpath -w $fontdir` umount -u $fontdir 2/dev/null mount -bfs $wfontdir $fontdir 2 /dev/null || mount -bfu $wfontdir $fontdir Just to ensure that there is no user mount? Btw, I like the use of the fontdir variable in this context. It's a little thing, but... cgf
RFP: boost libraries
Is there anyone on this list interested in providing a distribution of some/all of the boost C+ libraries? Rob
RE: attn cgf - single build integration
-Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 10:13 AM Btw, if you want to set up a web page off the cygwin directory, that's ok, too. I don't think I could justify a new top-level web page given the fact that I've rejected some other attempts to start up new projects on sourceware due to resource limitations but adding it into the cygwin hierarchy should be ok. Is there a cygwin-apps hierarchy? I note that there is a cygwin-apps/htdocs dir, but I don't know where files put there appear on the website. Having http://cygwin-apps.cygwin.com would be quite neat, or http://www.cygwin.com/cygwin-apps. This is for more than just this library (obviously). Rob
Re: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
Robert Collins wrote: we have to make XFree86-base-src the package that contained the full source archive. Hmm. Yes. I think this would work. That might be the best solution. In fact, it may be a nice trend setter. I think setup.exe needs a little work before doing this, but it's a good direction. (i.e. setup.exe should have a view to only show src packages, and a view to only show binaries - to avoid confusing folk). (Think apt-get source vs apt-get install). How about my 'external-src: ' idea? setup hint for XFree86-[anything but base]-... external-src: XFree86-base setup hint for XFree86-base- no external-src tag and both upset and setup will understand this and do the right thing: upset needs to, for those pkgs with an external-src in their setup hint, find the -src tarball for the indicated package, whose VER-REL string matches the package-under-consideration, and put THAT into setup.hint, so (for the fonts package) you get install: release/xfree/xfree86-fonts/XFree86-fonts-4.2.0-2.tar.bz2 source: release/xfree/xfree86-base/XFree86-base-4.2.0-2-src.tar.bz2 [prev] install: release/xfree/xfree86-fonts/XFree86-fonts-4.2.0-1.tar.bz2 source: release/xfree/xfree86-base/XFree86-base-4.2.0-1-src.tar.bz2 Also, setup must do the following (even without new 'views' and whatnot) 1) all XFree86-...- indicate that src is available (that is, 'presence of a -src tarball' == 'no -src tarball but external-src: marker in setup.hint' 2) clicking on any one (or multiple) of the 'src' checkboxes in setup will trigger a download (and only one download) of the actual XFree86-base-4.2.0-1-src.tar.bz2 package - Later, we can get even fancier, and allow the specification of multiple -src packages...then the monolithic 'XFree86-base-4.2.0-1-src.tar.bz2' can be split into the stuff that cygwin-xfree doesn't change and the stuff that changes frequently (e.g. .../hw/xwin). e.g. setup hint for XFree86-[anything but base]-... external-src: XFree86-base setup hint for XFree86-base- no external-src tag extra-src: XFree86-base2 in release/xfree/xfree86-base/ XFree86-base-4.2.0-1.tar.bz2 XFree86-base-4.2.0-1-src.tar.bz2 XFree86-base2-4.2.0-1-src.tar.bz2 But that (or something like it) can be later - --Chuck P.S. Chris, where'd upset go? the current version used to be in htdocs, but it's gone now. AND, the old version which lived in cinstall/temp, is still there -- and you said you were going to remove it. Did you remove the wrong one?
RE: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
-Original Message- From: Charles Wilson [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 12:59 PM Also, setup must do the following (even without new 'views' and whatnot) Setup should already do that, why not make a test setup.ini and see what happens :]. It's all data driven and there is no requirement for -src packages to follow the same name as the base. Rob
Re: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
On Fri, Apr 19, 2002 at 10:59:29PM -0400, Charles Wilson wrote: P.S. Chris, where'd upset go? the current version used to be in htdocs, but it's gone now. AND, the old version which lived in cinstall/temp, is still there -- and you said you were going to remove it. http://www.cygwin.com/ml/cygwin-apps/2002-02/msg00028.html cinstall/temp is an empty directory. Did you remove the wrong one? Nope. upset2 is gone now, though. It is now 'upset'. cgf
Re: attn cgf - single build integration
On Sat, Apr 20, 2002 at 01:20:03PM +1000, Robert Collins wrote: -Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 10:13 AM Btw, if you want to set up a web page off the cygwin directory, that's ok, too. I don't think I could justify a new top-level web page given the fact that I've rejected some other attempts to start up new projects on sourceware due to resource limitations but adding it into the cygwin hierarchy should be ok. Is there a cygwin-apps hierarchy? I note that there is a cygwin-apps/htdocs dir, but I don't know where files put there appear on the website. Having http://cygwin-apps.cygwin.com would be quite neat, or http://www.cygwin.com/cygwin-apps. This is for more than just this library (obviously). There is nothing there now but apparently I set up the system so that if you check in an index.html, etc., it will show up at http://sources.redhat.com/cygwin-apps/ . If you want to do that, go ahead. I'm not going to be adding another virtual domain or host anytime soon. cgf
key repeats when other window pops up
From the keyboard testing department, April 19 2002. Today we noticed the following behaviour from XWin: Whilst typing merrily away in an xterm-client, all of a sudden a message window popped up, as message windows are wont to do. The xterm-client lost control, and did not notice that the end user had released the key he was pressing in xterm, in this case, the a-key. Under the impression that the end-user was still holding the a-key, the xterm-client continued displaying a-characters, and would still be doing so, had he not been stopped by the end-user himself. Please ignore this message if the behaviour described above is not, as is often much to hastily concluded, a bug, but rather a feature to occupy the clients while the end user is being distracted. With the utmost respect, we remain, yours faithfully, etc. etc. === This email is confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. You are explicitly requested to notify the sender of this email that the intended recipient was not reached.
Re: XFree86 4.2.0 under Cygwin on Win98 w/ i810 won't display CDEfro m HPUX
On Mon, 15 Apr 2002, Michael Reaser wrote: XWin -query aa.bb.cc.dd -fp tcp/aa.bb.cc.dd:7000 Fatal server error: XDMCP fatal error: Session failed Session 6 failed for display 0.0.0.0:0: Cannot open display you need the -from parameter. XWin -query aa.bb.cc.dd -from localip (not 127.0.0.1) bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723 phone: +49 3725 349 80 80 mobile: +49 172 7854017 4. Chemnitzer Linux-Tag http://www.tu-chemnitz.de/linux/tag/lt4
New Xfree Cygwin Package...
I've been watching with interest all this work on packaging the Xfree/XWin stuff. Now that it appears to be a reality, what do you recommend for those of us who already have Xfree installed via the old method? I for one would like to move over the the Cygwin package method becaused I like being able to into the Cygwin setup program to see what's changed. However, I'm a little hesitant to go installing the new packages until I understand what the impact on my existing setup might be. _ Send and receive Hotmail on your mobile device: http://mobile.msn.com
Re: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
On Fri, Apr 19, 2002 at 12:52:27PM -0400, Christopher Faylor wrote: On Fri, Apr 19, 2002 at 01:24:48AM -0400, Harold Hunt wrote: Chris, Shall we add this to the cygwin distro or are we still waiting for some postinstall shell script work? These will forever be known as Harold's Famous Last Words: Sure Chris, why not? Go ahead and add the packages to the distro. Be aware, I just updated XFree86-xserv to 4.2.0-2, so you'll need to grab the latest packages off of ftp://huntharo-4.user.msu.edu/pub/cygwin/ That's all for now. I can't wait to see how many people use Cygwin/XFree86 now! Ditto. Hope you're ready for this. It's up there. Should be on mirrors shortly. One thing I just noticed, though (by looking at http://cygwin.com/packages/), was that the source tar.bz2 files don't seem to be part of this. There should probably be fewer source tar balls than binary but they should be part of the distribution, right? If not, we'll inevitably get questions. cgf
RE: key repeats when other window pops up
Gerard, Yes, we have been aware of that behavior for some time now. In fact, it is listed as the first item on the Development To-Do List: http://xfree86.cygwin.com/devel/todo.html We have a patch for this problem. However, in the course of applying this patch I realized that there is a second problem that was originally thought to be a bug of the patch that fixes your problem. This other bug is that when Cygwin/XFree86 gets bogged down in processing, such as when running the test Native GDI server (which is really slow right now because it does every single graphics operations as a set of thousands of simple line draws). For example: 1) Open the test Cygwin/XFree86 server in Native GDI mode. (you can't do this unless you build from CVS) 2) Run 'xdpyinfo', 'ls' on /usr/X11R6/bin, or some other program that will fill an xterm's scroll buffer with lines of text. Notice that there is an extra blank command line after the output. This is because somewhere along the way the 'enter' key gets fired twice. 3) Scroll to the top of the xterm scroll buffer (this will take seconds). 4) Type 'exit' or any other word, but do not press enter. This will cause xterm to scroll down to the command line. (this will take seconds). 5) Notice that 'exit' comes out as 'eexit'. No, this is not because the 'e' that you typed is being echoed late. This is an actual duplicate key event, because if you press 'enter' xterm will report that 'eexit' cannot be found. I did much investigating into this problem using printf's sprinkled throughout the code. I was able to figure out that it wasn't the hw/xwin code that processes Windows keyboard messages that was duplicating events. Rather, there is a procedure deep in the server that seems to be duplicating the events. I built a debug version of the tree and tried to debug it but gdb kept crashing and I ran out of time. To make a long story short, after all that excitement I kinda put off those patches for awhile. I should go ahead and apply them since they solve a very real and current problem, and I have determined that the patch is not the cause of the mystery key repeat problem. I hope that muddies things up for you :) Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Pille Geert (bkarnd) Sent: Friday, April 19, 2002 10:33 AM To: '[EMAIL PROTECTED]' Subject: key repeats when other window pops up From the keyboard testing department, April 19 2002. Today we noticed the following behaviour from XWin: Whilst typing merrily away in an xterm-client, all of a sudden a message window popped up, as message windows are wont to do. The xterm-client lost control, and did not notice that the end user had released the key he was pressing in xterm, in this case, the a-key. Under the impression that the end-user was still holding the a-key, the xterm-client continued displaying a-characters, and would still be doing so, had he not been stopped by the end-user himself. Please ignore this message if the behaviour described above is not, as is often much to hastily concluded, a bug, but rather a feature to occupy the clients while the end user is being distracted. With the utmost respect, we remain, yours faithfully, etc. etc. === This email is confidential and intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. You are explicitly requested to notify the sender of this email that the intended recipient was not reached.
qt 2.3.1 beta 1 release available
Hi all, the kde-cygwin team has released the qt 2.3.1 beta 1 release. This release is an update to the official qt 2.3.1 with all cygwin related patches from the 2.3.0 release applied. The most imported change is optimized qdir/qfile code, which speeds up qt file dialog displaying. You can found qt-cygwin under http://kde-cygwin.sf.net. Ralf
Re: cygwin/xfree86 setup.exe packages available for comments and testing
Harold Hunt [EMAIL PROTECTED] writes: Excellent idea. Now I just need someone to write that script. Shouldn't be too hard. Any takers? How about fontdir=/usr/X11R6/lib/X11/fonts wfontdir=`cygpath -w $fontdir` mount -bfs $wfontdir $fontdir 2 /dev/null || mount -bfu $wfontdir $fontdir IOW, create a system mount in binary mode on the font directory, disregarding any existing mount on the same place. If the user is not allowed to create a system mount, create a user mount instead. This would break when there already is a user mount in text mode. That seems pretty unlikely, though. so long, benny
RE: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
-Original Message- From: Harold Hunt [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 6:56 AM In a related question that has to do with my laziness, I need a way to tarball a CVS tree without including the CVS directories. I'm sure this can be done with a simple script, but I'm a programmer not a script writer. Anyone want to point me to an existing script that does this, or write one for me? Grab the -src for one of the packages that Chuck or I maintain - say libxslt. There is a tar command in the .sh that filters out various directories... I'm sure you can adapt it easily. Rob
RE: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
-Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 8:48 AM I didn't quite gather from the earlier discussions whether we can have a source package seperate from any binary packages. i.e., could we have XFree86-full-src without an associated binary package? Or would we have to make XFree86-base-src the package that contained the full source archive. Hmm. Yes. I think this would work. That might be the best solution. In fact, it may be a nice trend setter. I think setup.exe needs a little work before doing this, but it's a good direction. (i.e. setup.exe should have a view to only show src packages, and a view to only show binaries - to avoid confusing folk). (Think apt-get source vs apt-get install). Rob
Re: cygwin/xfree86 setup.exe packages available for comments and testing
On Fri, Apr 19, 2002 at 11:17:56PM +0200, Benjamin Riefenstahl wrote: Harold Hunt [EMAIL PROTECTED] writes: Excellent idea. Now I just need someone to write that script. Shouldn't be too hard. Any takers? How about fontdir=/usr/X11R6/lib/X11/fonts wfontdir=`cygpath -w $fontdir` mount -bfs $wfontdir $fontdir 2 /dev/null || mount -bfu $wfontdir $fontdir IOW, create a system mount in binary mode on the font directory, disregarding any existing mount on the same place. If the user is not allowed to create a system mount, create a user mount instead. This would break when there already is a user mount in text mode. That seems pretty unlikely, though. This looks pretty good to me. How about something like this, though: fontdir=/usr/X11R6/lib/X11/fonts wfontdir=`cygpath -w $fontdir` umount -u $fontdir 2/dev/null mount -bfs $wfontdir $fontdir 2 /dev/null || mount -bfu $wfontdir $fontdir Just to ensure that there is no user mount? Btw, I like the use of the fontdir variable in this context. It's a little thing, but... cgf
Send an announcement to cygwin-announce?
Harold, do you want to send an announcement to cygwin-announce? If so, I'd appreciate it if you'd pattern it on one of the announcements that you find in the cygwin-announce archives, e.g., see below. The important bit is to set Reply-To to cygwin-xfree and mention cygwin-xfree in the announcement. I'll set up a cygwin-xfree-announce in the next couple of days, too. Should there be a link to setup.exe on the Cygwin/XFree86 web page. cgf (who's so happy that this is part of the main installation now) From: Harold Hunt [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: New package: XFree86 4.2.0 Reply-To: [EMAIL PROTECTED] The XFree86 package developed by the Cygwin/XFree86 project is now part of the standard distribution. You can select it by clicking on the XFree86 portion of the package selection after clicking on the Install Cygwin Now! link at the main cygwin web page. Blah, blah. If you have questions or comments, please send them to the Cygwin mailing list at: [EMAIL PROTECTED] . I would appreciate it if you would use this mailing list rather than emailing me directly. If you want to make a point or ask a question, the cygwin-xfree mailing list is the appropriate place. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. I implore you to READ this information before sending email about how you tried everything to unsubscribe. In 100% of the cases where people were unable to unsubscribe, the problem was that they hadn't actually read and comprehended the unsubscribe instructions. If you need to unsubscribe from cygwin-announce or any other mailing list, reading the instructions at the above URL is guaranteed to provide you with the info that you need.
RE: xfree86 install makes wininit not working
Robert, Cygwin's setup.exe doesn't use wininit.ini, does it? I'm going to guess that the answer is something along the lines of no way in hell, but I figure I had better check with you. Harold -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Faylor Sent: Friday, April 19, 2002 10:04 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: xfree86 install makes wininit not working And here it begins... Cygwin/XFree86 has its own mailing list: [EMAIL PROTECTED] If you want help you should ask the experts. I've redirected this message there. cgf On Sat, Apr 20, 2002 at 03:59:32AM +0200, Sylvain Petreolle wrote: Hi, I wanted to update my existing Xfree86-4.2.0-1 installation. So i choose a default Xfree86 installation. All files downloaded correct, and i was told that everything was ok. But at reboot, a 65497 bytes wininit.ini wants to rename/rewrite 627 files, and no one is replaced (wininit.ini isn't even renamed to .bak) This damn thing makes windows write Please wait while updating your configuration files... every time I reboot if I don't rename the file. could the fact that wininit.ini is too big make it fail ? I'm running it under Windows Me.
RE: xfree86 install makes wininit not working
-Original Message- From: Harold Hunt [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 12:47 PM To: [EMAIL PROTECTED] Cc: Robert Collins Subject: RE: xfree86 install makes wininit not working Robert, Cygwin's setup.exe doesn't use wininit.ini, does it? I'm going to guess that the answer is something along the lines of no way in hell, but I figure I had better check with you. It does, via the proscribed windows API to perform copy-on-reboot for in-use files in win95. Windows is meant to perform the copies before loading the GUI, and then remove the ini entries after it does that. If I could get some details - the /var/log/setup.log and setup.log.full, and the machine layout (where windows cygwin etc are), and a copy of the ineffective wininit.ini, I will see what I can figure out. As to why this happened, I assume that the user was running X at the same time as installing it via setup.exe. Rob
RE: xfree86 install makes wininit not working
I realised the ini file was present in Sylvain's email. Sylvain - do the .NEW files exist? Are the paths correct? ROb
RE: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
-Original Message- From: Charles Wilson [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 12:59 PM Also, setup must do the following (even without new 'views' and whatnot) Setup should already do that, why not make a test setup.ini and see what happens :]. It's all data driven and there is no requirement for -src packages to follow the same name as the base. Rob
Re: [ANNOUNCEMENT] cygwin/xfree86 setup.exe packages available for comments and testing
On Fri, Apr 19, 2002 at 10:59:29PM -0400, Charles Wilson wrote: P.S. Chris, where'd upset go? the current version used to be in htdocs, but it's gone now. AND, the old version which lived in cinstall/temp, is still there -- and you said you were going to remove it. http://www.cygwin.com/ml/cygwin-apps/2002-02/msg00028.html cinstall/temp is an empty directory. Did you remove the wrong one? Nope. upset2 is gone now, though. It is now 'upset'. cgf
RE: xfree86 install makes wininit not working
It does, via the proscribed windows API to perform copy-on-reboot for in-use files in win95. Windows is meant to perform the copies before loading the GUI, and then remove the ini entries after it does that. Already know this (I develop for Wine Emulator :)) But that's ok to review point after point to see a failure somewhere. If I could get some details - the /var/log/setup.log and setup.log.full, and the machine layout (where windows cygwin etc are), and a copy of the ineffective wininit.ini, I will see what I can figure out. Ok, I attached them. cygcheck -s -r -v follows separately (Yahoo doesn't allow 3 attachments per message). As to why this happened, I assume that the user was running X at the same time as installing it via setup.exe. Rob I just updated Cygwin via typing http://www.cygwin.com/setup.exe in IE 6. Cygwin-X wasn't running at the time. Even Cygwin itself wasn't running. ___ Do You Yahoo!? -- Une adresse yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com setup.log.gz Description: setup.log.gz 2002/04/20 00:28:24 Starting cygwin install, version 2.194.2.24 2002/04/20 00:28:24 Current Directory: C:\Program Files\GOA 2002/04/20 00:28:24 Command line parameters 2002/04/20 00:28:24 0 - 'C:\WINDOWS\Temporary Internet Files\Content.IE5\KHQ7W5QN\setup[1].exe' 2002/04/20 00:28:24 1 parameters passed 2002/04/20 00:28:28 source: network install 2002/04/20 00:28:31 root: C:/cygwin binary user 2002/04/20 00:28:34 Ending cygwin install WININIT.INI.gz Description: WININIT.INI.gz
RE: xfree86 install makes wininit not working
As I wrote in last message, I attached output of cygcheck. ___ Do You Yahoo!? -- Une adresse yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com Cygwin Win95/NT Configuration Diagnostics Current System Time: Sat Apr 20 06:01:37 2002 Windows ME Ver 4.90 Build 3000 Path: . C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin c:\WINDOWS c:\WINDOWS\COMMAND SysDir: C:\WINDOWS\SYSTEM WinDir: C:\WINDOWS HOME = `C:\cygwin\home\Nom' MAKE_MODE = `unix' PWD = `/home/Nom' USER = `Nom' BLASTER = `A220 I5 D1 H7 P330 T6' CMDLINE = `bash --login -i' COMSPEC = `C:\WINDOWS\COMMAND.COM' MANPATH = `:/usr/ssl/man' OLDPWD = `/usr/bin' PROMPT = `$p$g' PS1 = `\[\033]0;\w\007 \033[32m\]\u@\h \[\033[33m\w\033[0m\] $ ' SBPCI = `C:\PROGRA~1\CREATIVE\AUDIO\DOSDRV' SHLVL = `1' TEMP = `c:\WINDOWS\TEMP' TERM = `cygwin' WINBOOTDIR = `C:\WINDOWS' WINDIR = `C:\WINDOWS' _ = `/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MenuOrder\Start Menu\Programs\Cygnus Solutions (default) = (unsupported type) HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 (default) = `/cygdrive' cygdrive flags = 0x0022 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/ (default) = `C:/cygwin' flags = 0x0002 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/bin (default) = `C:/cygwin/bin' flags = 0x0002 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2\/usr/lib (default) = `C:/cygwin/lib' flags = 0x0002 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2 HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options a: fd N/AN/A c: hd FAT32 10234Mb 67% CPUN DISQUE C d: hd FAT32 4994Mb 62% CPUN DISQUE D e: hd FAT32 4994Mb 50% CPUN DISQUE E f: cd CDFS 619Mb 100% UN Collect6 g: cd N/AN/A h: cd N/AN/A C:/cygwin / userbinmode C:/cygwin/bin /usr/bin userbinmode C:/cygwin/lib /usr/lib userbinmode . /cygdrive userbinmode,noumount Found: C:\cygwin\bin\bash.exe Found: C:\cygwin\bin\cat.exe Found: C:\cygwin\bin\cpp.exe Found: C:\cygwin\bin\find.exe Found: c:\WINDOWS\COMMAND\find.exe Warning: C:\cygwin\bin\find.exe hides c:\WINDOWS\COMMAND\find.exe Found: C:\cygwin\bin\gcc.exe Found: C:\cygwin\bin\gdb.exe Found: C:\cygwin\bin\ld.exe Found: C:\cygwin\bin\ls.exe Found: C:\cygwin\bin\make.exe Found: C:\cygwin\bin\sh.exe 45k 2001/04/25 C:\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0 cygform5.dll v0.0 ts=2001/4/25 7:28 26k 2001/04/25 C:\cygwin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0 cygmenu5.dll v0.0 ts=2001/4/25 7:27 156k 2001/04/25 C:\cygwin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0 cygncurses++5.dll v0.0 ts=2001/4/25 7:29 226k 2001/04/25 C:\cygwin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0 cygncurses5.dll v0.0 ts=2001/4/25 7:17 15k 2001/04/25 C:\cygwin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0 cygpanel5.dll v0.0 ts=2001/4/25 7:27 50k 2002/03/12 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0 cygz.dll v0.0 ts=2002/3/12 5:38 170k 2002/01/21 C:\cygwin\bin\cygpng2.dll - os=4.0 img=1.0 sys=4.0 cygpng2.dll v0.0 ts=2002/1/21 2:05 35k 2002/01/09 C:\cygwin\bin\cygform6.dll - os=4.0 img=1.0 sys=4.0 cygform6.dll v0.0 ts=2002/1/9 7:03 20k 2002/01/09 C:\cygwin\bin\cygmenu6.dll - os=4.0 img=1.0 sys=4.0 cygmenu6.dll v0.0 ts=2002/1/9 7:03 175k 2002/01/09 C:\cygwin\bin\cygncurses++6.dll - os=4.0 img=1.0 sys=4.0 cygncurses++6.dll v0.0 ts=2002/1/9 7:03 81k 2001/10/19 C:\cygwin\bin\cygitcl30.dll - os=4.0 img=1.0 sys=4.0 cygitcl30.dll v0.0 ts=2001/10/20 2:25 35k 2001/10/19 C:\cygwin\bin\cygitk30.dll - os=4.0 img=1.0 sys=4.0 cygitk30.dll v0.0 ts=2001/10/20 2:25 390k 2001/10/19 C:\cygwin\bin\cygtcl80.dll - os=4.0 img=1.0 sys=4.0 cygtcl80.dll v0.0 ts=2001/10/20 2:24 5k 2001/10/19 C:\cygwin\bin\cygtclpip80.dll - os=4.0 img=1.0 sys=4.0 10k 2001/10/19 C:\cygwin\bin\cygtclreg80.dll - os=4.0 img=1.0 sys=4.0 cygtclreg80.dll v0.0 ts=2001/10/20 2:24 623k 2001/10/19 C:\cygwin\bin\cygtk80.dll - os=4.0 img=1.0 sys=4.0 cygtk80.dll v0.0 ts=2001/10/20 2:25 19k 2002/02/20 C:\cygwin\bin\cyggdbm.dll - os=4.0 img=1.0 sys=4.0
RE: xfree86 install makes wininit not working
--- Robert Collins [EMAIL PROTECTED] a écrit : I realised the ini file was present in Sylvain's email. Sylvain - do the .NEW files exist? Are the paths correct? ROb Yes, I checked for some of these, the .new exists in the correct paths (checked in dos box too to see if 8.3 names are correct, and they are). ___ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com
Re[2]: setup with empty proxy password
Hello ljubomir, Thursday, April 18, 2002, 12:08:56 PM, you wrote: lmpc Sorry for beeing unprecise. My internet acsess setup is solved by an lmpc automatic configuration script proxy server, with an user name, but without lmpc password (empty password). If I start cygwin setup.exe, and choose Use IE5 Settings, Hmm I have to check MSDN for more information but it seems that the Inet API (which is used when you check User IE5 Settings) is the culprit. However, is it possible to type in your username in the usual place in the InternetExplorer settings and leave the password empty ? This will solve your problem. lmpc the prompt for Proxy authorisation pops up. The problem is: without lmpc specifying some password, the OK button stays inactive. And, of course, lmpc only correct password is empty one :( Yes, this is known problem - in fact I'm sure once I had a patch for this but it didn't make its way into the setup.exe source :( Or more accurate it seems I didn't send it to the cygwin-patches list at all... I dont remember why:( See this thread in the ml archives: http://cygwin.com/ml/cygwin-apps/2001-11/msg00427.html -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[Fwd: Updated: mingw-runtime-1.3-1]
I don't think this made it to the list via the automated gateway. Original Message Subject: Updated: mingw-runtime-1.3-1 Date: Tue, 09 Apr 2002 18:59:37 -0400 From: Earnie Boyd [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] I've made a new version of the mingw-runtime available for download. A list of what has changed is attached. To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. Note that we do not allow downloads from sources.redhat.com (aka cygwin.com) due to bandwidth limitations. This means that you will need to find a mirror which has this update. In the US, ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/ is a reliable high bandwidth connection. In Germany, ftp://ftp.uni-erlangen.de/pub/pc/gnuwin32/cygwin/mirrors/cygnus/ is usually pretty good. In the UK, http://programming.ccp14.ac.uk/ftp-mirror/programming/cygwin/pub/cygwin/ is usually up-to-date within 48 hours. If one of the above doesn't have the latest version of this package then you can either wait for the site to be updated or find another mirror. If you have questions or comments, please send them to the Cygwin mailing list at: [EMAIL PROTECTED] . I would appreciate it if you would use this mailing list rather than emailing me directly. This includes ideas and comments about the setup utility or Cygwin in general. Really. No kidding. Email cygwin stuff to [EMAIL PROTECTED] If you want to make a point or ask a question, the Cygwin mailing list is the appropriate place. Did I mention that I'd prefer that all cygwin questions should go to [EMAIL PROTECTED]? I can't remember... *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. I implore you to READ this information before sending email about how you tried everything to unsubscribe. In 100% of the cases where people were unable to unsubscribe, the problem was that they hadn't actually read and comprehended the unsubscribe instructions. If you need to unsubscribe from cygwin-announce or any other mailing list, reading the instructions at the above URL is guaranteed to provide you with the info that you need. Christopher Faylor Red Hat, Inc. 2002-04-09 Earnie Boyd [EMAIL PROTECTED] * moldname-crtdll.def: Remove CR from end of line. * moldname-msvcrt.def: Ditto. * Makefile.in: Use bzip2 compression for Cygwin target. 2002-04-04 Danny Smith [EMAIL PROTECTED] * include/math.h (DOMAIN, SING, OVERFLOW, UNDERFLOW, TLOSS, PLOSS): Move oldname defines back, following the underscored names. 2002-03-29 Danny Smith [EMAIL PROTECTED] * include/stdio.h (_snwprintf): Correct spelling. (_vsnwprintf): Likewise. * include/wchar.h (_snwprintf): Correct spelling. (_vsnwprintf): Likewise. 2002-03-26 Danny Smith [EMAIL PROTECTED] * moldname.def.in (__MSVCRT__): Replace with !(__CRTDLL__). (wpopen): Add if !(__CRTDLL__). * Makefile.in (moldname-msvcrt.def rule): Use -C, not -c to preserve comments. (moldname-crtdll.def rule): Likewise. * moldname-msvcrt.def: Regenerate. * moldname-crtdll.def: Regenerate. * include/stdio.h (wpopen):Use prototype, not a define. (_swnprintf): Add prototype. (_vswnprintf): Likewise. Tidy up whitespace. * include/wchar.h (_swnprintf): Add prototype. (_vswnprintf): Likewise. Tidy up whitespace. 2002-01-28 Danny Smith [EMAIL PROTECTED] * include/malloc.h (_heapinfo): Correct structure definition. (_USEDENTRY,_FREEENTRY): Add defines. Add comment on platform support for _heap* functions. (_get_sbh_threshold): Add prototype. (_set_sbh_threshold): Likewise. (_expand): Likewise. 2002-01-25 Danny Smith [EMAIL PROTECTED] * profile/profil.c: Update copyright info. * profile/profil.h: Likewise. * profile/gcrt0.c: Likewise. 2002-01-25 Pascal Obry [EMAIL PROTECTED] * profile/profil.h (PROFADDR): Cast idx to unsigned long long to avoid overflow. * profile/gmon.c: Define bzero as memset if mingw32. (monstartup): Use it. 2002-01-25 Danny
[Fwd: Updated: w32api-1.3-1]
I don't think this made it to the list via the automated gateway. Earnie. Original Message Subject: Updated: w32api-1.3-1 Date: Tue, 09 Apr 2002 19:04:49 -0400 From: Earnie Boyd [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] I've made a new version of the w32api headers and libraries available for download. A list of what has changed is attached. To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and answer all of the questions. Note that we do not allow downloads from sources.redhat.com (aka cygwin.com) due to bandwidth limitations. This means that you will need to find a mirror which has this update. In the US, ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/ is a reliable high bandwidth connection. In Germany, ftp://ftp.uni-erlangen.de/pub/pc/gnuwin32/cygwin/mirrors/cygnus/ is usually pretty good. In the UK, http://programming.ccp14.ac.uk/ftp-mirror/programming/cygwin/pub/cygwin/ is usually up-to-date within 48 hours. If one of the above doesn't have the latest version of this package then you can either wait for the site to be updated or find another mirror. If you have questions or comments, please send them to the Cygwin mailing list at: [EMAIL PROTECTED] . I would appreciate it if you would use this mailing list rather than emailing me directly. This includes ideas and comments about the setup utility or Cygwin in general. Really. No kidding. Email cygwin stuff to [EMAIL PROTECTED] If you want to make a point or ask a question, the Cygwin mailing list is the appropriate place. Did I mention that I'd prefer that all cygwin questions should go to [EMAIL PROTECTED]? I can't remember... *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] If you need more information on unsubscribing, start reading here: http://sources.redhat.com/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. I implore you to READ this information before sending email about how you tried everything to unsubscribe. In 100% of the cases where people were unable to unsubscribe, the problem was that they hadn't actually read and comprehended the unsubscribe instructions. If you need to unsubscribe from cygwin-announce or any other mailing list, reading the instructions at the above URL is guaranteed to provide you with the info that you need. Christopher Faylor Red Hat, Inc. 2002-04-09 Earnie Boyd [EMAIL PROTECTED] * Makefile.in (bindist): Use * instead of . for file list for tar command. 2002-04-02 Danny Smith [EMAIL PROTECTED] * include/wtypes.h (enum tagCLSCTX): Change formatting. 2002-04-02 Pat Thoyts [EMAIL PROTECTED] * include/objidl.h (IRunningObjectTable.Register): Correct prototype. * include/wtypes.h (ROTFLAGS_REGISTRATIONKEEPSALIVE, ROTFLAGS_ALLOWANYCLIENT): Add defines. 2002-03-31 Victor Porton [EMAIL PROTECTED] * include/shellapi.h (SHGFI_ATTR_SPECIFIED): Add define. 2002-03-29 David Robinow [EMAIL PROTECTED] * include/wingdi.h (SetPixelFormat): Correct prototype. 2002-03-29 Phil Krylov [EMAIL PROTECTED] * include/richedit.h (EM_SHOWSCROLLBAR): Add define. 2002-03-26 Phil Krylov [EMAIL PROTECTED] * include/richedit.h (EM_GETSCROLLPOS, EM_SETSCROLLPSPOS): Add defines. 2002-03-14 Gunnar Degnbol [EMAIL PROTECTED] * include/richedit.h (RICHEDIT_CLASS): UNICODE it. * include/shlobj.h (IContextMenu2): Put methods in right order. * include/basetyps.h (REFGUID, REFIID, REFCLSID): Check for CINTERFACE before defining. 2002-03-09 Danny Smith [EMAIL PROTECTED] * include/accctrl.h: Add #pragma GCC system_header if __GNUC__ = 3. * include/aclapi.h: Same. * include/basetsd.h: Same. * include/basetyps.h: Same. * include/cderr.h: Same. * include/cguid.h: Same. * include/commctrl.h: Same. * include/commdlg.h: Same. * include/cpl.h: Same. * include/cplext.h: Same. * include/custcntl.h: Same. * include/dbt.h: Same. * include/dde.h: Same. * include/ddeml.h: Same. * include/dlgs.h: Same. * include/excpt.h: Same. * include/httpext.h: Same. * include/imagehlp.h: Same. * include/imm.h: Same. * include/initguid.h: Same. * include/intshcut.h:
Re: Where is the manual to manually install cygwin in Windiows 2000
Hallo, from where can the source of setup be downloaded? CVS is no choice, because of a firewall. Is there a possibility to start setup.exe in batchmodus, so cygwin could be installed an a lot of machines remotly? Regards __ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] Updated: libpng-1.0.13-1
The libpng package has been updated to version 1.0.13-1. libpng is a library that provides routines to access and manipulate Portable Network Graphics (PNG) images. PNG is a lossless, patent- unencumbered image format intended to replace GIF. CHANGES: - Correct a bug in pngconf.h (_cdecl), update to 1.0.13 release - split into three packages, instead of just two (yes, it was necessary. See below) libpng-1.0.13-1 : documentation and the postinstall script libpng10-1.0.13-1 : the dll libpng10-devel-1.0.13-1 : the link libs, headers, etc - Note: most people will get the libpng10 package automagically, but you need to explicitly select and install the libpng10-devel package. - Aside: there are a few packages that depend on cygpng2.dll (that is, on the libpng2 package). libpng2 can be installed alongside these three packages, but new compiles will link against cygpng10.dll. Package maintainers should remember to update their setup.hints when recompiling dependent packages, to reflect the (future) new dependence on the libpng10 package. -- Charles Wilson libpng volunteer maintainer for cygwin INSTALLATION: To update your installation, click on the Install Cygwin now link on the http://cygwin.com/ web page. This downloads setup.exe to your system. Then, run setup and update the libpng package -- and also install the new libpng10 and libpng10-devel package. Note that we have recently stopped downloads from sources.redhat.com (aka cygwin.com) due to bandwidth limitations. This means that you will need to find a mirror which has this update. In the US, ftp://mirrors.rcn.net/mirrors/sources.redhat.com/cygwin/ is a reliable high bandwidth connection. In the UK, http://programming.ccp14.ac.uk/ftp-mirror/programming/cygwin/pub/cygwin/ is usually up-to-date within 48 hours. If one of the above doesn't have the latest version of this package then you can either wait for the site to be updated or find another mirror. If you have questions or comments, please send them to the Cygwin mailing list at: [EMAIL PROTECTED] . I would appreciate if you would use this mailing list rather than emailing me directly. This includes ideas and comments about the setup utility or Cygwin in general. If you want to make a point or ask a question, the Cygwin mailing list is the appropriate place. *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: [EMAIL PROTECTED] NOTES: In order to facilitate peaceful coexistence, the upstream libpng folks made a few changes. Now, you can use -I/usr/include/libpng10 -lpng10 to explicitly link against 1.0.x, or you can use (eventually) -I/usr/include/libpng12 -lpng12 to explicitly link against 1.2.x Also, they recommend symlinks so that -I/usr/include/libpng -lpng will link against the newest version of libpng installed on the system. They also decided to scrap the [cyg|lib]png2.dll, 3.dll, sequence, instead, going with MAJMIN, so 1.0.x is now cygpng10.dll -- ditto for the import libs and static libs, as well as moving the header files into versioned subdirs of /usr/include/. This is a major pain, but nobody asked me. So, we have: dynamic lib: cygpng10.dll import lib: libpng10.dll.a static lib: libpng10.a include files: /usr/include/libpng10/* The symlinks I mentioned earlier: in /usr/lib: libpng.dll.a -- libpng10.dll.a in /usr/lib: libpng.a -- libpng10.a in /usr/include: libpng -- libpng10/ I've implemented this symlink creation as part of the postinstall script. Finally, they recommend removing the /usr/include/png[conf].h files completely -- setup.exe handles this for us. However, this means that dependent packages MUST adjust their -I paths... Presumably, the 1.2.x version of libpng will use 12 suffixes. o Now uses the auto-import functionality of newer binutils, and doesn' t use __declspec(dllimport). This means you no longer need -DPNG_STATIC when compiling objects intended for static linking. Just compile as normal. HOWEVER, you need to use a special flags when linking statically: 'gcc -static'. For dynamic linking, you need no special link-time flags (assuming you're using binutils newer than 20010930, when --enable-auto-import was made the default). -- PRO: no compile time flags needed when building client programs; ONLY need a link-time flag linking to static libraries. NO special flags at compile-time nor link-time when linking to dynamic links. -- CON: (partial): if using binutils older than 20010930, you now need a special linktime flag for dynamic linking (-Wl,--enable-auto-import). However, with an up-to-date binutils, you don't need this. o The following
CreateWindow Errors and undefined reference to InitCommonControls
Greetings, I have two problems that I am hoping some of you could shed some light on. I am getting a NULL from calls to subsequent calls to CreateWindow after the first one to create the parent window. This happens for any call to it, I am using the instance value passed to WinMain and am using the handle of the parent window. Here is the kicker: This happens on Win98 but I also run the code on my WinNT machine and have absolutely no problems with it. I do remeber there being an issue in how hInst is handled between winNT and win98. Anyone else run into this problem? Any suggestions/insight would be greatly appreciated. My second problem is that during linking, I get an undefined reference to InitCommonControls function, I am linking against gdi32 and user32, is there some other library I should be linking with as well? Thanks in advace for all suggestions/hints/comments, they are much appreciated! -Bryan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
[ANNOUNCEMENT] New on sourceware: libpng10-devel-1.0.13-1
See libpng-1.0.13-1 announcement --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Where is the manual to manually install Cygwin in Windows 2000
From: Randall R Schulz [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 2:34 AM To: George Hester; [EMAIL PROTECTED] Subject: Re: Where is the manual to manually install Cygwin in Windiows 2000 George, I don't know what's not to like about Setup.exe (well, maybe URL-encoded mirror directory names), but you're really bucking the tide and going against the grain in trying to install without Setup.exe. You'll also be told (if this message doesn't forestall it) that this list doesn't cater to problems with installation or problems originating in installation errors for people who don't use the standard installation procedure based on Setup.exe. He maybe bucking the tide but IMHO he does have a point of sorts: setup.exe has become a real mess TBH between the URL directory names, accumulating multiple copies of data in multiple places instead of the simple tree used before and the fallacy inherent in a GUI install. What makes for an easy install on one workstation ought to imply ease of use on multiple workstations... it doesn't, quite the contrary, a simple config file based approach with a script that did the installing would be far, far easier. (such as make) As it is, it smacks of the developer knows best and one size fits all approaches so popular at M$ which is sad given cygwin's heritage! Short-sighted, misguided install philosophy aside, thanks for a wonderful selection of software :) Lawrence -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Where is the manual to manually install Cygwin in Windiows 2000
At 09:45 PM 4/18/2002, Michael A Chase wrote: From: Larry Hall (RFK Partners, Inc) [EMAIL PROTECTED] To: George Hester [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 18:09 Subject: Re: Where is the manual to manually install Cygwin in Windiows 2000 At 10:25 AM 4/18/2002, George Hester wrote: The last time I tried the installer I did not like the result. So now I have downloaded all the packages I need evne the docs. But I see nothing about how to install this manually; what environment variables I should set. Nothing at all. All I see is telling me to use the installer. If I do not want to do this does that mean I cannot install Cygwin in Windows 2000? Thanks. What didn't you like? It may have been fixed or you might not understand the implications of some of your choices. OK. I guess you just somehow missed this: http://www.cygwin.com/download.html That explains your options. Installing by a method other that setup is not really supported by this list however. BTW, there are no *required* settings beyond unpacking the software. But if you want any of the additions that setup gives you, that's another argument for just using setup. Of course, the source for setup is available if you'd just prefer to look at it to find out what it does. But you're right. There is no documentation that guides you through a manual install of Cygwin. It's assumed that if you don't use setup, you understand enough about what you're doing to just do it. Either that or you're the adventurous type. ;-) Really, there's really no *magic* to setup though... There are some mount points that _must_ be created for Cygwin to work reliable I quite disagree with this point. If it were true, it would be impossible to move a Cygwin executable and the DLL to a machine without a Cygwin install and have it work. This does work in the general case, though there are specific packages for which it won't without additional configuration (like the mount points you mentioned, mount type, environment variable settings, etc). But those are limited exceptions to the rule. and many packages have postinstall scripts that should be run. Which can still be run manually if the user chooses. Setup automates the running of these but there is still nothing magical about them. Setup.exe will take care of them for you. Without it you are on your own. I'm only mentioning these as a caution against what you seem to insist on doing. Don't expect any support if you go against all advice. I fully agree with this. The above comments I made are really nits since I want to dispel the myth that setup does things that can't be done manually. Anyone really interested in installing manually can always look at what setup does and perform the same steps. My impression is that people looking to install manually are looking for a scriptable setup, of which there is already a start (thanks Rob). I'd recommend anyone who plans to put any time into creating their own automated installation to seriously consider adding to the capabilities of setup in this area. You'll leverage allot of work, make things easier for yourself and others, and gain something that is maintainable over time. Just my $.02. Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Where is the manual to manually install cygwin in Windiows 2000
At 07:36 AM 4/19/2002, misi misi wrote: Hallo, from where can the source of setup be downloaded? CVS is no choice, because of a firewall. No, CVS is it. Is there a possibility to start setup.exe in batchmodus, so cygwin could be installed an a lot of machines remotly? I refer you to: http://cygwin.com/ml/cygwin/2002-04/msg01008.html Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: make customized installation of cygwin
At 05:28 AM 4/19/2002, hugo wrote: Hi I would like create a customized version of cygwin - a cygwin distribution which includes Perl TK, some perl utilities of my own, some other extras like Tk::FileDialog and the like. I would like to be able to package that up, then install this with a script similar to setup.exe on other computers. I had a look at the setup.exe script - I cannot customize it as it is binary code. I also tried to simply zip up my customized cygwin distribution and install on another computer. This didn't work. My question is: is there any way to create a customized version of cygwin, then use an install script that installs cygwin properly on any other computer (this would include doing the mkpasswd -l etc/password and mkgroup -l /etc/group commands and whatever else is needed to install cygwin properly). Can anyone help me out with this? Setup is what you want to look at. I refer you to: http://cygwin.com/ml/cygwin/2002-04/msg01008.html Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Where is the manual to manually install Cygwin in Windows 200 0
At 09:21 AM 4/19/2002, Lawrence W. Smith wrote: From: Randall R Schulz [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 2:34 AM To: George Hester; [EMAIL PROTECTED] Subject: Re: Where is the manual to manually install Cygwin in Windiows 2000 George, I don't know what's not to like about Setup.exe (well, maybe URL-encoded mirror directory names), but you're really bucking the tide and going against the grain in trying to install without Setup.exe. You'll also be told (if this message doesn't forestall it) that this list doesn't cater to problems with installation or problems originating in installation errors for people who don't use the standard installation procedure based on Setup.exe. He maybe bucking the tide but IMHO he does have a point of sorts: setup.exe has become a real mess TBH between the URL directory names, accumulating multiple copies of data in multiple places instead of the simple tree used before and the fallacy inherent in a GUI install. What makes for an easy install on one workstation ought to imply ease of use on multiple workstations... it doesn't, quite the contrary, a simple config file based approach with a script that did the installing would be far, far easier. (such as make) As it is, it smacks of the developer knows best and one size fits all approaches so popular at M$ which is sad given cygwin's heritage! Short-sighted, misguided install philosophy aside, thanks for a wonderful selection of software :) Thanks for your points. These have been discussed before. You can review the discussion in the email list archive if you like. Key points of the installer are that it must not be reliant on facilities that are part of the packages it's installing and that it must be GUI based for the masses. That doesn't mean that these are exclusive requirements. The goal is to make setup support a variety of needs. But it needs to focus on a subset of those requirements initially, due to resource constraints. Anyone interested in seeing more progress in an area of their preference is welcome to join in the development of setup. That's generally the best way to resolve issues with missing functionality. I think we're all pretty clear on the varied needs for installation. IMO, it's only worth discussing here if it's in the context of new development work to improve setup. Any takers on that note? Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: CreateWindow Errors and undefined reference to InitCommonControls
At 08:51 AM 4/19/2002, Siever Bryan-BSIEVER1 wrote: Greetings, I have two problems that I am hoping some of you could shed some light on. I am getting a NULL from calls to subsequent calls to CreateWindow after the first one to create the parent window. This happens for any call to it, I am using the instance value passed to WinMain and am using the handle of the parent window. Here is the kicker: This happens on Win98 but I also run the code on my WinNT machine and have absolutely no problems with it. I do remeber there being an issue in how hInst is handled between winNT and win98. Anyone else run into this problem? Any suggestions/insight would be greatly appreciated. This list deals with Cygwin specific issues. As such this issue is off-topic. You may want to consult a Win32 specific list or reference book. My second problem is that during linking, I get an undefined reference to InitCommonControls function, I am linking against gdi32 and user32, is there some other library I should be linking with as well? Thanks in advace for all suggestions/hints/comments, they are much appreciated! nm -A /lib/*.a | grep InitComm also not really Cygwin specific but... Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: info
Hey There!brbr Are you a guy? Do you ever worry that your penis isn't as large as it bcould be/b? Maybe you've considered buying a pump? Well, the pump WILL make your penis bigger, that is a fact. But what if you want to do something with your penis besides leave it in a tube? In that case you're back where you started. And then there's surgery. Did you know there is fairly high rate of failure with that kind of stuff? I'd rather have an average penis than a deformed penis, wouldn't you? If you're ready to get serious about increasing the size of your penis, then read on. Not only will the Add-Inches program give you a bigger dick, it will help you sustain erections, it will help you achieve bmultiple orgasms without losing your erection/b, it will teach you thrusting techniches that will set you apart in bed from just about every man out there, and it will teach you how to control your orgasms so closely that you can bactually plan them/b. It will do all of this bwithout pumps, surgery, or anything harmful to your body/b. brbrIf you want to:brbr * Last longer in bedbr* Control your orgasms so you can actually plan when they happenbr * Increase your penis size without pumps, surgery, or any other gadgets or invasive techniquesbrbrthen try the program. We are so sure that it will work for you we GUARANTEE it 100%. If you do the excersizes in the program and don't see results within 1 month we will brefund 100% of your money/b. This program works, it's been tried and tested. Read the testimonials, try the program, you've got nothing to lose. bAre you ready to be on your way to having the dick you've always dreamed about? If you are, a href=http://affiliates.add-inches.com/store/%78%30%72%64%62%32;click here/a.brbrbrbrbrbrbrbrbrbrbrbrbrbrbrbrbr brbrbrbrbrbrbrbrbrbrbrbrbrbrbrbrbrbrbrbr brbrbrbrbrbrbrbrbrbrbrbrbrbrbrbrbrbrbr brbrbrbrbrbrbrbrbrbrThis message is not spam; it is never sent unsolicited. If you wish to be removed from future mailings please email [EMAIL PROTECTED] with the subject REMOVE. Thank you. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Where is the manual to manually install cygwin in Windows 200 0
On Fri, Apr 19, 2002 at 02:21:20PM +0100, Lawrence W. Smith wrote: setup.exe has become a real mess TBH between the URL directory names, accumulating multiple copies of data in multiple places instead of the simple tree used before and the fallacy inherent in a GUI install. What's become a real mess is the fact that people seem to be doing an ls in their download directories and then apparently gasp with slack jawed horror when they see the awful mirror-based directory in their download area. However, that aside, setup's functionality has not degraded. In fact it improves with each release, just like good software should. What makes for an easy install on one workstation ought to imply ease of use on multiple workstations... it doesn't, quite the contrary, Why doesn't it? Run setup on each workstation. If that's too hard, then copy the download directory around to multiple workstations. Think of the directory as a black box. Don't perform ls in the directory if your sensibilities are offended by the mirror subdirectory. Or, copy the whole cygwin root directory around and set up the mount points using mount. It's not that hard if you reorient your thinking to solving problems rather than complaining about problems and waiting for someone to solve your problems for you. a simple config file based approach with a script that did the installing would be far, far easier. (such as make) This is really hilarious. When we had a version of setup that just did a non-gui install everyone whined about how hard it was and kept asking where the gui version was. Now true nirvana would be achieved if only we had a script based install. As it is, it smacks of the developer knows best and one size fits all approaches so popular at M$ which is sad given cygwin's heritage! Cygwin's heritage is free software. Unfortunately, that means that there are a lot of groaners who think things should be done their way and few people doing the actual work. So developers work on what we want to work on, but still try to produce software that we think will help. Oddly enough, it's the developers who advance the state of the software, not the hyperbolic messages from people who have figured out how to use their mail software to send opinionated email to cygwin at cygwin dot com. So, bottom line is that we have little interest in dealing with people who think that they have special needs but have no special skills to implement their needs -- especially when they can't even really articulate why the available software doesn't fit their needs. That doesn't mean that there aren't all sorts of methods for installing cygwin that will work just as well as setup.exe. It's just up to whomever to exert a little brain power to figure out how to do it. I even posted a short snippet of code that showed how to do this in a script not too long ago. Regardless, It is always humorous to see people becoming indignant about software that they're being given for free. Short-sighted, misguided install philosophy aside, thanks for a wonderful selection of software :) Ignorant, inflammatory email aside, you're welcome. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Looking for mknod implementation
Hello: Just installed cygwin today (cygwin-1.3.10-1). I'm trying to create some named pipes like so: mknod myfile p However, I get a Function not implemented message and no pipe. Having looked through this list, I found a message from Robert Collins dated Nov 9 2001 http://sources.redhat.com/ml/cygwin/2001-11.t/msg00517.html stating that a patch containing a mknod implementation exists in the cygwin-patches list. I've searched through that list, but so far I've been unable to find the aforementioned patch. Does anybody have any idea where exactly it might be found? Thanks, Edward Ross -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: [ANNOUNCEMENT] New Package: Pine]
*** [EMAIL PROTECTED] wrote on Apr 18, 2002: :) *** How to run Pine under Cygwin :) :) - If you plan to use filters in Pine (display and send filters) or :) the pipe command, you need to execute the following command: :) :)ln -s /bin/bash.exe /bin/csh.exe :) :) Would this still be applicable if the tcsh package is installed? Is there a :) [simple|quick] explaination for this requirement? Hello Chris, This is what happens. Pine needs to know your shell when it executes shell commands, for this, it tests to see if the SHELL variable is set. I am running the bash shell, and somehow, even though the SHELL variable is set, Pine does not pick it up. When Pine does not know which shell you are using from the SHELL variable, then pine assumes that you are using csh, hence you need to fake a csh shell, and that's the reason for that command. I haven't tested if this trick works (or does not) under tcsh. I would appreciate if you let me know what you find in this respect. Thanks! -- Eduardo http://www.math.washington.edu/~chappa/pine/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Having lots of troubles building/getting cygwin base source!!!
Ok, I seem to be having some difficulties getting cygwin sources. When I pull the latest source for cygwin (cygwin-1.3.10-1) using setup, I cannot build it because the winsup/w32api directory is empty, and make fails with a no for target 'all'. When I try to pull the 20020409 snapshots from either planetmirror.com or mirrors.rcn.net, I keep getting a 'no such file or directory', and it looks like they have some wierd symbolic link to a file that doesn't exist within the machine. SO, how do I get a complete buildable snapshot image of the cygwin base? Any help appreciated. Thanks -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: FW: Can you offer enscript.cfg file for cygwin?
Like Xiangjiang, I am also stumped on how to configure the Cygwin 'lpr' so that it can be used by enscript. I searched the archives but didn't succeed in finding anything that seemed to help. Here are the messages I get: lpr: can't open 'prn' for writing lpr: The printer name is invalid. If it helps any, the printer I want to use is on the network but associated with lpt1 through an NT login script. It is able to print either PCL or PS. TIA Gerrit P. Haase wrote: Hallo Xiangjiang, It is better, though I still could not make it print out anything Enscript uses 'lpr' from the cygutils package for printing to PRN. Printing under Cygwin was discussed a lot of times on this list and there is a really good reason why 'lpr' is in the cygutils package included. Please search the archives, I'm sorry that I cannot tell you some more right now, I will have to search the archives too before I know why you cannot print;) Gerrit -- =^..^= Please keep communication about Cygwin and Cygwin Aplications on the Cygwin mailinglist. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Having lots of troubles building/getting cygwin base source!!!
On Fri, Apr 19, 2002 at 10:03:37AM -0600, Mark Paulus wrote: how do I get a complete buildable snapshot image of the cygwin base? Calm down. http://cygwin.com/snapshots/ cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
FAQ entry for setting up /etc/passwd with both NT domain users andSamba servers under ntsec
I spent a while figuring out the right way to configure Cygwin's
/etc/passwd in the face of CYGWIN=ntsec, domain users, and Samba
servers. I thought I'd write a quick FAQ entry to save others time.
Let's say you have a Windows domain DOM to which all your users
belong. However, you also have a Samba server, which we'll call
SAMBA. Usernames are the same in the domain and on the Samba
server; let's consider user juser. Files created on the Windows
machines will be correctly owned by DOM\juser; files on the Samba
server will be owned by SAMBA\juser. Unfortunately Samba does not
yet handle forwarding user SIDs from the domain, even with security =
domain, though the documentation says work is ongoing in this area.
Instead it just makes up a SID base when it first initializes itself,
and uses a simple algorithm (2*uid+1000) to generate RIDs from uids.
The older cygwins didn't have to worry about this issue, since they
always mapped all the file ownership on remote shares to the username
of the user who was active. (This is still the default behavior if
you don't set CYGWIN=ntsec.) Unfortunately, in this mode you can't
see file owners or permissions, which is a serious limitation.
The question then is, how do we map the SAMBA\juser SIDs for cygwin?
If you just do a standard mkpasswd -d, you will get a password file
that includes uids for all the DOM users, but doesn't include uids for
the SIDs generated by the SAMBA server; files on that server will be
shown as owned by (effectively) random uids with no names. What's
more, since the uids won't match, programs will tend to get confused
as to whether they're accessible. For example, if your Unix account
owns a file with 644 permissions, access(file,W_OK) will report
failure (specifically EACCESS, permission denied) if you check it from
cygwin.
At first I just wanted to give names to the uids owning the Samba
server files. Following Corinna's advice from a while back, I created
a series of /etc/passwd lines by taking the Unix uids, applying the
Samba conversion to get RIDs, then writing out lines with the RID as
the uid and the username as SAMBA\juser. This gave real usernames
to the uids, but didn't help with the access problems. I then decided
the SAMBA\ prefixes weren't buying me much, and removed them. At
this point each user had two entries in the Cygwin /etc/passwd, one
for the DOM RID mapping to one UID, and the other for the SAMBA RID
mapping to another UID. This made the output of ls -l, etc., look
prettier, since users appeared to own their own files, but the
underlying uids still didn't match for things like access().
Finally I realized that, unlike a normal Unix passwd file, it made
sense for there to be multiple lines with the same name and uid. In
normal Unix all you do is map from username to uid and back, so lines
like this would be meaningless. With cygwin there's an extra mapping
from SID to uid, and that's when it helps to have multiple lines. My
final solution was to write a Perl script that digests the Cygwin
mkpasswd -d output to get preferred name-uid mappings, then digests
the Unix passwd file to generate SAMBA+RID-uid mappings that match
the domain uids. (The Samba SID base is available in the MACHINE.SID
file.) Combining the initial mkpasswd -d output with the output of
this script gives us the final Cygwin /etc/passwd. Now both
DOM\juser and SAMBA\juser files are mapped to the same uid and all
the cygwin functionality just works.
This still seems like something of an elaborate workaround,
unfortunately. Ideally, of course, the Samba server would use the
user's domain SID. But until that happens, it would be nice if there
was a way to coerce it into using the right SID. Clearly we can reset
the MACHINE.SID to the domain SID base. But the RIDs will still be
out of wack; we would need a table mapping uids to RIDs that Samba
could use. (We can't do it just by changing all the Unix uids,
since the domain RIDs can be odd numbers, unlike Samba user RIDs.)
I've appended my version of the perl script I use to do this. It
should be reasonably easy to customize.
I don't plan on pushing any further on this, but I'd be curious to
hear if anyone has any better strategies they've used in this
situation.
Chris
--
#!/usr/bin/perl
# This script builds a piece of the password file for Cygwin.
# It should be run on a Samba server; it parses the server's /etc/passwd
# and /etc/group and creates matching files in $TARGET_DIR
# suitable for appending to a cygwin /etc/{passwd,group}.
# It requires that the mkpasswd -d output be available in $TARGET_DIR.
# We use the SID of the host, from /etc/samba/MACHINE.SID, plus the
# computed ID (1000+uid*2, 1001+gid*2). However, we map usernames
# that appear in the domain not to that $uid, but to the domain $uid,
# so that Cygwin thinks it's all the same.
#
# Hopefully this will all be unnecessary with a later release of Samba.
# See the discussion of security = domain in the
Nevermind, fixed: Re: Having lots of troubles building/getting cygwin base source!!!
Disregard the previous note. I apologizing for cluttering up the airwaves with this trivial matter. On Fri, 19 Apr 2002 10:03:37 -0600, Mark Paulus wrote: Ok, I seem to be having some difficulties getting cygwin sources. When I pull the latest source for cygwin (cygwin-1.3.10-1) using setup, I cannot build it because the winsup/w32api directory is empty, and make fails with a no for target 'all'. When I try to pull the 20020409 snapshots from either planetmirror.com or mirrors.rcn.net, I keep getting a 'no such file or directory', and it looks like they have some wierd symbolic link to a file that doesn't exist within the machine. SO, how do I get a complete buildable snapshot image of the cygwin base? Any help appreciated. Thanks -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Where is the manual to manually install cygwin in Windows 2000
From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 4:10 PM To: [EMAIL PROTECTED] Subject: Re: Where is the manual to manually install cygwin in Windows 200 0 snip What's become a real mess is the fact that people seem to be doing an ls in their download directories and then apparently gasp with slack jawed horror when they see the awful mirror-based directory in their download area. However, that aside, setup's functionality has not degraded. In fact it improves with each release, just like good software should. Not entirely true sometimes it improves sometimes it meanders down a blind alley or two, much like redhat your sponsor! It's free software as a nobody user I accept its oddities and enjoy it's strengths, I'd like to contribute some constructive feedback but clearly that's not welcome. What makes for an easy install on one workstation ought to imply ease of use on multiple workstations... it doesn't, quite the contrary, Why doesn't it? Run setup on each workstation. I don't think that's terribly scalable. If that's too hard, then copy the download directory around to multiple workstations. Perhaps far more useful would be provide a cmdline mode to setup.exe offering a more flexible install method, scaleable to multiple installations and capable of saving a specific bundle of packages as an install set and then reapplying those with a single commandline across a list of boxes. This is meant as entirely constructive criticism, accompanied by an example suggestion, (not a demand or even a request), neither is it intended to solicit the perennial go code it yourself, we're too busy, response Think of the directory as a black box. Don't perform ls in the directory if your sensibilities are offended by the mirror subdirectory. I don't think this is about sensibilities but about choosing a simple, clean approach, without unnecessary complexity. As a for instance of the consequences of your approach: How would you suggest the mere mortals should clear out old versions of packages after say 4 or 5 revisions are sitting scattered across directory trees based on 6 different mirrors used by a particular user over a 2 year period? Or, copy the whole cygwin root directory around and set up the mount points using mount. It's not that hard if you reorient your thinking to solving problems rather than complaining about problems and waiting for someone to solve your problems for you. I'm not waiting for anything I already have my solution for dealing with the current bizarre consequences of setup.exe. It relies on simple scripting batch scripting, a simple config file based approach with a script that did the installing would be far, far easier. (such as make) This is really hilarious. When we had a version of setup that just did a non-gui install everyone whined about how hard it was and kept asking where the gui version was. Now true nirvana would be achieved if only we had a script based install. As it is, it smacks of the developer knows best and one size fits all approaches so popular at M$ which is sad given cygwin's heritage! Cygwin's heritage is free software. Unfortunately, that means that there are a lot of groaners who think things should be done their way and few people doing the actual work. So developers work on what we want to work on, but still try to produce software that we think will help. Oddly enough, it's the developers who advance the state of the software, not the hyperbolic messages from people who have figured out how to use their mail software to send opinionated email to cygwin at cygwin dot com. So, bottom line is that we have little interest in dealing with people who think that they have special needs but have no special skills to implement their needs -- especially when they can't even really articulate why the available software doesn't fit their needs. That doesn't mean that there aren't all sorts of methods for installing cygwin that will work just as well as setup.exe. It's just up to whomever to exert a little brain power to figure out how to do it. I even posted a short snippet of code that showed how to do this in a script not too long ago. Regardless, It is always humorous to see people becoming indignant about software that they're being given for free. Short-sighted, misguided install philosophy aside, thanks for a wonderful selection of software :) Ignorant, inflammatory email aside, you're welcome. I was attempting to offer a new direction that may have been overlooked from your perspective but clearly the experiences and or suggestions of users are of little consequence to you. My humblest apologies for attempting to make a feeble constructive suggestion. I'm glad such wonderful software has such an enlightened, good humoured ambassador. Thanks again, Lawrence -- Unsubscribe info:
Bug in setup.exe 2.194.2.24
Hi, I'm wondering if I've found a bug in setup.exe. I'm using 2.194.2.24 and when I go through Download from Internet and download the new components. It downloads them fine. Next, I re-run setup.exe and I go through Download from Internet again, (but this was by accident) and it says that the same files are ready to be downloaded and proceeds to re-download them all again. If I Install from Local Directory first it clears the problem. Alan. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Cygwin maildrop patches and issues (was Re: fetchmail 5.9.8 ...)
Rui,
On Sat, Mar 02, 2002 at 12:45:12AM +, Rui Carmo wrote:
However, mutt then complains that /var/spool/mail/user is not a valid
mbox file, since somewhere along the line, an extra blank line is inserted
at the beginning of the mailbox upon creation. Editing it out by hand
solves the problem, but is a rather lame fix.
The first attachment solves the above problem.
Unfortunately, I have discovered other problems:
1. maildrop appears (at least under Cygwin) to not quite respect
dotlocking and actually removes the lock file created by other
processes! The second attachment solves this problem.
2. maildrop appears to lock in a different order (i.e., dotlock then
fcntl()) than mutt (and procmail) (i.e., fcntl() then dotlock) so I'm
concerned about race conditions.
3. maildrop causes Cygwin to spin while another process has locked a mbox
via fcntl(F_SETLK). If interested, see the third attachment for details.
I'm interested in getting Cygwin maildrop to work because it is much
easier to build (and maintain) than procmail. Unfortunately, I'm getting
the impression that maildrop is used more for maildirs than for mboxes...
Thanks,
Jason
--- formatmbox.C.orig Mon Apr 1 21:01:02 2002
+++ formatmbox.CMon Apr 1 21:01:12 2002
-42,7 +42,7 time_ttm;
time(tm);
- tempbuf=\nFrom ;
+ tempbuf=From ;
tempbuf += maildrop.msginfo.fromname;
tempbuf += ' ';
--- dotlock.C.orig Tue Apr 2 01:57:49 2002
+++ dotlock.C Tue Apr 2 01:58:58 2002
-112,7 +112,7 AlarmTimer stat_timer;
}
else if (stat_timer.Expired())
{
- unlink(lockfile);
+ // unlink(lockfile);
}
}
108 147643 [main] maildrop 1816 fhandler_disk_file::fstat_helper: 0 = fstat (,
0x22C808) st_atime=3CA962A0 st_size=26158, st_mode=0x8180, st_ino=1446857, sizeof=88
109 147752 [main] maildrop 1816 fstat64: 0 = fstat (3, 0x22C808)
14988895 15136647 [win] maildrop 1816 wndproc 275 WM_TIMER 1 0
291 15136938 [win] maildrop 1816 _kill: kill (1816, 14)
242 15137180 [win] maildrop 1816 sig_send: pid 1816, signal 14, its_me 1
99 15137279 [win] maildrop 1816 sig_send: Waiting for thiscomplete 0x12C
273 15137552 [sig] maildrop 1816 wait_sig: awake
134 15137686 [sig] maildrop 1816 wait_sig: processing signal 14
99 15137785 [sig] maildrop 1816 wait_sig: Got signal 14
99 15137884 [sig] maildrop 1816 sig_handle: signal 14
126 15138010 [sig] maildrop 1816 sig_handle: signal 14, about to call 0x41FCF4
104 15138114 [sig] maildrop 1816 setup_handler: suspending mainthread
180 15138294 [sig] maildrop 1816 interruptible: pc 0x77F8318B, h 0x77F8,
interruptible 1, testvalid 1
181 15138475 [sig] maildrop 1816 interruptible: pc 0x77F8318B, h 0x77F8,
interruptible 0, testvalid 0
111 15138586 [sig] maildrop 1816 setup_handler: couldn't send signal 14
100 15138686 [sig] maildrop 1816 setup_handler: ResumeThread returned 1
104 15138790 [sig] maildrop 1816 setup_handler: returning 0
96 15138886 [sig] maildrop 1816 sig_handle: returning 0
109 15138995 [win] maildrop 1816 sig_send: returning 0 from sending signal 14
94 15139089 [win] maildrop 1816 kill_worker: 0 = kill_worker (1816, 14)
108 15139197 [sig] maildrop 1816 wait_sig: looping
103 15139300 [sig] maildrop 1816 wait_sig: awake
103 15139403 [sig] maildrop 1816 wait_sig: processing signal 14
95 15139498 [sig] maildrop 1816 wait_sig: Got signal 14
93 15139591 [sig] maildrop 1816 sig_handle: signal 14
95 15139686 [sig] maildrop 1816 sig_handle: signal 14, about to call 0x41FCF4
96 15139782 [sig] maildrop 1816 setup_handler: suspending mainthread
149 15139931 [sig] maildrop 1816 interruptible: pc 0x77F8318B, h 0x77F8,
interruptible 1, testvalid 1
153 15140084 [sig] maildrop 1816 interruptible: pc 0x77F8318B, h 0x77F8,
interruptible 0, testvalid 0
105 15140189 [sig] maildrop 1816 setup_handler: couldn't send signal 14
99 15140288 [sig] maildrop 1816 setup_handler: ResumeThread returned 1
95 15140383 [sig] maildrop 1816 setup_handler: returning 0
94 15140477 [sig] maildrop 1816 sig_handle: returning 0
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
lpr problem (was: Re: FW: Can you offer enscript.cfg file for cygwin?)
Dave schrieb: Like Xiangjiang, I am also stumped on how to configure the Cygwin 'lpr' so that it can be used by enscript. I searched the archives but didn't succeed in finding anything that seemed to help. Here are the messages I get: lpr: can't open 'prn' for writing lpr: The printer name is invalid. If it helps any, the printer I want to use is on the network but associated with lpt1 through an NT login script. It is able to print either PCL or PS. I have also problems with printing through lpr. Unfortunately I couldn't figure out how to set it up correct yet. There are some threads in the archives about printing without lpr, maybe there are some hints? Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Where is the manual to manually install Cygwin in Windiows 2000
On Fri, 19 Apr 2002 10:23:56 -0400 Larry Hall (RFK Partners, Inc) [EMAIL PROTECTED] wrote: At 09:45 PM 4/18/2002, Michael A Chase wrote: From: Larry Hall (RFK Partners, Inc) [EMAIL PROTECTED] To: George Hester [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 18:09 Subject: Re: Where is the manual to manually install Cygwin in Windiows 2000 Really, there's really no *magic* to setup though... There are some mount points that _must_ be created for Cygwin to work reliable I quite disagree with this point. If it were true, it would be impossible to move a Cygwin executable and the DLL to a machine without a Cygwin install and have it work. This does work in the general case, though there are specific packages for which it won't without additional configuration (like the mount points you mentioned, mount type, environment variable settings, etc). But those are limited exceptions to the rule. Those limited exceptions generate a lot of Cygwin is broke messages like when a version of setup failed to create the /usr/bin and /usr/lib mounts a couple months ago. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bug in setup.exe 2.194.2.24
On Fri, 19 Apr 2002 18:41:04 +0100 Alan Hourihane [EMAIL PROTECTED] wrote: I'm using 2.194.2.24 and when I go through Download from Internet and download the new components. It downloads them fine. Next, I re-run setup.exe and I go through Download from Internet again, (but this was by accident) and it says that the same files are ready to be downloaded and proceeds to re-download them all again. I think this is because you haven't installed the packages yet. I think setup.exe gets the current version information from the installed package not the download directory. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bug in setup.exe 2.194.2.24
Alan, I was about to send in a similar report yesterday evening. I think to generalize, the current Setup.exe offers to download based on which packages are currently installed, not on which packages are present in the local download area(s). I say this because even though I have a full set of packages in my download area, including all source packages, I only routinely install the binary counterparts. When I run Setup.exe for download, it lists n/a for all the installed binary packages but presents a (blank / unchecked) check-box in all the source code positions. I don't know about you, Alan, but I still have the vast preponderance of packages (488 package archive files) are in the old latest and contrib directories and only the few from the past week or so (22) in the new, mirror-separated directories. Randall Schulz Mountain View, CA USA At 10:41 2002-04-19, Alan Hourihane wrote: Hi, I'm wondering if I've found a bug in setup.exe. I'm using 2.194.2.24 and when I go through Download from Internet and download the new components. It downloads them fine. Next, I re-run setup.exe and I go through Download from Internet again, (but this was by accident) and it says that the same files are ready to be downloaded and proceeds to re-download them all again. If I Install from Local Directory first it clears the problem. Alan. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Where is the manual to manually install Cygwin in Windiows 2000
At 02:12 PM 4/19/2002, Michael A Chase wrote: On Fri, 19 Apr 2002 10:23:56 -0400 Larry Hall (RFK Partners, Inc) [EMAIL PROTECTED] wrote: At 09:45 PM 4/18/2002, Michael A Chase wrote: From: Larry Hall (RFK Partners, Inc) [EMAIL PROTECTED] To: George Hester [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, April 18, 2002 18:09 Subject: Re: Where is the manual to manually install Cygwin in Windiows 2000 Really, there's really no *magic* to setup though... There are some mount points that _must_ be created for Cygwin to work reliable I quite disagree with this point. If it were true, it would be impossible to move a Cygwin executable and the DLL to a machine without a Cygwin install and have it work. This does work in the general case, though there are specific packages for which it won't without additional configuration (like the mount points you mentioned, mount type, environment variable settings, etc). But those are limited exceptions to the rule. Those limited exceptions generate a lot of Cygwin is broke messages like when a version of setup failed to create the /usr/bin and /usr/lib mounts a couple months ago. Exactly. Which is why manual installation processes are a use at your own risk approach. My point is, if you're so inclined, you *can* install Cygwin and any of it's packages manually, without setup. Again, the only reason I mention this is because there have been indications from folks on this list that there is something which setup does that can't be reproduced by any other mechanism. This is just plain false. However, I am in no way encouraging people to use or generate an installation method other than setup. Certainly, if one does so, this list cannot entertain questions about installation problems based on such a procedure. I hope this message and my previous response to this thread clarifies the installation issue for those of all interests. I guess we'll see if that is indeed the case. ;-) Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bug in setup.exe 2.194.2.24
On Fri, Apr 19, 2002 at 11:22:08AM -0700, Michael A Chase wrote: On Fri, 19 Apr 2002 18:41:04 +0100 Alan Hourihane [EMAIL PROTECTED] wrote: I'm using 2.194.2.24 and when I go through Download from Internet and download the new components. It downloads them fine. Next, I re-run setup.exe and I go through Download from Internet again, (but this was by accident) and it says that the same files are ready to be downloaded and proceeds to re-download them all again. I think this is because you haven't installed the packages yet. I think setup.exe gets the current version information from the installed package not the download directory. This isn't the way it used to work, and shouldn't in my opinion. setup.exe should know what it's downloaded and not installed. Alan. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bug in setup.exe 2.194.2.24
On Fri, Apr 19, 2002 at 11:28:19AM -0700, Randall R Schulz wrote: I think to generalize, the current Setup.exe offers to download based on which packages are currently installed, not on which packages are present in the local download area(s). I hate to say it but that sounds like a bug to me. I can't remember if this is new behavior, though. Is it? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: command to close the bash window
Hi, yes. I prefer Ctrl/D, which I can even type faster than moving the mouse and click on x... -Original Message- From: Randall R Schulz [mailto:[EMAIL PROTECTED]] Sent: Donnerstag, 18. April 2002 23:06 To: [EMAIL PROTECTED] Subject: Re: command to close the bash window Hi, Also, don't just close the window. BASH will not get a chance to do it's termination processing and things like history saving and / or execution of the commands in ~/.bash_logout, if any, won't happen. Randall Schulz Mountain View, CA USA At 10:56 2002-04-18, you wrote: hongxun lee wrote: Does the current package include such a command as to close the Bash window? Ah try exit! :-) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: FW: Can you offer enscript.cfg file for cygwin?
Try this $ export PRINTER=computerprintername (or maybe) $ export PRINTER=computer\\printername and then run enscript. --Chuck Dave McLaughlin wrote: Like Xiangjiang, I am also stumped on how to configure the Cygwin 'lpr' so that it can be used by enscript. I searched the archives but didn't succeed in finding anything that seemed to help. Here are the messages I get: lpr: can't open 'prn' for writing lpr: The printer name is invalid. If it helps any, the printer I want to use is on the network but associated with lpt1 through an NT login script. It is able to print either PCL or PS. TIA -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
NT domain user's chmod on Samba file quietly fails
As I mentioned in my previous message, I've set up a fairly reasonable /etc/passwd that holds SIDs for both my Windows domain and the primary file server, a Samba box. The Windows SID and the Samba SID for each user map to the same UID (the Windows RID) to try to keep cygwin tools largely unaware of the discrepancy between the SIDs, even with CYGWIN=ntsec. Unfortunately, although I can chmod files just fine on Windows shares, it isn't working for Samba shares (using Samba 2.2.1a from the latest Redhat 7.2, latest cygwin, on either Windows NT or 2k): $ touch foo $ ls -l foo -rwxr--r--1 metcalf users 0 Apr 19 15:46 foo $ chmod 600 foo $ ls -l foo -rwxr--r--1 metcalf users 0 Apr 19 15:46 foo $ getfacl foo # file: foo # owner: metcalf # group: users user::rwx group::r-- mask::r-- other::r-- $ setfacl -m o::--- foo $ ls -l foo -rwxr--r--1 metcalf users 0 Apr 19 15:46 foo If I just try to make the file read-write, that works somewhat: $ chmod 400 foo $ ls -l foo -r-xr--r--1 metcalf users 0 Apr 19 15:46 foo If I bring up Explorer and, in the File Permissions dialog, reset the Everyone permission to O instead of R, that does work: $ ls -l foo -rwxr-1 metcalf users 0 Apr 19 15:46 foo The Samba server logs don't seem to be reporting anything too amiss, and the strace output between a working chown (on a Windows share) and a failing chown (on a Samba share) are basically indistinguishable. Any ideas as to what's going wrong here? Thanks, Chris Metcalf -- InCert Software -- 1 (617) 621 8080 [EMAIL PROTECTED] -- http://www.incert.com/~metcalf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
rexecd/inetutils configuration and startup question
All, Is there a document out there someplace that explains how to start the Cygwin implementation of rexecd, or perhaps somehting a little more generic discussing how to configure and start servers in Cygwin inetutils? I've spent the last couple of hours scouring Google and the Cygwin documentation and have been unable to find anything relevent. Any insight would be very much appreciated. Thanks. -Andy Major Harold G. Andrews II, Ph.D. Assistant Professor Department of Computer Science United States Air Force Academy DSN 333-7553 Comm 719-333-7553 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: lpr problem (was: Re: FW: Can you offer enscript.cfg file for cygwin?)
I have also problems with printing through lpr. Unfortunately I couldn't figure out how to set it up correct yet. There are some threads in the archives about printing without lpr, maybe there are some hints? See my message posted a few minutes ago. Currently, lpr.exe from the cygutils package is not documented (at all), and it expects printer shares to be specified using backslash notation: \\computer\share of course, since those are backslashes, they have to be escaped: computer\\share and what's odd, is that sometimes they must be escaped twice computershare because two shells parse it. It would be nice (tm) if someone wanted to contribute a man page, and perhaps some code to allow a) specifying printer names with forward slashes (autodetect and automatically convert to backslashes before GetHandle'ing the printer) b) figure out (and document) how to use local mount names (e.g. instead of \\bob\bigprinter, I've used the Add Printer Wizard and have added this remote printer to my local printer list as My Friend Bob's Big Fancy Printer. c) access to lpt1, lpt2, etc (although prn: seems to work already) All together nowpatches gratefully accepted. --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: fortune-1.8-2.tar.bz2 minor bug
Hi John. that's not a packing error nor cygwin specific and may also happen with gzipped tar, so for the curious: It's only a warning and avoided by something like bunzip foo.tar.bz2|(tar tvvf -;cat/dev/null) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Freitag, 19. April 2002 02:56 To: [EMAIL PROTECTED] Subject: fortune-1.8-2.tar.bz2 minor bug Hi Cygwin: The copy of fortune-1.8-2.tar.bz2 I get from planetmirror.com gives a warning message when I test it with bunzip -t. I get: bsip2: fortune-1.8-2.tar.bz2: trailing garbage after EOF ignored Not really a problem, but probably re-tarring it would be good. It installs fine... John Szetela -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Problems linking program
Larry, I did an nm -C and collected the output to a text file. I found references to these functions in libc, libg, and libcygwin. I am not quite sure what to look for now. Can you explain what I need to be looking for? Thanks, Matt At 02:24 PM 4/18/2002, you wrote: At 02:16 PM 4/18/2002, Matt Minnis wrote: I am having trouble linking a program: What libraries are these found in? __umoddi3 __udivdi3 _cygwin_istext_for_stdio The errors are below: /usr/lib/libg.a(vfprintf.o): In function `vfprintf_r': /home/Habacker/src/cygwin-1.3.2-1/build/i686-pc-cygwin/newlib/libc/stdio/ ../../. ./../../src/newlib/libc/stdio/vfprintf.c:774: undefined reference to `__umoddi3' /home/Habacker/src/cygwin-1.3.2-1/build/i686-pc-cygwin/newlib/libc/stdio/ ../../. ./../../src/newlib/libc/stdio/vfprintf.c:775: undefined reference to `__udivdi3' /usr/lib/libg.a(stdio.o): In function `_stextmode': /home/Habacker/tmp/kde/cygwin-1.3.2-1/build/i686-pc-cygwin/newlib/libc/st dio/../ ../../../../src/newlib/libc/stdio/stdio.c:127: undefined reference to `_cygwin_i stext_for_stdio' make: *** [libgd.so.2.0.0] Error 1 In all seriousness, 'nm' on the available libraries will tell you this. But I'm going to guess you won't find what you want. It looks to me like you have two (other) problems: 1. You're building with against some old Cygwin DLL code 2. You're trying to build the GNU C library You can rectify (1). Good luck with (2). You'll need it! ;-) Larry Hall [EMAIL PROTECTED] RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ Pinky, you've left the lens cap of your mind on again. - The Brain = Preferred Resources (314) 567-7600 phone 701 Emerson rd. (314) 993-6699 fax Suite 475 [EMAIL PROTECTED] St. Louis, MO 63141 = -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
vim doesn't quite get backslash-separated paths right
If you run vim with c:\temp\foo it complains E303: Unable to open swap file for c:\temp\foo, recovery impossible However, it then manages to correctly write the file out to the indicated path. Looking at strace shows it trying to open a file named /tmp/c:\temp\foo.swp; it thinks the whole path is a relative name in the current directory. This is a problem if you set $EDITOR to vim and then have non-Cygwin programs invoke vim. Chris Metcalf -- InCert Software -- 1 (617) 621 8080 [EMAIL PROTECTED] -- http://www.incert.com/~metcalf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: cygwin mentors? Was: bash and the suid bit
Hi Richard, if it's that important for your company's project (that you work like me 50% of each 25h day 8-) why don't you pay Red Hat per hour or day, so Corinna or Chris work for you in their prime time? -Original Message- From: Richard Troy [mailto:[EMAIL PROTECTED]] Sent: Donnerstag, 18. April 2002 17:45 To: Corinna Vinschen Subject: Re: cygwin mentors? Was: bash and the suid bit [Heribert] [snip] You may operate under the assumption that it's left-over minutes in the day that are being applied, and you're probably right for most everyone else. However, that's not what I'm proposing. If I attempt this, it will be during my work day, which, at the present time, comprises about 5AM to midnight every day, including weekends and most holidays - aren't startup companies fun? -wink- ...I need this other code to run on a Windows Box (NT/2k and later), and it's a high priority. [Heribert] [snip] -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Where is the manual to manually install cygwin in Windows 2000
From: Larry Hall (RFK Partners, Inc) [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 8:35 PM To: Lawrence W. Smith; '[EMAIL PROTECTED]' Subject: RE: Where is the manual to manually install cygwin in Windows 200 0 At 01:18 PM 4/19/2002, Lawrence W. Smith wrote: I was attempting to offer a new direction that may have been overlooked from your perspective but clearly the experiences and or suggestions of users are of little consequence to you. Although you responded specifically to Chris's message, I want to pick up on this statement since it's important and I want to make sure the key point here gets clarified. The first part of this sentence gets right to the heart of the matter. I think I can use it to help explain why you may have felt slighted (by me) for any (my) response. This is actually not a new idea at all for setup. It has been talked about before (as you can check in the email archives if you want) and is something for which there is already rudimentary support already in setup. So perhaps the response you needed to hear is, Yes, we know. We're working on it. It will be there someday. I thought I made the essentials of that statement in my original response. Sorry for not being more clear before. Thank you for the clarification though I didn't feel at all slighted by anything you stated. You might want to review the prose at http://cygwin.com/lists.html and substitute suggestion for question. snip Thank you. Lawrence -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Bug with /cygdrive/X in binmode
I'm having trouble mounting some of my drives in binmode. As an ordinary
user, I tried:
mount -b -f E: /cygdrive/e
To mount the E: drive in binmode. Mount reports:
$ mount
C:\cygwin\bin on /usr/bin type system (textmode)
C:\cygwin\lib on /usr/lib type system (textmode)
C:\cygwin on / type system (textmode)
E: on /cygdrive/e type user (binmode)
c: on /cygdrive/c type user (textmode,noumount)
d: on /cygdrive/d type user (textmode,noumount)
z: on /cygdrive/z type user (textmode,noumount)
Writing to files under /cydrive/e still converts \n to \r\n. I used the
following test program (testNL.c):
#include stdio.h
main ()
{
FILE *fd;
fd = fopen(HelloWorld, w);
fprintf(fd, Hello world\n);
}
Compiled with:
gcc -g testNL.c -o testNL
Test results:
cd /cygdrive/e/Partage/Images
testNL
od -c HelloWorld
000 H e l l o w o r l d \r \n
015
However, creating another binary mount point, things work as they should:
mkdir /Partage
mount -b E:/Partage /Partage
$ mount
C:\cygwin\bin on /usr/bin type system (textmode)
C:\cygwin\lib on /usr/lib type system (textmode)
E:\Partage on /Partage type user (binmode)
C:\cygwin on / type system (textmode)
E: on /cygdrive/e type user (binmode)
c: on /cygdrive/c type user (textmode,noumount)
d: on /cygdrive/d type user (textmode,noumount)
z: on /cygdrive/z type user (textmode,noumount)
cd /Partage/Images
testNL
od -c HelloWorld
000 H e l l o w o r l d \n
014
It seems that users cannot remount their drives in binmode but only
subdirectories.
cygwin version is 1.3.10-1
André Bleau, ing., associé de recherche
[EMAIL PROTECTED]
Laboratoire de recherche en imagerie et orthopédie (LIO)
École de technologie supérieure (ETS)
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
RE: Bug in setup.exe 2.194.2.24
-Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 5:38 AM To: [EMAIL PROTECTED] Subject: Re: Bug in setup.exe 2.194.2.24 On Fri, Apr 19, 2002 at 11:28:19AM -0700, Randall R Schulz wrote: I think to generalize, the current Setup.exe offers to download based on which packages are currently installed, not on which packages are present in the local download area(s). I hate to say it but that sounds like a bug to me. I can't remember if this is new behavior, though. Is it? It's a bug. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bug in setup.exe 2.194.2.24
On Fri, Apr 19, 2002 at 08:33:02PM +0100, Alan Hourihane wrote: On Fri, Apr 19, 2002 at 11:22:08AM -0700, Michael A Chase wrote: On Fri, 19 Apr 2002 18:41:04 +0100 Alan Hourihane [EMAIL PROTECTED] wrote: I think this is because you haven't installed the packages yet. I think setup.exe gets the current version information from the installed package not the download directory. This isn't the way it used to work, and shouldn't in my opinion. I think you're right and I agree. setup.exe should know what it's downloaded and not installed. Yep. I thought I added code to do that in the previous version but it's been so long that I'm not sure. And, (bwahaha) I don't have time to look into this myself right now. However, if Robert indicates that this is not the desired behavior then maybe someone else (*cough*, Michael, *cough*) might have time to look into this? cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Setup.exe bugreport
Hi, while looking for the new Xfree86 packages in my local package directory (in my case D:\cyg-install), I see that packages are saved in a curious directory since March 22th. Its name is : D:\cyg-install\ftp%3a%2f%2fmirrors.rcn.net%2fmirrors%2fsources.redhat.com%2fcygwin No package appears to be updated in normal directories like D:\cyg-install\contrib I always use the net version of setup.exe, i don't have a local copy.I'm running Cygwin under WinME. ___ Do You Yahoo!? -- Une adresse yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bug in setup.exe 2.194.2.24
Christopher Faylor [EMAIL PROTECTED] wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... On Fri, Apr 19, 2002 at 11:28:19AM -0700, Randall R Schulz wrote: I think to generalize, the current Setup.exe offers to download based on which packages are currently installed, not on which packages are present in the local download area(s). I hate to say it but that sounds like a bug to me. I can't remember if this is new behavior, though. Is it? That doesn't sound like new behavior (although I'm not certain). I don't think that's a bug, though -- that sounds like useful functionality. The problem isn't that setup bases its decision of what to download on what's installed, it's that it doesn't ALSO base its decision on what's already downloaded. -jt -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Why did you guys break EVERYTHING...
I'm sure you won't put this in the intelligent question genre but... I've been using cygwin for years and I brag about it and make all my teammates install it and make my managers refuse to piss away money on MKS... Well, I think that party's over. I just installed the new distribution and every one (and I mean EVERY GODDAMN ONE) of my scripts that call any of your routines that need to know what a host or a directory are f#$king broke. What in god's name is /usr/local/bin on a windows machine? Why don't you UNIX weeneies get a grip. F#$king fix it. It used to be great. Now I can't even change a directory. I've gone back to your old, unsupported code until we can find the money to equip our team with MKS for $400 a throw. Thanks for making a great product unusable. Sincerely, Barry Schwartz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Offer for killall-script
In the cygwin-apps I have seen some messages
http://sources.redhat.com/ml/cygwin-apps/2002-01/msg00340.html about a killall
util, which was going to be part of the cygutils packages but was waiting
because of licensing problems.
For killall I'm using a good working script for about a half year. Perhaps
anyone like this to integrate in the cygutils package. This script allows
killing more than one task, because it does a grep with the first param.
syntax: killall taskname | tasknamepart
$ cat /bin/killall
ps -ea | grep $1 | gawk '$1 ~ /^[^SI]/ { system(kill -9 $1); }'
Regards
Ralf Habacker
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
RE: Where is the manual to manually install cygwin in Windows 2000
-Original Message- From: Lawrence W. Smith [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 3:19 AM Not entirely true sometimes it improves sometimes it meanders down a blind alley or two granted. It's free software as a nobody user I accept its oddities and enjoy it's strengths, I'd like to contribute some constructive feedback but clearly that's not welcome. Actually it is welcome. Command line based installs are desirable. There is code in setup.exe to allow contributors to add command line options quite easily. I'm putting the finishing core touches on a library to make that simpler still. (getopt based to leverage that, but with OOD). Why doesn't it? Run setup on each workstation. I don't think that's terribly scalable. Agreed - thus the push for command line options. If that's too hard, then copy the download directory around to multiple workstations. Perhaps far more useful would be provide a cmdline mode to setup.exe offering a more flexible install method, scaleable to multiple installations and capable of saving a specific bundle of packages as an install set and then reapplying those with a single commandline across a list of boxes. Sure. How us get there. Others share your vision, I'm sure if you colelctively put in 3 command line options each, and sent in the patches, we would get there very quickly. neither is it intended to solicit the perennial go code it yourself, we're too busy, response It's not about business (sic). It's about the model. I'm the setup.exe maintainer - that does not mean that I volunteered to code the entire thing, and there have been some fantastic net contributors who have put in a lot of effort. They have been addressing the things that interest them. If no-one actively coding on setup.exe finds what you propose interesting enough to provide a gift of code, then ... no one will. Thus you can either attempt to get us interested, or join us as a interested party. As a for instance of the consequences of your approach: How would you suggest the mere mortals should clear out old versions of packages after say 4 or 5 revisions are sitting scattered across directory trees based on 6 different mirrors used by a particular user over a 2 year period? find -mtime 180 | xargs would be a good start (as a simple approach). Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bug in setup.exe 2.194.2.24
Christopher Faylor wrote on Friday, April 19, 2002 8:38 PM: On Fri, Apr 19, 2002 at 11:28:19AM -0700, Randall R Schulz wrote: I think to generalize, the current Setup.exe offers to download based on which packages are currently installed, not on which packages are present in the local download area(s). I hate to say it but that sounds like a bug to me. I can't remember if this is new behavior, though. Is it? Not so new - I've already reported this twice: http://sources.redhat.com/ml/cygwin/2002-03/msg01115.html http://sources.redhat.com/ml/cygwin/2002-03/msg01704.html Since noone acknowledged it was a bug I've been assuming it was a (rather strange to me) design feature. -- Cliff -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bug in setup.exe 2.194.2.24
On Fri, 19 Apr 2002 18:01:34 -0400 Christopher Faylor [EMAIL PROTECTED] wrote: On Fri, Apr 19, 2002 at 08:33:02PM +0100, Alan Hourihane wrote: setup.exe should know what it's downloaded and not installed. Yep. I thought I added code to do that in the previous version but it's been so long that I'm not sure. And, (bwahaha) I don't have time to look into this myself right now. However, if Robert indicates that this is not the desired behavior then maybe someone else (*cough*, Michael, *cough*) might have time to look into this? I'll look into it this evening. Not sure if I'll be able to figure it out though. I seem to have trouble leaving the old procedural paradigm. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Why did you guys break EVERYTHING...
Without ANY example of what you are calling, there is NO way that assistance can be provided. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Bug in setup.exe 2.194.2.24
I've noticed similar behaviour. I always use Download from Internet to get a local disk image on a zip disk, which I can then use to update cygwin on several machines. However I've sometimes got things out of sync and can't download local copies of the package depending on what computer I'm downloading from. E. At 06:41 PM 19/04/02 +0100, Alan Hourihane wrote: Hi, I'm wondering if I've found a bug in setup.exe. I'm using 2.194.2.24 and when I go through Download from Internet and download the new components. It downloads them fine. Next, I re-run setup.exe and I go through Download from Internet again, (but this was by accident) and it says that the same files are ready to be downloaded and proceeds to re-download them all again. If I Install from Local Directory first it clears the problem. Alan. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Bug in setup.exe 2.194.2.24
From: Randall R Schulz [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 9:43 PM To: [EMAIL PROTECTED] Subject: Re: Bug in setup.exe 2.194.2.24 Chris, At 12:38 2002-04-19, you wrote: On Fri, Apr 19, 2002 at 11:28:19AM -0700, Randall R Schulz wrote: I think to generalize, the current Setup.exe offers to download based on which packages are currently installed, not on which packages are present in the local download area(s). I hate to say it but that sounds like a bug to me. I can't remember if this is new behavior, though. Is it? I hesitate to say with 100% certainty, but I'm fairly sure it is new behavior. Randall Schulz Last 2 versions behave like that but ver 2.29 didn't just tested it. It offers to d/l packages even if not installed whereas setup 2.194.2.22 and 24 default to skip for packages not installed. hth Lawrence -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Bug in setup.exe 2.194.2.24
-Original Message- From: Christopher Faylor [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 8:02 AM On Fri, 19 Apr 2002 18:41:04 +0100 Alan Hourihane [EMAIL PROTECTED] wrote: I think this is because you haven't installed the packages yet. I think setup.exe gets the current version information from the installed package not the download directory. Setup gets the version of the current installed package from the local information - which it should. It also gets the 'curr' package information from one or more setup.ini files. ... And, (bwahaha) I don't have time to look into this myself right now. Don't worry - I've got a little time right now and am actively hacking cygwinrelated stuff this weekend. However, if Robert indicates that this is not the desired behavior http://cygwin.com/ml/cygwin/2002-04/msg01048.html Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Bug in setup.exe 2.194.2.24
-Original Message- From: Cliff Hones [mailto:[EMAIL PROTECTED]] Sent: Saturday, April 20, 2002 9:10 AM Since noone acknowledged it was a bug I've been assuming it was a (rather strange to me) design feature. Actually, I acknowledged it as a bug, but one I couldn't repeat until I was given an exact recipe on cygwin-apps. I've jet to track it down and squash it though. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Why did you guys break EVERYTHING...
umm calm down, maybe you could post more of your scripts and what they do and expound on this line What in god's name is /usr/local/bin on a windows machine? do you mean WHERE? not what? - Original Message - From: Schwartz, Barry [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, April 19, 2002 3:46 PM Subject: Why did you guys break EVERYTHING... I'm sure you won't put this in the intelligent question genre but... I've been using cygwin for years and I brag about it and make all my teammates install it and make my managers refuse to piss away money on MKS... Well, I think that party's over. I just installed the new distribution and every one (and I mean EVERY GODDAMN ONE) of my scripts that call any of your routines that need to know what a host or a directory are f#$king broke. What in god's name is /usr/local/bin on a windows machine? Why don't you UNIX weeneies get a grip. F#$king fix it. It used to be great. Now I can't even change a directory. I've gone back to your old, unsupported code until we can find the money to equip our team with MKS for $400 a throw. Thanks for making a great product unusable. Sincerely, Barry Schwartz -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
