Re: gnome-vfs problems with XP SP2
Walter Landry wrote: As I mentioned in another message, I managed to get gnome-vfs working by removing all traces of gconfd. However, I have to do this periodically, because gconfd hangs around too long. If I run my program, then gconfd doesn't exit when the program exits. So when I exit cygwin and log out, gconfd leaves around stale locks. Am I doing something wrong? No, this is one problem remaining with gconfd, I use a startup script to start the desktop which kills gconfd if it doesn't shutdown when the desktop is closed and removes the lockfiles before starting up anything. Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Share rootfs by nfs-server?
How can I share a root filesystem using Windows? I've had 2 ideas on how to approach this: - using nfs-server and a ext3 driver - compress the entire 18gb into one big file using cramfs and share that. Is there a better way? The first approach I doubt will work because even Paragons ext3 driver doesn't do permissions that well. The last approach seems messy and even then I'm not sure it will work because I'm not sure how cramfs and similar compressed filesystems uncompress. To add some detail about the `thin`client mounting the exported root filesystem: - will be running off a 64mb flash card with Mozilla so with little space will be left. - 320mb RAM - 1ghz - small and silent I could have 3 computers; Windows, linux server and a thinclient but I don't want to introduce another computer into the house, trying to be effiecient on electric. I've sent a similar question to the ltsp to see what they say. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Help! Need B.20.1 src
On Sat, 2005-22-01 at 20:22 -0500, Christopher Faylor wrote: On Sat, Jan 22, 2005 at 05:17:44PM -0800, Brian Dessent wrote: John Mellor wrote: Correct me if I'm mistaken, but if I'm going to make a few dollars off of a non-free something that links in an open source library, I need to provide the source for the open-source parts with the product, or fall afoul of the LGPL. So, to make everybody happy, I believe that all I need to add, is to provide the source for cygwin1.dll to the Customer. I don't know if the ancient Bxx series was LGPL, but the current Cygwin source is GPL which means you must provide not only the Cygwin DLL source but also all the source of your app that links to it. There is a mailing list to discuss this: cygwin-licensing at cygwin dot com. I think that cygwin has been GPL since early 1997. So, you're right. I can't believe I missed this. Anything that uses the Cygwin DLL is GPLed. In fact, I cannot ship the source for the app if I wanted to, as that would then publish some of the Customer's proprietary trade secrets. However, if I read the specific version of the GPL that is being used for cygwin correctly, then it says: In accordance with section 10 of the GPL, Red Hat permits programs whose sources are distributed under a license that complies with the Open Source definition to be linked with libcygwin.a/cygwin1.dll without libcygwin.a/cygwin1.dll itself causing the resulting program to be covered by the GNU GPL. This means that you can port an Open Source(tm) application to cygwin, and distribute that executable as if it didn't include a copy of libcygwin.a/cygwin1.dll linked into it. Note that this does not apply to the cygwin DLL itself. If you distribute a (possibly modified) version of the DLL you must adhere to the terms of the GPL, i.e. you must provide sources for the cygwin DLL. I believe that my app meets this criteria, and this then prevents me from being between a rock and a hard place;^) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Help! Need B.20.1 src
On Sat, 2005-22-01 at 20:06 -0500, Christopher Faylor wrote: On Sat, Jan 22, 2005 at 08:00:00PM -0500, John Mellor wrote: On Sat, 2005-22-01 at 18:44 -0500, Christopher Faylor wrote: On Sat, Jan 22, 2005 at 05:23:41PM -0500, John Mellor wrote: I'm looking for the source for the cygwin1.dll b.20.1.19 version, put out in 1999. The CVS tree on the RedHat site only goes back 4 years, and I guess they just threw everything before that in the bit bucket. Anybody got a copy, or know where I can get it? How about humoring us and telling us why you think you need this. Some time ago, I built a package that links in this DLL that somebody found useful, and now actually wants to pay me for. Having to put food on the table, I'd like to oblige them. Rather than upgrading to the latest-and-greatest, and all the work involved in changing APIs, etc., I just want to ship the one that I've got, seeing as it works perfectly well. Thanks for satisfying my curiousity. We go to quite some effort to make sure that nothing changed from B20 until now, so you should just be able to send your customer the latest cygwin DLL + sources without resorting to finding an almost six year old version of cygwin1.dll. There is no need to change APIs. Any idea where I can get it now? Nope. I wrote all of the warnings on the home page at http://cygwin.com/ : The last Bxx release was in December 1998. The Bxx releases are no longer available. In fact, older versions of the DLL or utilities are not usually available on this web site. Any cygwin program built from December 1998 onward should work correctly with newer DLLs. Thanks for the quick reply! I'll try running it with the latest dll underneatch instead of the original one, just to make sure nothing got unintentionally broken. If that solves my problem, cool. Thanks! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Help! Need B.20.1 src
On Jan 23 09:28, John Mellor wrote: On Sat, 2005-22-01 at 20:22 -0500, Christopher Faylor wrote: On Sat, Jan 22, 2005 at 05:17:44PM -0800, Brian Dessent wrote: I don't know if the ancient Bxx series was LGPL, but the current Cygwin source is GPL which means you must provide not only the Cygwin DLL source but also all the source of your app that links to it. There is a mailing list to discuss this: cygwin-licensing at cygwin dot com. I think that cygwin has been GPL since early 1997. So, you're right. I can't believe I missed this. Anything that uses the Cygwin DLL is GPLed. In fact, I cannot ship the source for the app if I wanted to, as that would then publish some of the Customer's proprietary trade secrets. If you linked your application against the Cygwin DLL, then this application *is* GPL'd. Full stop up to this point. You don't have to publish the sources to the world, but you have to publish your sources to your customer. Your customer has the right to get the source code of your application and the Cygwin DLL. If you didn't do this so far, you're violating the license. However, if I read the specific version of the GPL that is being used for cygwin correctly, then it says: In accordance with section 10 of the GPL, Red Hat permits programs whose sources are distributed under a license that complies with the Open Source definition to be linked with libcygwin.a/cygwin1.dll without libcygwin.a/cygwin1.dll itself causing the resulting program to be covered by the GNU GPL. [...] I believe that my app meets this criteria, and this then prevents me from being between a rock and a hard place;^) I don't see how that applies to your application. The above paragraph only mentions that open source applications are excempted from that rule, not proprietary software as yours. You have two choices: - Comply with the GPL in one way or the other, which always means your application is also GPLed and you have to open the source code to your customer. - Or, you ask Red Hat for a special Cygwin License according to this paragraph on http://cygwin.com/licensing.html: Red Hat sells a special Cygwin License for customers who are unable to provide their application in open source code form. For more information, please see: http://www.redhat.com/software/cygwin/, or call +1-866-2REDHAT ext. 45300 (toll-free in the US) Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin@cygwin.com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
FW: whois and man packages
Hi: I am new to CYGWIN. I am an experienced UNIX and WINDOWS user. I joined this community at the request of a fellow employee since I am designing my own aircraft but ran into a problem using AutoCAD 3D. He suggested I use some of the free source code available on the Internet for my 3D modeling. I am running Windows 2000 Professional Thus far I like the feel of CYGWIN, but I have a question. I must not have downloaded the packages, WHOIS, or MAN. When I go to the PACKAGE site all I get are listing and not the source codes, etc. What am I doing wrong? Thanks for your time. Tony -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: update on hyperthreading system for cgf
On Sat, Jan 22, 2005 at 10:57:32PM -0800, David Christensen wrote: I wrote: http://secure.newegg.com/app/WishR.asp?ID=1251752 Christopher Faylor wrote: Well, yeah. I sort of need a hard disk, though and is that system *guaranteed* to exhibit this problem? This motherboard, case, and power supply are the core of my desktop machine and the machines I build for clients. The 2.4C processor and 256 MB of RAM represent skimping to get the price down to near $400.00. Honestly, if you're going to build a new hyperthreading box for yourself, spend the money to do it right. You're a developer and power user; time is money. $600 vs. $400 now will save you countless hours over the next several years. Huh? I can only spend as much money as I have. Why do you think I was asking for a good system in the $400 price range? I don't think you've been paying attention. I don't *need* a new system. I have perfectly adequate systems running linux. My cygwin system is also perfectly adequate for everything but checking this particular problem. When I was asking for feedback on a $400 system, I meant that I wanted a system that was actually usable. A system without a hard drive is not usable. Suggesting another $186 worth of improvements after I had mentioned my price limitations isn't really very helpful. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Multiple installations and 3PPs (FAQ alert)
On Sat, 22 Jan 2005 11:32:08 -0800, Joshua Daniel Franklin wrote: I like the idea of it at least saving mounts. And the paths should work (note the bin). :) The only thing I would change is to save the state of the mounts within the uninstall script (just before uninstalling), rather than the state at install time when /etc/postinstall/gen-uninst.sh was run. I also added a warning at the beginning, since this performs such a drastic operation, even though the UN*X philosophy is to do what the user says, no matter what, as in rm * .o: -- BEGIN gen-uninst.sh -- #!/bin/sh CYGDIR=`/bin/cygpath -aw /` cat /uninstall.bat EOF @echo Warning! This will remove all of Cygwin! @echo Use Ctrl-C or Ctrl-Break now to abort. Any other key will continue. @pause $CYGDIR\\bin\\mount -m %TEMP%\\saved-mounts.bat $CYGDIR\\bin\\umount -s -A $CYGDIR\\bin\\umount -A copy $CYGDIR\\bin\\cygwin1.dll $CYGDIR\\bin\\regtool.exe %TEMP% $CYGDIR\\bin\\rm -rf / del /s $CYGDIR %TEMP%\\regtool remove /HKLM/Software/Cygnus Solutions %TEMP%\\regtool remove /HKCU/Software/Cygnus Solutions del %TEMP%\\cygwin1.dll %TEMP%\\regtool.exe EOF --- END gen-uninst.sh --- Steve -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Help! Need B.20.1 src
On Sun, Jan 23, 2005 at 09:28:45AM -0500, John Mellor wrote: On Sat, 2005-22-01 at 20:22 -0500, Christopher Faylor wrote: On Sat, Jan 22, 2005 at 05:17:44PM -0800, Brian Dessent wrote: John Mellor wrote: Correct me if I'm mistaken, but if I'm going to make a few dollars off of a non-free something that links in an open source library, I need to provide the source for the open-source parts with the product, or fall afoul of the LGPL. So, to make everybody happy, I believe that all I need to add, is to provide the source for cygwin1.dll to the Customer. I don't know if the ancient Bxx series was LGPL, but the current Cygwin source is GPL which means you must provide not only the Cygwin DLL source but also all the source of your app that links to it. There is a mailing list to discuss this: cygwin-licensing at cygwin dot com. I think that cygwin has been GPL since early 1997. So, you're right. I can't believe I missed this. Anything that uses the Cygwin DLL is GPLed. In fact, I cannot ship the source for the app if I wanted to, as that would then publish some of the Customer's proprietary trade secrets. However, if I read the specific version of the GPL that is being used for cygwin correctly, then it says: In accordance with section 10 of the GPL, Red Hat permits programs whose sources are distributed under a license that complies with the Open Source definition to be linked with libcygwin.a/cygwin1.dll without libcygwin.a/cygwin1.dll itself causing the resulting program to be covered by the GNU GPL. This means that you can port an Open Source(tm) application to cygwin, and distribute that executable as if it didn't include a copy of libcygwin.a/cygwin1.dll linked into it. Note that this does not apply to the cygwin DLL itself. If you distribute a (possibly modified) version of the DLL you must adhere to the terms of the GPL, i.e. you must provide sources for the cygwin DLL. I believe that my app meets this criteria, and this then prevents me from being between a rock and a hard place;^) I think it's already been pointed out that licensing discussions should go to cygwin-licensing. I've reset the reply-to for this message. However, when you mention being unable to ship the source, it is hard to see how you could possibly be compliant with anythin that resembles an open source license. FWIW, you don't have to provide the source code to the world. You just have to provide source code to anyone who gets the binaries. Also, if you truly are using B20.1, then the license was just GPL back then. The overriding of section 10 didn't happen until I had pleaded with Cygnus's CEO to allow this change. -- Christopher Faylor spammer? - [EMAIL PROTECTED] Cygwin Co-Project Leader[EMAIL PROTECTED] TimeSys, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygpng12.dll not found
At 04:03 PM 1/22/2005, you wrote: How can I get the cygpng12.dll? I got the libpng12 installed via setup.exe. But there is no cygpng12.dll See the FAQ entry: What packages should I download? Where are 'make', 'gcc', 'vi', etc? http://cygwin.com/faq/faq_toc.html#TOC13 So http://cygwin.com/cgi-bin2/package-grep.cgi?grep=cygpng12.dll If you've installed the latest libpng12, then you should search your disk for 'cygpng12.dll'. It's around somewhere. If it isn't, reinstall. If you didn't actually install the latest 'cygpng12.dll' (maybe you just downloaded it but didn't install it), do so. If after reviewing the above you still can't figure out what's wrong, please read and follow the problem reporting guidelines at http://cygwin.com/problems.html. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin Time Machine
At 02:19 AM 1/23/2005, you wrote: I'm probably going to regret this :) For some time, I've been keeping a private mirror of Cygwin for my own personal use. Unlike other mirrors, I've been keeping all of the versions of all packages, along with a revision of setup.ini to go with it. Now, call me crazy (and I know you already do :), but since Cygwin Setup uses nothing more than setup.ini and the release/ directory, I thought: why not provide a historical representation of Cygwin's package from which you can actually install from? Think of it as a time machine for going back to a previous version of Cygwin. And so, that's what I did. See http://www.fruitbat.org/Cygwin/index.html#cygwincirca This provides the details of how it works. Basically, it's a bunch of timestamp based URLs which allow you to install a specific snapshot of Cygwin. So, why am I doing this? Well, I actually have need of this for work. It saved me much time and effort, because I could install additional packages at the same level of what we already had installed, thus introducing less instability into our environments, and it gives us a chance to gradually upgrade. It's a cop-out, I know, and I can already see people tut-tut'ing at this, but on the plus side, it's kind of neat to see a form of historical review of Cygwin packages. My mirroring is done automatically each day, and the time machine is also automatically regenerated along with it to keep it up to date. I really only did this for my work, but thought perhaps someone else might find it useful or interesting. Unfortinately, it only goes back to April of 2002, though I actually have package versions going back further, but not the setup.ini to go with them. Once our work has migrated to a more current Cygwin, I might remove this, but for now it's useful to me. You forgot to mention the most important thing in your post. Anybody who visits and uses your archive should contact you directly for any support issues they have with using the software. This list can't entertain questions or help solve problems for those using software from your archive. You do have wording something like this at your web page but you know no one ever reads documentation. ;-) Good luck! -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: FW: whois and man packages
On Sun, 23 Jan 2005, Anthony W. (Tony) Parran wrote: Hi: I am new to CYGWIN. I am an experienced UNIX and WINDOWS user. I joined this community at the request of a fellow employee since I am designing my own aircraft but ran into a problem using AutoCAD 3D. He suggested I use some of the free source code available on the Internet for my 3D modeling. I am running Windows 2000 Professional Welcome to Cygwin. Hope you like it. Thus far I like the feel of CYGWIN, but I have a question. I must not have downloaded the packages, WHOIS, or MAN. When I go to the PACKAGE site all I get are listing and not the source codes, etc. What am I doing wrong? Thanks for your time. Tony Well, if by the package site you mean http://cygwin.com/packages/, it's only there to give you a listing of the available packages and their contents. If you need to install any of those packages, you should use the setup.exe tool that you used to install Cygwin originally (you can always get the current copy off http://cygwin.com/) and select any of the current mirrors. If you simply wish to run the application, you only need the binary package (the one selected by default), but you can also get the source packages (by checking the Src checkbox for the package). Now for your particular problem... The man package is in the Base category, and thus should have been installed by default. If you had problems with your installation, please review the Cygwin problem reporting guidelines at http://cygwin.com/problems.html and post the relevant details as described there. I would, however, first try to run /bin/man man from a Cygwin bash shell. As for whois, use the setup.exe tool to install the whois package (though if it's a typo and you meant to say whatis, that's probably the same problem as man, since they're both in the same package). HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
CPAN install of LWP::UserAgent
Hi, Just wondering if anyone else had problems installing LWP::UserAgent using CPAN. After multiple attempts to install Cygwin on Windows 98, and various adventrues about Perl running out of memory (I deleted 4G of space, did a full defrag and expanded the page file) during CPAN install, I'm now at the point where I'm failing the $r = new WWW::RebotRules::AnyDBM_File myrobot/2.0 $file; test. Guessing that it might be a permissions problem, I tried to specify a path for the test file, changed $file = test-$$; to $file = /home/tab/test-$$; This didn't work. I tried to find or create a world-writable directory that could be used, and was unable to do that. The latest suggestion I received via Perl Monks (http://perlmonks.org/index.pl?node_id=424312) was to bypass the entire group of tests. I'll do that, but I wanted to see if any Cygwin users had encountered similar problems. Thanks! Alex -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Share rootfs by nfs-server?
At 08:06 AM 1/23/2005, you wrote: How can I share a root filesystem using Windows? I've had 2 ideas on how to approach this: - using nfs-server and a ext3 driver - compress the entire 18gb into one big file using cramfs and share that. Is there a better way? The first approach I doubt will work because even Paragons ext3 driver doesn't do permissions that well. The last approach seems messy and even then I'm not sure it will work because I'm not sure how cramfs and similar compressed filesystems uncompress. To add some detail about the `thin`client mounting the exported root filesystem: - will be running off a 64mb flash card with Mozilla so with little space will be left. - 320mb RAM - 1ghz - small and silent I could have 3 computers; Windows, linux server and a thinclient but I don't want to introduce another computer into the house, trying to be effiecient on electric. I've sent a similar question to the ltsp to see what they say. It's pretty unclear from the above exactly what you're trying to share. If you just want to share the root of your Linux server to your Windows machine, just use Samba. If you have a partition local to your Windows machine that's formatted for Linux (ext2/ext3) and you want access to that from Windows, then you will need some kind of ext2/ext3 driver for Windows (Paragon is one commercial option). If you only need read access, there's others, including a user-space option called Explore2fs. But unless you can clearly relate your need back to something Cygwin-related, further discussion would be off-topic for this list. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Share rootfs by nfs-server?
I'll try and cut out all the detail to make things clear. Imagine I have only one computer. This computer is running Windows. Inside it there is a 2nd hard drive with a linux ext3 root partition. I want to make that available to other computers on the network. Yes, I can READ the partition using Paragon ext2anywhere and SHARE the result using samba that is built into Windows. However, by doing this all the files are seen as one owner - the person who mounted the partition. And that is the problem. On Sun, 23 Jan 2005 13:10:28 -0500, Larry Hall [EMAIL PROTECTED] wrote: At 08:06 AM 1/23/2005, you wrote: How can I share a root filesystem using Windows? I've had 2 ideas on how to approach this: - using nfs-server and a ext3 driver - compress the entire 18gb into one big file using cramfs and share that. Is there a better way? The first approach I doubt will work because even Paragons ext3 driver doesn't do permissions that well. The last approach seems messy and even then I'm not sure it will work because I'm not sure how cramfs and similar compressed filesystems uncompress. To add some detail about the `thin`client mounting the exported root filesystem: - will be running off a 64mb flash card with Mozilla so with little space will be left. - 320mb RAM - 1ghz - small and silent I could have 3 computers; Windows, linux server and a thinclient but I don't want to introduce another computer into the house, trying to be effiecient on electric. I've sent a similar question to the ltsp to see what they say. It's pretty unclear from the above exactly what you're trying to share. If you just want to share the root of your Linux server to your Windows machine, just use Samba. If you have a partition local to your Windows machine that's formatted for Linux (ext2/ext3) and you want access to that from Windows, then you will need some kind of ext2/ext3 driver for Windows (Paragon is one commercial option). If you only need read access, there's others, including a user-space option called Explore2fs. But unless you can clearly relate your need back to something Cygwin-related, further discussion would be off-topic for this list. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Multiple installations and 3PPs (FAQ alert)
On Sun, 23 Jan 2005, Steve Munson wrote: On Sat, 22 Jan 2005 11:32:08 -0800, Joshua Daniel Franklin wrote: I like the idea of it at least saving mounts. And the paths should work (note the bin). :) The only thing I would change is to save the state of the mounts within the uninstall script (just before uninstalling), rather than the state at install time when /etc/postinstall/gen-uninst.sh was run. I also added a warning at the beginning, since this performs such a drastic operation, even though the UN*X philosophy is to do what the user says, no matter what, as in rm * .o: -- BEGIN gen-uninst.sh -- #!/bin/sh CYGDIR=`/bin/cygpath -aw /` cat /uninstall.bat EOF @echo Warning! This will remove all of Cygwin! @echo Use Ctrl-C or Ctrl-Break now to abort. Any other key will continue. @pause $CYGDIR\\bin\\mount -m %TEMP%\\saved-mounts.bat $CYGDIR\\bin\\umount -s -A $CYGDIR\\bin\\umount -A copy $CYGDIR\\bin\\cygwin1.dll $CYGDIR\\bin\\regtool.exe %TEMP% $CYGDIR\\bin\\rm -rf / del /s $CYGDIR %TEMP%\\regtool remove /HKLM/Software/Cygnus Solutions %TEMP%\\regtool remove /HKCU/Software/Cygnus Solutions del %TEMP%\\cygwin1.dll %TEMP%\\regtool.exe EOF --- END gen-uninst.sh --- Ok, so now we have two new versions of this floating around: this and http://cygwin.com/ml/cygwin/2005-01/msg01092.html. The final solution will, hopefully, combine the best features of both (mostly the output messages/warnings, as they're the same otherwise, AFAICS). Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Share rootfs by nfs-server?
At 01:23 PM 1/23/2005, you wrote: I'll try and cut out all the detail to make things clear. Imagine I have only one computer. This computer is running Windows. Inside it there is a 2nd hard drive with a linux ext3 root partition. I want to make that available to other computers on the network. Yes, I can READ the partition using Paragon ext2anywhere and SHARE the result using samba that is built into Windows. However, by doing this all the files are seen as one owner - the person who mounted the partition. And that is the problem. OK, that's clearer. But it still doesn't clarify why you think this is a Cygwin issue. Cygwin does not provide an ext2/ext3 or cramfs file system driver. It is not (nor does it really need to be) a SAMBA server. So nothing about this question appears to be Cygwin-related and as such is off-topic for this list. You should consider asking your question in a Windows forum. FWIW, Explore2fs provides the UID/GID from Linux, if that's helpful to you. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: update on hyperthreading system for cgf
Christopher Faylor wrote: I don't think you've been paying attention. No, I haven't been following this entire thread. I've told you what I use and recommend, and shown that my system demonstrates the Cygwin HT bug. When I build computers, my goals are reliability first, price/performance second. I use good parts, and they're not cheap. Sorry that they don't fit within your budget. I don't *need* a new system. I have perfectly adequate systems running linux. Then rebuild one of them dual-boot. If you need another drive, then buy one. If you use mobile docks, then buy another drawer. $400 is more than enough. When I was asking for feedback on a $400 system, I meant that I wanted a system that was actually usable. If you want HT at $400, then you need to shop around for cheap mass produced systems -- e-Machines, Great Quality, Fry's Electronics specials, etc.. A key parameter that I failed to state in my test report is that I run Windows XP Professional SP2 with all current patches except Windows Journal Viewer. Has the Cygwin HT bug been reported on XP Home Edition? XP Home is what cheap computers are going to have. A critical dimension to this whole discussion is repeatability, or lack thereof. Myself and others have demonstrated the bug on our computers, yet still others (apparently, yourself) have been unable to reproduce it. The solution is configuration management and automation. Because Cygwin is not versioned at the distribution level, and because Cygwin cannot be easily and completely installed and uninstalled with scripts that depend solely on Windows, it is very difficult to reproduce and isolate the HT bug across multiple Cygwin deployments. These ideas have been beaten to death on this list in the past, and I don't want to raise them again. I am merely pointing out that here is an example of the price to be paid when such features are missing. Could you or other Cygwin developers debug the HT bug on my machine via ssh, without adversely impacting my system? p42800e is my primary desktop machine, and myself and my family members use it daily (including Cygwin). David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: CPAN install of LWP::UserAgent
Alex Beamish wrote: Just wondering if anyone else had problems installing LWP::UserAgent using CPAN. Yes: robot/ua-get..FAILED tests 2, 7 Failed 2/8 tests, 75.00% okay robot/ua..FAILED tests 2, 7 Failed 2/7 tests, 71.43% okay local/http-getFAILED tests 1-2, 15-20 Failed 8/20 tests, 60.00% okay local/httpFAILED tests 1-2 Failed 2/18 tests, 88.89% okay Failed Test Stat Wstat Total Fail Failed List of Failed - local/http-get.t 208 40.00% 1-2 15-20 local/http.t 182 11.11% 1-2 robot/ua-get.t 82 25.00% 2 7 robot/ua.t 72 28.57% 2 7 Failed 4/30 test scripts, 86.67% okay. 14/759 subtests failed, 98.16% okay. Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: update on hyperthreading system for cgf
On Sun, Jan 23, 2005 at 10:39:07AM -0800, David Christensen wrote: Christopher Faylor wrote: I don't think you've been paying attention. No, I haven't been following this entire thread. Fair enough. Bye, bye. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
precompiled header status
Group, what is the current status of precompiled headers under cygwin? The last post I read about this was http://sources.redhat.com/ml/cygwin/2004-10/msg01318.html - then silence! thx a bundle, H. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: CPAN install of LWP::UserAgent
On Sun, 23 Jan 2005 20:06:36 +0100, Gerrit P. Haase [EMAIL PROTECTED] wrote: Alex Beamish wrote: Just wondering if anyone else had problems installing LWP::UserAgent using CPAN. Yes: robot/ua-get..FAILED tests 2, 7 Failed 2/8 tests, 75.00% okay robot/ua..FAILED tests 2, 7 Failed 2/7 tests, 71.43% okay local/http-getFAILED tests 1-2, 15-20 Failed 8/20 tests, 60.00% okay local/httpFAILED tests 1-2 Failed 2/18 tests, 88.89% okay Failed Test Stat Wstat Total Fail Failed List of Failed - local/http-get.t 208 40.00% 1-2 15-20 local/http.t 182 11.11% 1-2 robot/ua-get.t 82 25.00% 2 7 robot/ua.t 72 28.57% 2 7 Failed 4/30 test scripts, 86.67% okay. 14/759 subtests failed, 98.16% okay. OK .. what did you do then? I finally had to delete the test that was failing and hope that LWP::UserAgent would be OK. It appears that it was, as I finally got my script to login to a web site using https and upload a file for processing. Thanks for your response! Alex Beamish -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: 1.5.12: find with -iregex is case-sensitive
I found a workaround: Remake findutils 4.1.7-4 from source, and use /usr/local/bin/find.exe instead of /usr/bin/find.exe. Here's what I did: $ cd /usr/src/findutils-4.1.7-4 $ ./configure $ make $ make install $ mv /usr/bin/find.exe /usr/bin/find.exe.old $ cd /bin $ ln -s /usr/local/bin/find.exe Now the test procedure gives correct case-insensitive results: $ find test -iregex .*file.* test/file-a test/File-b Even with the -iregex option, the find command performs case-sensitive matching. Test procedure: $ mkdir test $ touch test/file-a $ touch test/File-b $ find test | grep -i .*file.* test/file-a test/File-b $ find test -iregex .*file.* test/file-a $ find test -iregex .*File.* test/File-b I'm using Cygwin 1.5.12-1 under Windows XP Professional Ver 5.1 Build 2600 Service Pack 1, findutils 20041227-1. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
problems with tmpnan naming using octave.
while using octave on cygwin, i can't use imread command. it complains it can't open file: c:\cygwin\tmp/oct-22fb00.0 i think the problem comes becuse of the \ or / direction. tmpnam() gives: c:\cygwin\tmp/oct-22fb00.0 any sugestions? thanks, Eran. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: CPAN install of LWP::UserAgent
Alex Beamish wrote: On Sun, 23 Jan 2005 20:06:36 +0100, Gerrit P. Haase [EMAIL PROTECTED] wrote: Alex Beamish wrote: Just wondering if anyone else had problems installing LWP::UserAgent using CPAN. Yes: robot/ua-get..FAILED tests 2, 7 Failed 2/8 tests, 75.00% okay robot/ua..FAILED tests 2, 7 Failed 2/7 tests, 71.43% okay local/http-getFAILED tests 1-2, 15-20 Failed 8/20 tests, 60.00% okay local/httpFAILED tests 1-2 Failed 2/18 tests, 88.89% okay Failed Test Stat Wstat Total Fail Failed List of Failed - local/http-get.t 208 40.00% 1-2 15-20 local/http.t 182 11.11% 1-2 robot/ua-get.t 82 25.00% 2 7 robot/ua.t 72 28.57% 2 7 Failed 4/30 test scripts, 86.67% okay. 14/759 subtests failed, 98.16% okay. OK .. what did you do then? Go to the build directory and issue: $ make UNINST=1 install or call in the cpan shell: cpan force install libwww I finally had to delete the test that was failing and hope that LWP::UserAgent would be OK. It appears that it was, as I finally got my script to login to a web site using https and upload a file for processing. Thanks for your response! That is another option I usually don't use. Gerrit -- =^..^= -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Fw: bug in texi2dvi, and hack patch
Greetings,
Regarding texi2dvi and cygwin, please see if the new version (below) works.
(Akim, I'm cc-ing you since you've worked so much on texi2dvi, not to
mention autoconf, that I figured you might spot problems.)
Thanks,
karl
#! /bin/sh
# texi2dvi --- produce DVI (or PDF) files from Texinfo (or LaTeX) sources.
# $Id: texi2dvi,v 1.37 2005/01/20 22:45:52 karl Exp $
#
# Copyright (C) 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2001,
# 2002, 2003, 2004, 2005 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, you can either send email to this
# program's maintainer or write to: The Free Software Foundation,
# Inc.; 59 Temple Place, Suite 330; Boston, MA 02111-1307, USA.
#
# Original author: Noah Friedman.
#
# Please send bug reports, etc. to [EMAIL PROTECTED]
# If possible, please send a copy of the output of the script called with
# the `--debug' option when making a bug report.
# This string is expanded by rcs automatically when this file is checked out.
rcs_revision='$Revision: 1.37 $'
rcs_version=`set - $rcs_revision; echo $2`
program=`echo $0 | sed -e 's!.*/!!'`
version=texi2dvi (GNU Texinfo 4.8) $rcs_version
Copyright (C) 2004 Free Software Foundation, Inc.
There is NO warranty. You may redistribute this software
under the terms of the GNU General Public License.
For more information about these matters, see the files named COPYING.
usage=Usage: $program [OPTION]... FILE...
Run each Texinfo or LaTeX FILE through TeX in turn until all
cross-references are resolved, building all indices. The directory
containing each FILE is searched for included files. The suffix of FILE
is used to determine its language (LaTeX or Texinfo).
Makeinfo is used to perform Texinfo macro expansion before running TeX
when needed.
Operation modes:
-b, --batch no interaction
-c, --clean remove all auxiliary files
-D, --debug turn on shell debugging (set -x)
-h, --help display this help and exit successfully
-o, --output=OFILE leave output in OFILE (implies --clean);
Only one input FILE may be specified in this case
-q, --quiet no output unless errors (implies --batch)
-s, --silentsame as --quiet
-v, --version display version information and exit successfully
-V, --verbose report on what is done
TeX tuning:
-@ use @input instead of \input; for preloaded Texinfo
-e, -E, --expand force macro expansion using makeinfo
-I DIR search DIR for Texinfo files
-l, --language=LANG specify the LANG of FILE (LaTeX or Texinfo)
-p, --pdfuse pdftex or pdflatex for processing
-r, --recode call recode before TeX to translate input characters
-t, --command=CMDinsert CMD in copy of input file
or --texinfo=CMDmultiple values accumulate
The values of the BIBTEX, LATEX (or PDFLATEX), MAKEINDEX, MAKEINFO,
TEX (or PDFTEX), TEXINDEX, and THUMBPDF environment variables are used
to run those commands, if they are set. Any CMD strings are added
after @setfilename for Texinfo input, in the first line for LaTeX input.
Email bug reports to bug-texinfo@gnu.org,
general questions and discussion to help-texinfo@gnu.org.
Texinfo home page: http://www.gnu.org/software/texinfo/;
# Initialize variables for option overriding and otherwise.
# Don't use `unset' since old bourne shells don't have this command.
# Instead, assign them an empty value.
batch=false # eval for batch mode
clean=
debug=
escape='\'
expand= # t for expansion via makeinfo
miincludes= # makeinfo include path
oformat=dvi
oname= # --output
quiet= # by default let the tools' message be displayed
recode=false
set_language=
textra= # Extra TeX commands to insert in the input file.
textra_cmd= # sed command to insert TEXTRA where appropriate
tmpdir=${TMPDIR:-/tmp}/t2d$$ # avoid collisions on 8.3 filesystems.
txincludes= # TEXINPUTS extensions, with trailing colon
txiprereq=19990129 # minimum texinfo.tex version with macro expansion
verbose=false # echo for verbose mode
orig_pwd=`pwd`
# Systems which define $COMSPEC or $ComSpec use semicolons to separate
# directories in TEXINPUTS -- except for Cygwin, where it might be inherited.
if test -n $COMSPEC$ComSpec uname | grep -iv cygwin /dev/null; then
path_sep=;
else
path_sep=:
fi
# Pacify verbose cds.
CDPATH=${ZSH_VERSION+.}$path_sep
# In case
Re: setup.hint coreutils editing (was: [ANNOUNCEMENT] Updated: coreutils-5.2.1-3)
On Thu, 23 Dec 2004 17:45:07 -0500, Christopher Faylor wrote: Yes, good point. I've swept through the setup.hints, changed all of the fileutils|sh-utils|textutils to 'coreutils', and removed duplicates. ... AFAICT, my list coincided with yours so everything should be up-to-date now. Actually, tetex-bin still lists fileutils, sh-utils, and textutils in its requires: line, at least on mirrors.rcn.net and sigunix.cwru.edu. I was wondering why setup.exe still wanted to install the removed packages, and then I found this old thread about it. I like the fact that the empty packages in ZZZRemovedPackages install nothing of their own and install coreutils instead, but I understand why others consider it unnerving that setup.exe seems to want to reinstall packages that have been removed. Steve -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Where can I get the source code for setup.exe
The current version of setup.exe is 2.457.2.1 but the Cygwin distribution contains version 2.427, i.e. setup installs the 2.427 source code instead of 2.457.2.1. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Where can I get the source code for setup.exe
On Sun, 23 Jan 2005, Dan Ch wrote: The current version of setup.exe is 2.457.2.1 but the Cygwin distribution contains version 2.427, i.e. setup installs the 2.427 source code instead of 2.457.2.1. See http://sources.redhat.com/cygwin-apps/setup.html. The version of the executable is determined by the revision of ChangeLog. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: cygwin bughunt (FAQ alert?)
On Sat, Jan 22, 2005 at 03:42:15PM -0800, Joshua Daniel Franklin wrote: Yep, I missed that. It's gone, but with the other FAQ additions it moved: http://cygwin.com/faq/faq0.html#SEC104 On Sat, 22 Jan 2005 18:46:41 -0500, Christopher Faylor wrote: This feels vaguely like I'm programming in Fortran again. It would be nice (tm, (C), etc.) if there was some way to put permanent anchors in the FAQ so that we wouldn't have to rely on renumbered sections. Isn't there any way to accomplish that? Not that I know of with Texinfo, even the GNU Texinfo manual's HTML version uses numbered anchors: http://gnu.hands.com/manual/texinfo-4.0/html_chapter/texinfo_4.html#SEC35 I could do it with DocBook's FAQ stuff, as in this example: http://www.miwie.org/docbook-dsssl-faq.html#COLOUREDLINKS I'd kinda like to get everything in DocBook anyway. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: 1.5.12-1: documentation bug in lib[cm].texinfo
On Sat, 22 Jan 2005 07:18:31 -0500 (GMT-05:00), Steve Munson wrote: From the info dir file in /usr/share/info, you can't get to the info files for libc or libm, because their entries are wrong. The file cygwin-1.5.12-1/newlib/libc/libc.texinfo in the source distribution for cygwin-1.5.12-1 contains the following lines near the top of the file: START-INFO-DIR-ENTRY * libc::The ANSI C library. END-INFO-DIR-ENTRY This incorrectly instructs info to look for a node named libc, which doesn't exist. The correct entry would be: * libc: (libc). The ANSI C library. This tells info to look for the *file* libc.info. There is a similar problem in cygwin-1.5.12-1/newlib/libm/libm.texinfo: START-INFO-DIR-ENTRY * libm::An ANSI-C conforming mathematical library. END-INFO-DIR-ENTRY This entry, of course, should read: * libm: (libm). An ANSI-C conforming mathematical library. Thanks Steve. Problem 1 is that these files come from newlib. Problem 2 is that they're in both cygwin and cygwin-doc. When did they get back into the cygwin package? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
ld error while making a dll for module
hi all ,
here i m having a prob regarding creating a shared dll. what exactly
is that i m having a code which is abt a proxy server. It is linux
based source code and i m porting it to windows with the help of
CYGWIN .. Its exe is working fine ..Now i m going to create add-on
module for that project.. Its abt CLAMAV antivirus. I have all header
files, llibclamav, etc. Now when i m going to create shared dll
using following Makefile ::--
CXX = g++
CXXFLAGS = -g -O2 -I../../include -I. -Wall -Wno-sign-compare
-Wno-unknown-pragmas -Wno-format -D_GNU_SOURCE
clamavlib.DLL : clamavlib.c
${CXX} $ ${CXXFLAGS} -Wl, -shared -L. -lclamav -Wl,-soname,$@ -o $@
clean:
rm -f libclamavlib.DLL clamavlib.DLL
It is giving me ld error which is i m attaching as a file .
So now my question is Is my code for makefile is correct ?? If any
solution for the error then plz help me..
---BeginMessage---
---End Message---
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: Cygwin Time Machine
On Sun, 23 Jan 2005, Larry Hall wrote: At 02:19 AM 1/23/2005, you wrote: I'm probably going to regret this :) For some time, I've been keeping a private mirror of Cygwin for my own personal use. Unlike other mirrors, I've been keeping all of the versions of all packages, along with a revision of setup.ini to go with it. Now, call me crazy (and I know you already do :), but since Cygwin Setup uses nothing more than setup.ini and the release/ directory, I thought: why not provide a historical representation of Cygwin's package from which you can actually install from? Think of it as a time machine for going back to a previous version of Cygwin. And so, that's what I did. See http://www.fruitbat.org/Cygwin/index.html#cygwincirca This provides the details of how it works. Basically, it's a bunch of timestamp based URLs which allow you to install a specific snapshot of Cygwin. So, why am I doing this? Well, I actually have need of this for work. It saved me much time and effort, because I could install additional packages at the same level of what we already had installed, thus introducing less instability into our environments, and it gives us a chance to gradually upgrade. It's a cop-out, I know, and I can already see people tut-tut'ing at this, but on the plus side, it's kind of neat to see a form of historical review of Cygwin packages. My mirroring is done automatically each day, and the time machine is also automatically regenerated along with it to keep it up to date. I really only did this for my work, but thought perhaps someone else might find it useful or interesting. Unfortinately, it only goes back to April of 2002, though I actually have package versions going back further, but not the setup.ini to go with them. Once our work has migrated to a more current Cygwin, I might remove this, but for now it's useful to me. You forgot to mention the most important thing in your post. Anybody who visits and uses your archive should contact you directly for any support issues they have with using the software. This list can't entertain I'm not advocating anyone post questions about problems with older versions. In fact, I have advocated, on this list, that people should be at current levels and even try the snapshots before posting to the list. If they do come to me with problems, I'd tell them to either migrate through the revisions until either their problem went away, or they got up to current levels, at which point, they would very likely be using this list to address their problems. :) questions or help solve problems for those using software from your archive. You do have wording something like this at your web page but you know no one ever reads documentation. ;-) Think of it more like a library, with several copies of various books for people to read. Just the same, I've updated the webpage with more verbage on the subject of what the do incase of problems. Good luck! Thanks. I'm just hoping I don't live to regret this. :) -- Larry Hall http://www.rfk.com -- Peter A. Castro [EMAIL PROTECTED] or [EMAIL PROTECTED] Cats are just autistic Dogs -- Dr. Tony Attwood -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
gencat not found.
Hello all, gencat a tool to create message catalog is not present in cygwin. Is someone working on it? If some one could point me to the source so that I can create it on for cygwin. -- cheers, Vadi -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: csh Shell
Hi, Thank you very much for your help, now when i write echo $SHELL i can see tcsh! Cheers, Alexis On Fri, 21 Jan 2005, Igor Pechtchanski wrote: On Fri, 21 Jan 2005, Igor Pechtchanski wrote: On Fri, 21 Jan 2005, Alexis Cothenet wrote: I have installed cygwin but i see that my defautl shell (doing echo $SHELL) is bash. I would prefer to have csh shell. Do you know how i could proceed ? Alexis, Cygwin doesn't have pure csh, but it does have tcsh, which should be compatible. To make it your default shell, you need to do two things: 1) Edit your /cygwin.bat and make it invoke tcsh -l instead of bash --login -i. That way, when you click on the Cygwin shortcut, you'll get tcsh[*]. 2) Edit your /etc/profile, and change the shell entry from /bin/bash to Whoops, sorry! Correction: s/profile/passwd/ Igor /bin/tcsh. This should do it. HTH, Igor [*] There is a /bin/csh, but it's a Cygwin symlink, and you won't be able to invoke it via Windows mechanisms. -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_ [EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! The Sun will pass between the Earth and the Moon tonight for a total Lunar eclipse... -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
