RE: Cygwin maildrop patches and issues (was Re: fetchmail 5.9.8 ...)
What you mention is true: maildrop is closely associated with maildirs (and it was due to one of my colleagues, who swears by maildir on any OS, that I came accross it). I intended to use mutt with maildirs, including a shared mail archive we keep, but did not get around to it. I tried Cygwin mutt 1.3.24 with maildirs and it did not seem to like the ones generated by maildrop. If it did, this would solve (OK workaround) any locking problems. Has anyone had success with mutt and maildirs? FWICT maildirs have some filename issues (illegal chars in the names) that Windows chokes on. I can get inboxes to work OK, but e.g. mutt puts :'s and ,'s in the filenames it tries to create in your received folder. I do have a build of 1.3.28 that works OK with its *own* inbox maildir. Do you want the EXE to try out? -- Gary R. Van Sickle Brewer. Patriot. -- 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: Is Cygwin legal under Windows XP?
The following excerpt is from Brian Livingston's 'Windows Manager' column, 18Mar2002: http://www.infoworld.com/articles/op/xml/02/03/18/020318oplivingston.xml I'm wondering if, in addition to possibly forbidding the use of VNC, this might also forbid installing Cygwin on WinXP and then using a remote connection to the WinXP PC with Cygwin's telnetd, rlogind, rshd, sshd or any X-Windows type of interface, unless you also have a WinXP license for the computer at the other end of the connection. I know this might be considered OT, but I thought it was worth raising the issue. The following excerpt is from a speech delivered by John Patrick Henry to the Second Virginia Convention, convened at St. John's Church in Richmond, on March 23, 1775: Is life so dear, or peace so sweet, as to be purchased at the price of chains and slavery? Forbid it, Almighty God! I know not what course others may take; but as for me, give me Cygwin or give me death! To the best of my recollection anyway. -- Gary R. Van Sickle Brewer. Patriot. The war is inevitable--and let it come! I repeat it, sir, let it come. -- 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: Copy-on-write fork
cgf wrote: I assume that one possible reason is that the copy-on-write fork may be somehow bypassing normal in-memory sharing of text segments but I never knew for sure. Have either of you tried this comparison on XP, to see if it's any different there? I'm running XP here, if Chris J. wants to put the c-o-w DLL up somewhere so I can download it and try it. -- Gary R. Van Sickle Brewer. Patriot. -- 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: Release directory and Setup
Would it be a good idea to number the setup.exe's in the same manner as all other packages and keep them in the new release (under /setup?) directory? The download could then proceed as usual except the warning that there's a new setup moved to the end and the message changed in some manner to reflect this. Once setup is able to auto-update (wishlist Rob?) this'll likely make perfect sense. Right now I'm not so sure. Now, if you downloaded and installed it as if it were another package, you'd get a You have to reboot message. I guess it could be argued that that's better than nothing, but IMHO time spent moving it and dealing with the ramifications thereof would be better spent on auto-update and getting it solved permanent-like. -- Gary R. Van Sickle Brewer. Patriot.
RE: cygwin-doc
The first thing I thought of is that if I added texinfo later, cygwin-man would be a bad name to have, Are you kidding? Cygwin-Man is the COOLEST! Remember that one time when he flew around the world so fast that he made time run backwards? That was AWESOME! And how he can outrun a train? And how bullets just bounce off his chest, and how he just bends the gun as if it was rubber? And that one time when he fought Batman and died but then he came back in the future somehow? And how, when it's really hot and there's kids that are thirsty, he'll crash through the wall and scream OH YEAH! and give the kids flavored sugar water to drink... oh wait, that's Kool-Aid Man. But still, Cygwin-Man would be the BEST name to have! Truth, Justice, and the American Way, my friend. Truth, Justice, and the American Way. Now, basically what I've got is a few scripts that take the SGML files in the Cygwin src (/oss/src/winsup/cygwin/*sgml for the api on my machine) and make some man pages. I see two real options: 1) Include just the scripts as src, with some instructions on telling my Makefile where they keep what I have as /oss/src/ 2) Include the actual SGML files I used with a README about replacing them with the latest from CVS Do either of these sound better? Number 2, because the idea of the source distribution is that anybody can recreate the associated bin exactly. -- Gary R. Van Sickle Brewer. Patriot.
RE: Now that the new setup is here...
Well it shouldn't. There is definitely something wrong with setup and downloads at the moment, but I haven't tracked it down yet. What about the this page intentionally left blank report? Is that on your list? My patch of ~ a week ago puts that one out of our misery permanently. -- Gary R. Van Sickle Brewer. Patriot.
RE: Now that the new setup is here...
On Tue, Apr 09, 2002 at 08:16:32PM -0500, Gary R. Van Sickle wrote: Well it shouldn't. There is definitely something wrong with setup and downloads at the moment, but I haven't tracked it down yet. What about the this page intentionally left blank report? Is that on your list? My patch of ~ a week ago puts that one out of our misery permanently. Could you maybe put it back and just randomly display it? I kind of like the whimsy of such a thing. Whaddaya think's going in the big white box? -- Gary R. Van Sickle Brewer. Patriot.
RE: Now that the new setup is here...
Could you maybe put it back and just randomly display it? I kind of like the whimsy of such a thing. Whaddaya think's going in the big white box? Some part of this: http://www.msu.edu/~huntharo/xwin/logo-ideas/mclean-20020221-0940.png maybe? I like the cygwin C part. cgf Ooh, that's kinda cool. The C kinda looks like a staple though, maybe a little less pointiness. -- Gary R. Van Sickle Brewer. Patriot.
RE: Now that the new setup is here...
On Tue, Apr 09, 2002 at 08:40:06PM -0500, Gary R. Van Sickle wrote: Ooh, that's kinda cool. The C kinda looks like a staple though, maybe a little less pointiness. Do you want to edit it? I doubt that the author (artist?) would mind. Maybe rounding the corners would help. Well, I do have the GIMP just sitting here collecting dust. I'll see what I can do. I'm perhaps the world's worst artist however; I may have to abandon that ship should things get ugly. -- Gary R. Van Sickle Brewer. Patriot.
RE: cygwin-man
DESCRIPTION Cygwin is a UNIX environment, developed by Red Hat, for Windows. Cygwin was up and running long before Red Hat came into the picture. Which is why it's not Redhatwin ;-). Straight off the homepage. Great. Do they also have a statement to the effect of Linux is a UNIX clone, developed by Red Hat? Wait, don't answer that. -- Gary R. Van Sickle Brewer. Patriot. -- 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-man
DESCRIPTION Cygwin is a UNIX environment, developed by Red Hat, for Windows. Cygwin was up and running long before Red Hat came into the picture. Which is why it's not Redhatwin ;-). -- Gary R. Van Sickle Brewer. Patriot. -- 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: [PATCH] Setup Chooser integration
Likewise, if you click ash off, up pops a window listing everything that depends on ash, with an addiotnal message of Warning: removing ash will cause these packages to be removed as well. This does make quite a bit of sense to me. But wouldn't MessageBox() or something akin to it be a better fit to the task? The only possible user input here would be Yes, remove ash and everything dependent on it and Cancel, and the only output a list of package names. Actually, I think that automatically removing dependencies is not a good idea. If I select binutils specifically, then select gcc, then uninstall gcc, I would probably be annoyed to see binutils disappear. cgf I took it to mean the opposite - if you uninstalled *binutils*, it would uninstall gcc because gcc depends on them. But on further reflection I'm no longer sure even that is desirable. If I uninstall ash, should say make get deleted even though I have bash as sh? -- Gary R. Van Sickle Brewer. Patriot.
[PATCH] Setup Chooser integration
ALT-TAB no longer! This patch integrates the chooser into the wizard interface, eliminating a field-expedient thread in the process. Changelog also attached: 2002-04-02 Gary R. Van Sickle [EMAIL PROTECTED] * choose.cc: Run indent. (nextbutton): Remove static variable. (default_trust): Remove use of nextbutton. (set_view_mode): Ditto. (create_listview): Add IDC_CHOOSE_PREV and IDC_CHOOSE_NEXT to ta[] so rbset() sets the prev/next/curr radio buttons properly. (dialog_cmd): Delete function. (dialog_proc): Delete function. Move WM_INITDIALOG functionality to ChooserPage::OnInit. (do_choose): Delete function. Move pre-DialogBox() code to ChooserPage::OnInit(), post-DialogBox() code to ChooserPage::OnNext. (WM_APP_START_CHOOSE): Remove define. (WM_APP_CHOOSE_IS_FINISHED): Remove define. (do_choose_thread): Delete function. (ChooserPage::OnActivate): Delete method. (ChooserPage::OnMessageApp): Delete method. (ChooserPage::OnInit): New method. (ChooserPage::OnNext): New method. (ChooserPage::OnBack): New method. (ChooserPage::OnMessageCmd): New method. * choose.h: Run indent. (ChooserPage::OnMessageApp): Delete declaration. (ChooserPage::OnActivate): Ditto. (ChooserPage::OnMessageCmd): New declaration. (ChooserPage::OnInit): Ditto. (ChooserPage::OnNext): Ditto. (ChooserPage::OnBack): Ditto. * desktop.cc (DesktopSetupPage::OnBack): Replace use of IDD_CHOOSER with IDD_CHOOSE. * fromcwd.cc (do_fromcwd): Replace use of IDD_CHOOSER with IDD_CHOOSE. * ini.cc (do_ini_thread): Replace use of IDD_CHOOSER with IDD_CHOOSE. * res.rc (IDD_CHOOSE): Remove dialog template. (IDD_CHOOSER): Alter dialog template to fit wizard size and format. -- Gary R. Van Sickle Brewer. Patriot. setup-chooser-integration.diff Description: Binary data ChangeLog-chooser-integration Description: Binary data
RE: setup.exe gui testing
I dunno if it's the old behaviour, when setup window is covered by another window, and you click the icon on the taskbar, cygwin setup window does not come to top. That's not new to Rob's latest EXE, but it is new as of the latest released wizardized setup, because the wizardization was not 100% complete. I've got a patch to rectify that ready which I'll be submitting in the next few days. -- Gary R. Van Sickle Brewer. Patriot.
RE: Patch for Setup.exe problem and for mklink2.cc
[snip] Found the problem causing the segment violation and probably causing Jonas Eriksson's problem. It is a typical case of 'off by 1'. In PickView::set_headers the loop filling the window header does one iteration too much, resulting in a call to DoInsertItem with a NULL string pointer and hence a crash following. While debugging this I could not compile the new mklink2.cc ( the c++ version of the original mklink2.c). It seems three (address of c++ operator) have disappeared in the transition. Putting them back made the compiler happy. Is this OK Robert ? I'll check the off-by-one fix in tomorrow, as I'm off to bed now. [snip] There have been a few of these off-by-ones in Setup. Is it possible your habit of using 1-based arrays is a contributing factor Rob? This isn't a convention I see much (modulo Numerical Recipies); is there a reason you use this convention? -- Gary R. Van Sickle Braemar Inc. 11481 Rupp Dr. Burnsville, MN 55337 attachment: winmail.dat
Re: .bashrc not getting sourced?
My question is pretty simple: is editing the /etc/profile the recommended way to get my ~/.bashrc file sourced? I say: no. And if not, what is. It should be noted that I found a message by Gary R. Van Sickle suggesting that .bash_profile might be a better way to do things, but this doesn't directly answer my question. Yeah, well, that guy doesn't know what the heck he's talking about half the time ;-). Here's how I have things set up, and I recommend it to everyone; it seems to be the way bash was intended to work, and I can't see any flaws in the scheme: 1. /etc/profile does not source any .bash* files. It does do a bunch of things like USER=`id -un`, set the HOME var, and runs any scripts in /etc/profile.d/ (not entirely sure what that's about), all of which was setup by setup.exe. 2. .bashrc is empty. 3. .bash_profile sources .bashrc (just in case, for future use), and then contains all my env var settings, aliases, etc. 4. PATH is *not* set in any of these files, but rather in the normal Windows way (control panel on NT+, ??? on 9x). So what you get with all this is: 1. PATH is always good, whether you're running cygwin apps from bash or the Windows command line, and regardless of how bash is invoked (interactive/login or not). 2. When you start bash (interactively, your shell), it runs /etc/profile and sets up the bare minimums and cd's to HOME. 3. After runing /etc/profile, bash looks for ~/.bash_profile and runs it to set up your user stuff. 4. Subshells end up sourcing nothing (no BASH_ENV is defined anywhere), so scripts run faster. 5. Interactive but non-login shells run an empty .bashrc. I don't know when you'd get an interactive but non-login shell, but I haven't noticed any problems to date. -- Gary R. Van Sickle Braemar Inc. 11481 Rupp Dr. Burnsville, MN 55337 -- 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/
Rob: OK to begin chooser integration?
Rob, Alright if I start on bringing the chooser window into the wizard as another page, now that the new version is out? Hopefully it won't be too big of a deal. And what the heck happened to my big white box?!?!? ;-) -- Gary R. Van Sickle Brewer. Patriot.
RE: OT: possible project/research project
Sir, We await your improved model for process control and the operating system that implements it. Senor, Well wait no longer! These days, by gosh, we got everything from spawns to execs to named synchronization objects to... dare I say it?... yes, even threads! Gone are the days when alls a guy could do was fork dozens of exact duplicates of the process he was already running when all he wanted was a little concurrency! Oh, and don't worry, ALL the OSes gots 'em! Randall Schulz Mountain View, CA USA Patriotism is the last refuge of a scoundrel. -- Samuel Johnson I'm a scoundrel? That's the best you got Randy? Heehhehehee! And you're so smitten with fork that you need to start namecalling? -- Gary R. Van Sickle Brewer. Patriot. -- 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: OT: possible project/research project
The issue at hand though, is twofold: 1) Minimise the changes needed to make a proxy for a program. I.e. imagine if GCC and cc1plus.exe lived in-process. That would remove 2Mb of disk IO for each compile. However the _only_ chance of getting such a program proxied would be a minimalistic, non-intrusive approach, or keeping a patched branch :[. 2) Make the context saving and restoring as low-overhead as possible. (if this is spawn() + wait, there is no point). Rob My thinking on this matter (and I've been cogitating about it for some time actually) takes a slightly different tack. My basic ideas for a modernized sh are: 1. Eliminate as much fork()ing as possible, ideally all of it. 2. Get some concurrency going. #1 is basically the same as what you propose, though I'm not sure I'm wild about the DLL idea; if everything's a builtin, why not just statically link? #2 I think could be a significant win even for Unix folk. Basically I'm thinking along the lines of a pipelined shell, e.g.: # Why should this...: rm //a/bunch/of/files/out/on/a/super/slow/server/* # ...block this: gcc hello.c Obviously you're never going to be able to take advatage of all non-dependencies, but as a wise man once told me, you can't win if you don't enter. -- Gary R. Van Sickle Brewer. Patriot. -- 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: OT: possible project/research project
Gary, You labelled yourself a patriot. I quoted the label of a beer bottle. Samuel Adams to be precise. I just pointed out some relevant wisdom. Indeed. But not the relevant wisdom you thought you had. If you perceive that to be namecalling, so be it. It's the sort of baseless conclusion I expect from someone who admires patriotism. Or drinks beer? To the best of my ability to discern it, there is no connection between the impoverished and gravely mistaken notion of patriotism and software process control models. If you can see one, please share it with me. Well, I think the fork() concept qualifies as impoverished and gravely mistaken. So I got that goin' for me. Randy PS: In the future, if you have any insults or namecalling you feel you need to send my way, please do so in a public forum where others can enjoy your sarcasm. I have no desire to converse privately with someone who hates his country as much as he hates himself. My apologies to the list for bothering to respond to Mr. Schulz' bait. -- Gary R. Van Sickle Brewer. Patriot. -- 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 without installing
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John A. Turner Sent: Friday, February 22, 2002 1:14 PM To: Robinow, David Cc: Cygwin mailing list Subject: Re: Cygwin without installing Robinow, David wrote: arborescence is a perfectly legitimate French word meaning tree structure. It's quite popular as can be seen by a simple search. It has fewer letters than it's english equivalent so I see no reason not to use it and I intend to, now that I know what it means. See http://translation.langenberg.com/ NTAGARA, but my introduction to the word came in the form of an album by Ozric Tentacles: Oh wow, now THAT takes me back. Tentaclemania, mop-tops, Shay Stadium, Seargent Ozric's Lonely-Tentacle Club Band, the Fifth Tentacle... they truly taught us how to love, and how to live. -- Gary R. Van Sickle Brewer. Patriot. I'd like to say 'Thank you' on behalf of the group and ourselves and I hope we passed the audition. -- 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: setup w/char* eliminated is big
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Pavel Tsekov Sent: Friday, February 15, 2002 10:05 AM Robert Collins wrote: Ok, finally got some breathing time. Setup with char * eliminated is ~350K. Ouch. This is why I've not committed my patch yet (I've been trying to see *where* the extra 100K appeared from). You have four 'inline' - I know they're small in size, but three of them are the most commonly used methods (the default and the copy constructor and also the 'operator ='). Remove the 'inline' modifier and see if the executable gets smaller. Done and done: CVS + For the curious patch + Two subsequent patches from Michael Chase == 355840 bytes. Above with all inlines un-inlined == 344576 bytes. So a bit over 11KB saved. In my judgement that's enough to warrant removing the inlines; if string-handling speed is a significant factor for setup.exe I'd say there's something wrong somewhere that no amount of inlines could remedy. -- Gary R. Van Sickle Brewer. Patriot.
RE: setup w/char* eliminated is big
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Collins Sent: Thursday, February 14, 2002 3:36 AM To: [EMAIL PROTECTED] Subject: setup w/char* eliminated is big Ok, finally got some breathing time. Setup with char * eliminated is ~350K. Ouch. This is why I've not committed my patch yet (I've been trying to see *where* the extra 100K appeared from). Yowzers. I currently show ~285K pre-char*-elimination, making it more like 65K, but that still sounds like way too much of an increase. Can you check it into HEAD maybe and let a few more eyes look at it? -- Gary R. Van Sickle Brewer. Patriot.
RE: anybody else also infected
Thank you, Mr. Norton! cgf Number of times I've lost data to a virus: 0. Number of times I've been alerted to a real virus by a virus scanner: 0. Number of times I've lost data to a virus scanner: 2. Norton, McCaffee, they all go in the same hopper as far as I'm concerned. (Figured I'd better get in on this thread before it dies out ;-)) -- Gary R. Van Sickle Brewer. Patriot. -- 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: cvs -- carriage return problems with cygwin 1.3.9 and interaction with setup's text file default
[snip] I think it would be useful to update the cygwin faq with some well-chosen advice about how to deal with DOS vs. Unix text file formats, Oh man, let me do the honors: XX.XX HOW TO DEAL WITH THE WINDOWS VS UNIX VS MAC TEXT FILE FORMAT FIASCO 1. Track down the bastage who thought fscanf() was a good idea and make him atone for his crimes against humanity. 2. Teach Unix that all files are not actually text files. 3. Teach Notepad that \r does not look like a black square. 4. Teach all programs on both OSs that ASCII text files are just as valid regardless of whether the lines end in \r or \r\n or \n or \n\r. 5. Put on yer asbestos drawers, because by the time you get to this step, you'll have missed the Rapture. particularly pointing out that some of the programs in the cygwin release will only work in DOS text mode if they were ever installed in DOS Text mode and wrote any files. It would also be helpful if there was a better explanation than what I've found so far about the meaning of this setting in the setup dialogs. What is actually changed by altering it? The default mount mode. I don't recall offhand if this gets reset every time you run it or not, I'm guessing yes. Regardless, you're right, I don't see anything in the FAQ about this at all (or actually the Everyone/Just Me one either) and there needs to be. We should also probably reconsider whether these need to even be there every time you run setup. Presumably what I've done is partly bogus. I should reinstall everything with a consistent text mode setting, right, or some other programs will be broken similarly to the way cvs was? I can only guess yes. -- Gary R. Van Sickle Brewer. Patriot. -- 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: how to create a new user
I'm not sure if you made a mistake or not, in typing the '-u' flag, because my mkpasswd doesn't support that option. You have an old mkpasswd. -u,--username username only return information for the specified user is relatively new. -- Gary R. Van Sickle Brewer. Patriot. -- 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: bison 1.31 is broken...
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Laurence F. Wood Sent: Thursday, February 07, 2002 3:58 PM To: Cygwin@Cygwin. Com Subject: bison 1.31 is broken... Bison version 1.31 is broken. The following command under bison 1.31 now generates incorrect output: bison -v -d -o anything.tmp parsetable.yy Well Christ, no wonder. Just look at that parsetable.yy! Sheesh, you email your mother with those fingers? bison 1.30 generates the correct output. Of course it does, what do you expect with a parsetable.yy like that? Lordy. While you're at it, you probably should try Cygwin-B20, everything worked a lot better back then. -- Gary R. Van Sickle Brewer. Patriot. -- 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: Scriptable start.exe
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Joseph Annino Sent: Tuesday, February 05, 2002 3:52 PM To: cygwin Subject: Scriptable start.exe I saw some discussion in the archive that start.exe was once scriptable, and now isn't, and some people showed interest in making it scriptable again. Setup.exe has never been scriptable in any respect, and no discussion to that effect has occurred here to the best of my knowledge. People have been discussing adding such a feature, but I haven't seen any code. So I am wondering what the state of making start.exe scriptable is? This is a feature that would be quite helpful on a current project so that clients can install a properly configured cygwin without the few clicks that are required now. None of the people that have been working on setup.exe recently (including myself) appear to have any desire to add any scripting functionality to it. There's much more important work that needs to be done before such a notion could even be realistically considered. -- Gary R. Van Sickle Brewer. Patriot. -- 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: Scriptable start.exe
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Faylor Sent: Tuesday, February 05, 2002 10:02 PM To: [EMAIL PROTECTED] Subject: Re: Scriptable start.exe On Tue, Feb 05, 2002 at 09:55:04PM -0600, Gary R. Van Sickle wrote: So I am wondering what the state of making start.exe scriptable is? This is a feature that would be quite helpful on a current project so that clients can install a properly configured cygwin without the few clicks that are required now. None of the people that have been working on setup.exe recently (including myself) appear to have any desire to add any scripting functionality to it. There's much more important work that needs to be done before such a notion could even be realistically considered. Currently, setup.exe is simple enough that you could almost get by with just using shell scripts, tar, and bzip2. One probably could. Exercise left to the reader ;-). I can forsee at some distant point in time maybe some command-line functionality thus: setup.exe packagename which I think has essentially (or maybe even exactly) already been suggested. But one release at a time. Speaking of which... Rob? ;-) -- Gary R. Van Sickle Brewer. Patriot. -- 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: /dev/registry
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Chris January Sent: Sunday, February 03, 2002 9:43 AM To: [EMAIL PROTECTED] Subject: /dev/registry How about adding a /dev/registry fhandler to Cygwin? Registry keys would be directories and values in the registry files. I'm willing to try coding this if people think it's a good idea. It allows shell scripts to easily access registry keys as well as programs. Well, it looks like I'll be the only one, but this sounds to me like an insanely *BAD* idea. It seems to me to be hard enough to keep the Windows registry in one piece even if you don't dink with it; I shudder to think what horrors await sombody with fat fingers and an itchy TAB finger (i.e. me): cat HundredsOfMBsOfCrap /dev/r[TAB-oops-I-meant...well-something-else-anyway] I'm trying to think where this would actually be useful, but I'm drawing a blank. It seems to me that the registry should have at least a slightly higher barrier to entry than the command line. -- Gary R. Van Sickle Brewer. Patriot. -- 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: setup.exe looks good!
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Faylor Sent: Tuesday, January 29, 2002 10:41 PM To: [EMAIL PROTECTED] Subject: setup.exe looks good! I just built the latest setup.exe. It looks really nice. And, I see that clickable categories are working! Are they ever! And did you catch the replace files in use feature? Yeah it makes you reboot, but still, pretty sweet. I keep meaning to suggest that we add a '+' or a '' to the left of all of the Categories so that it is obvious that they can be expanded. I think that people are used to interpreting the icon next to something as indicating that there are more things possible to list. I keep meaning to suggest the same thing, and maybe even lines like you get on most such expanding list control thingies. But I think Rob is rolling his own here instead of using the ListView common control (which isn't available on a stock 95 machine AFAIK), so lines might be asking a bit much. But I'd think that at a minimum, simply adding a toggling +/- to the front of each category string wouldn't be too traumatic. Rob? Also, I thought that the Category page was supposed to automatically expand the Categories that were installing things so that it was obvious what was about to be downloaded. Didn't it do that at one point. Yeah, it did, and I thought it still did the last time I checked (like a few days ago). I'm resynching to CVS now, I'll rebuild it and see. I need that rxvt update, and of course the sweet new bazzoo release. I really like the look and feel of the new setup.exe. [Cartman voice:] We're sweet ;-) Hopefully, that won't translate into it being completely incomprehensible for everyone on the cygwin@cygwin list. Well, we are working hard on the mindreading mode -- Gary R. Van Sickle Brewer. Patriot.
RE: setup crashing - fixed?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Corinna Vinschen [snip] But be *extremly* careful using 3.3! It's in an early development stage and it's marked as pretty useless by it's developers. Actually they are discussing to renumber that release to 0.9. Oh man, but just to have bazzoo on Windows, after all these years... I'm throwing all caution to the wind! I just hope I have enough memory and disk space. BTW, who's the Cygwin bazzoo maintainer? -- Gary R. Van Sickle Brewer. Patriot.
RE: DocBook and OpenJade packages
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jon Foster Sent: Sunday, January 27, 2002 9:23 AM To: [EMAIL PROTECTED] Subject: DocBook and OpenJade packages Hi all, I've recently installed the DocBook text processing system under CygWin. This was quite fiddly, as there are many small tools that have to be downloaded and configured. Holy bejesus you can say that again. I spent way too much time trying to do this myself with close to zero luck. I'm willing to volunteer to produce and maintain proper CygWin packages for these tools, so that they can be easily installed by just choosing the packages in the setup program. * Is this something you'd like? I most definitely would. * Is anybody currently working on this? Not me. As I said I had done some work in this direction, but with so little to show for it after much too much dinking around, I gave up a while ago. [snip] -- Gary R. Van Sickle Brewer. Patriot.
RE: for the brave
Well I can't duplicate it :}. I have a somewhat different source base though, so I'll try and commit that in the next coupla hours. I just read another post of yours that (if I read it right) sounded like you still had two small patches from me not comitted yet (Add box crash and something else)? If so, please don't lose them - because I have ;-). -- Gary R. Van Sickle Brewer. Patriot.
RE: setup crashing - fixed?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Corinna Vinschen [snip] By explicitely expressing my wish to change the state by pointy clicky somewhere. Honestly, think of the current test installation of tetex and texmf which is 30 Megs. If the user actually chooses to go back to the curr version, it's his/her choice. If that happens while the user actually just wanted to update to the latest bazzoo-3.3-8 package it's pretty annoying. SOMEBODY ***FINALLY*** PORTED BAZZOO 3.3 TO CYGWIN?!?! WHY DIDN'T YOU GUYS TELL ME!?!?!?!? Oh man the guys at work are gonna go WILD when I tell 'em! -- Gary R. Van Sickle Brewer. Patriot.
RE: [PATCH]Reduce messages in setup.log
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Collins Sent: Tuesday, January 29, 2002 12:05 AM To: Michael A Chase; [EMAIL PROTECTED] Subject: Re: [PATCH]Reduce messages in setup.log Ok, I've looked at the patch. Most of the methods are stubs that should warn when used. Some aren't, and I'll try and merge those changes in by hand tonight. Don't bother reissuing the patch - I'm about to cause everyone heartache by removing much of the char * usage (I got sick of memleaks) Yeah, I'm cryin' my eyes out here. ;-) for a quick-and-dirtyish String class. Sigh, still no STL. Rob, would you care to just graft more functionality onto my embryonic cistring class? Or was that the plan? -- Gary R. Van Sickle Brewer. Patriot.
RE: New setup.exe snapshot
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Collins [snip] - Original Message - From: John A. Turner [EMAIL PROTECTED] [snip] o if the window gets covered up, clicking on its button on the taskbar doesn't bring it back to the top like it does with other apps Hmm thats strange. Clicking on the taskbar should bring it back. Ah well, another TODO item :}. Yeah, this only happens on the chooser page, where I've got your dialog spawned by the property sheet page. Not sure what the cause is, but you can ALT-TAB to it. -- Gary R. Van Sickle Brewer. Patriot. -- 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: for the brave
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Collins I need a few testers: I've fixed the fault Corinna reported with in use files and upgrades. I'd like to know that it works on 9x (not tested properly just now), and if anyone can get it to fault - with reasonable behaviour. FWIW: Worked here (WinXP though) on an in-use cygwin1.dll (a hung bash process actually). -- Gary R. Van Sickle Brewer. Patriot.
RE: sed : Not compatible between cygwin-B20 and cygwin-2.125.2.10
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Faylor [snip] But same command work on cygwin-B20. Hello from the year 2002! When, we reach, at some point in the distant future, cygwin version 2.125.2.10, I will try to make sure that I remember this problem. Or, possibly, I will leave some provision in my will for my heirs and cygwin successors. Luckily, it works just fine now, however. Phew. cgf Why did everything work so much better in B20? ...Hair was short and skirts were long, Kate Smith really sold a song, I don't know just what went wrong, Those were the days! -- Gary R. Van Sickle Brewer. Patriot. -- 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: emacs or xemacs
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Collins Sent: Wednesday, January 16, 2002 10:48 PM To: [EMAIL PROTECTED] Subject: Re: emacs or xemacs - Original Message - From: Christopher Faylor [EMAIL PROTECTED] And then too, not all of them are even *meant* to be funny. ;-) I thought you were talking about the guy in M#A*S*H. He wasn't meant to be funny, or rather he was but he wasn't supposed to be purposely funny. That was Major Burns wasn't it? Rob No, I think he's Homer's boss on The Simpsons. Together: Third base! ;-) -- Gary R. Van Sickle Brewer. Patriot.
RE: emacs or xemacs
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Starks-Browning This is not *the* Ken Stevens, is it? The guy that did Wild World and Peace Train? Those ROCK dude! Oh wait, that was Ken Burns. Nevermind. -- Gary R. Van Sickle Brewer. Patriot.
RE: Maintainers of CURL, MUTT, PYTHON and WGET, heads up!
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Hack Kampbjørn Roth, Kevin P. wrote: Yes, I checked an actual SSL connection. It actually worked ;-) [snip] So I'm the last one to report back. AHEM! I believe that would be Second to last my good man! ;-) Ok, Mutt has no runtime version checking at all. It does have this at build time: #if OPENSSL_VERSION_NUMBER = 0x00904000L #define READ_X509_KEY(fp, key) PEM_read_X509(fp, key, NULL, NULL) #else #define READ_X509_KEY(fp, key) PEM_read_X509(fp, key, NULL) #endif which AFAICT is OK (right?). Generated config.h has RSA, IDEA, and RC5 support disabled. Still haven't found something to try to connect to, but AFAICT everything should be OK according to what you said in your email. PS: Contrary to all indications, I am still working on a new mutt release. -- Gary R. Van Sickle Brewer. Patriot.
Setup.exe: / prefix on symlinks
Mainly a heads-up for you Rob: I'm getting bad symlinks now with the latest setup.exe. They end up looking like this: ... lrwxrwxrwx1 Gary_VS None 21 Dec 27 00:36 etags.exe - /ctags.exe ... The / of course leads to all manner of havoc. This is the earliest one I see here. -- Gary R. Van Sickle Brewer. Patriot.
RE: Proposed Mailing List Page Reorg Has Been Reorged
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Collins -Original Message- From: Soren Andersen [mailto:[EMAIL PROTECTED]] So what I am addressing is a perceived (on my part) need for Soren, this is *discussing* it, if you wish to address it, then contribute a patch - to the web site, the FAQ - wherever you think it should go. I don't say this to cut short the discussion, but because no-one has disagreed in any substantial way with what you are saying, and no-one has steppted forth to do it Uh, guys: http://cygwin.com/lists.html. Pretty well done, whoever did it. And it's been up since at least the crack of noon. Let this be a lesson to everyone to: 1. RTFM 2. STFML and TFWS 3. WTFPMA[1] the next time a newless cluebie stumbles in here and for some reason the urge to bite his head off rears its ugly head. [1] Watch The Fricken Potty Mouth Abbreviations. -- Gary R. Van Sickle Brewer. Patriot. -- 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: new policy for packages
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Collins I want to suggest that the following become policy: No new packages are accepted that require non-packaged prerequisites. i.e. using rpm which was raised on cygwin@ recently, until db 3.2 is packaged and maintained by 'someone', rpm is not acceptable as a package. Thoughts? I don't know how things could work any other way, in cases such as this anyway. -- Gary R. Van Sickle Brewer. Patriot.
RE: Quick question on setup.exe
Just to clarify a bit: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Pavel Tsekov Hey, Vincent! :) First of all - this is _NOT_ a download application. This is an installer. Well, it's really both a floor wax AND a dessert topping*, but I digress. *For those outside the US, or with more years ahead than behind, that's from a Saturday Night Live skit. I suppose knowing that doesn't make it any funnier though. Now to answer you question - No! The package selection is not based on the OS, on which setup.exe is currently running. True, and the reason that is is because the same exes get installed regardless of OS. Any differences are taken into account (primarily by the cygwin1 and other DLLs) at runtime. -- Gary R. Van Sickle Brewer. Patriot. -- 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: Copy and Paste into Console
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Randall R Schulz Gary, I was happy to learn about this: # Make insert actually useful \e[2~: paste-from-clipboard Me too, since I didn't know about it myself until I went to answer the question. Who'd have guessed that even *I* could learn a thing or two from the FAQ? ;-) Now I just hope I don't start hitting the otherwise-good-for-nothing-but-causing-grief insert key in TextPad etc. ...since it is not documented via man readline, man bash nor in my rather dated hard-copy BASH manual. I'd guess that paste-from-clipboard probably doesn't do much on non-Windows readlines. Might be specific to the Cygwin port, I really don't know. However, I now have two questions: 1) Where does one find complete and definitive information on readline as implemented / used by BASH. AFAICT, man readline pretty much covers it, with the above exception, which all I can tell you about that is I got it from the FAQ. 2) Why does paste-from-clipboard stop just before the first newline in the clipboard contents while middle-mouse pastes the entire contents? Is there another undocumented clipboard pasting readline primitive that pastes the entire clipboard? (Running strings on /lib/libreadline.a suggests there is not.) Is this a bug, or intended behavior? I have absolutely no idea. Wasn't there when it happened ;-). Thanks. Randall Schulz Mountain View, CA USA -- Gary R. Van Sickle Brewer. Patriot. -- 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/
Proposed Mailing List Page Reorg (was: RE: No stderr output)
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Faylor [snip] For Bourne style shells I use runme filename 21 This redirects stdout first and then stderr to whereever stdout is pointing. If this doesn't do it, then I think the best plan is to find help from another mailing list. Basic shell questions are not really appropriate here -- especially given the recent volume we've been experiencing. I've been cogitating for a while that it could be mutually beneficial to inexperienced users and regulars' blood pressures alike if the Cygwin mailing list page listed a few concrete URLs to such newbie lists/newsgroups/FAQs etc, and at the same time reworked the wording on the description of this particular list. Currently it says, If you have questions about how to use Cygwin, or any of its tools (bash, gcc, make, etc.), this is the list for you. That means: If you have any question whatsoever regarding anything you can associate somehow with Cygwin, post it here. That's simply not the intention of the list (at least since I've been around), nor should it be, but the description simply gives no indication of the true intent, i.e. Cygwin-specific questions only need apply. Now as for where best to send people, I have no idea (maybe some can just point into the appropriate section of the FAQ). But here's a rough outline of what I'm thinking: Help With The Tools Packaged With Cygwin Can't figure out the bash command line syntax? Don't know what a HOME is? What-ular expressions? These are general Unix sorts of questions , and you'll have the best luck getting help at one of these many fine resources: Unix basics: http://wherever/ Bash up the wazoo: news://bash.whatever/ Regular Expressions Revealed: mailinglist://heretoo/ Cygwin Specific Mailing Lists = cygwin-xfree: (same description, note the clever inversion of these two, thus guaranteeing that no xfree questions get into the main list). cygwin: A high volume list solely for the discussion of Cygwin-specific issues/problems/etc. If you have questions specifically related to the Cygwin ports of the tools, *not* regarding the tools themselves, post here. Cygwin Developers Mailing Lists === Heaven help you if you post something off topic to one of these: cygwin-apps: blah blah blah etc etc Comments? Questions other than what are you smoking? ;-) -- Gary R. Van Sickle Brewer. Patriot. -- 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: ksh on cygwin
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Karsten Fleischer It's not a major change. SUSv2 doesn't say that you have to use /bin/sh for a shell. It even says that $SHELL can name the user's favorite shell. I know that you always have trouble with users who copy /bin/bash to /bin/sh, it's a monthly issue on the mailing list. My patch would solve this in an easy way. Actually, I can easily see it causing much *more* trouble, because then there'd be one more way to get things FUBAR. Well actually more like Permutation(2) (or whatever the notation is, God I'm getting old): Why is /bin/sh ash even though I set $SHELL to bash? I replaced /bin/sh with bash but I still get ash when I run a script. Rinse, repeat. I just don't see how the cost:benefit works out on this one. -- Gary R. Van Sickle Brewer. Patriot. -- 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: Newbie Question
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dylan Cuthbert Just right click on the cygwin shell icon and click Properties, then alter the settings just as you would for a DOS box. *Way* better than that, use rxvt instead of... ugh... command.com, and you can just resize the window at will, while it's running. Check the FAQ and the last day or so on this list on how to set that up. -- Gary R. Van Sickle Brewer. Patriot. -- 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: Copy and Paste into Console
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rob Hi all! I have been searching through the archives but the responses I found confused me a bit. Unix is a harsh mistress. That said, you want to be sure to also check the FAQ if you haven't already; it has a few entries on this particular issue. If I cannot find a .inputrc file, should I create one? Yes. It's not a tragedy if you don't have one though, things will just not work as nice at the bash prompt for you. If so, where should I put it? Your home directory. What entries would work to allow: man readline will get you started. - paste into console from a right click; Don't know if this is possible, and I can almost guarantee you if it is it won't be anything in .inputrc that will do it. The good news is that the middle button does this already if you have it, and also see my .inputrc below. - paste into console from a ctrl+v combination; - copy from console from a left click (with text selected); - copy from console from a ctrl+c combination. No need - once you lift the button, the selected text is copied to the clipboard. CTRL-C wouldn't be the wisest choice for copy anyway - it tends to already be used to kill the running app ;-). Here's what I have for my .inputrc, and it rarely steers me wrong: # This file is read by the 'readline' library # (the library which bash uses for its command- # line editing facility) # Make Home work \e[7~: beginning-of-line # Make End work \e[8~: end-of-line # Make Delete work \e[3~: delete-char # Make insert actually useful \e[2~: paste-from-clipboard # Ignore case for the command-line-completion # functionality. set completion-ignore-case On Now this is about as minimal as it gets beyond nothing; you can like most things Unixoid make things as convoluted as you want, and again the FAQ has some info on some other good things to have in there which I don't have. Hmmm... we've alredy got /etc/profile being generated by setup. Maybe add an .inputrc to that list? Any thoughts? -- Gary R. Van Sickle Brewer. Patriot. -- 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 console
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Warren Young John Peacock wrote: p.s. and I guess your color scheme isn't so awful; typically you never want to have red and blue of the same intensity next to each other, since the same cones in your eyes perceive both colors and you can sometimes get the phantom movement I wear glasses that distort blue/red so that as I move my head, the foreground color appears to move slightly over the top of the background. (Some kind of difference in the way the lenses refract the differing wavelengths.) It's very annoying, but fortunately red/blue combinations are pretty rare. Rxvt in Super-3D. Sweet. -- Gary R. Van Sickle Brewer. Patriot. -- 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: Success report: Setup.exe on Windows 2000.
-Original Message- From: Robert Collins [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 06, 2002 7:36 AM To: Gary R. Van Sickle; Cygwin-Apps Subject: Re: Success report: Setup.exe on Windows 2000. - Original Message - From: Gary R. Van Sickle [EMAIL PROTECTED] Actually now that I take a look, it's much worse than 25% - more like 5%. Example: nothing in BASE is showing a description, ash, bash, cygwin, all the way down the line. The view doesn't appear to matter. It was only showing the label for non installed packages. Fixed now. Rob Yep, looks like that did it. But what's this All thing I'm seeing now ;-)? -- Gary R. Van Sickle Brewer. Patriot.
RE: how to add a specified path to PATH
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Guenther Sohler Assuming you are using bash(this is the default) put following stetement into your ~/.bashrc file export PATH=$PATH:newpath newpath is the new path Actually I think it's probably marginally better to do it in .bash_profile (of course assuming you're using bash as your login shell) like this: .bash_profile: # Do everything that would be done in non-interactive mode. source $HOME/.bashrc # The path already has stuff in it, but # we can add to it here if we need to. export PATH=more paths:$PATH:still more paths The idea here is to load up as much stuff as possible into .bash_profile, which is only run once per bash window you start, as opposed to .bashrc, which will be run not only then but also in any sub-bash's you may end up spawning. At the same time, since you've done the export, any subshells (bash or not) will still get the right path (in fact if you're setting PATH in .bashrc it'll double in length in every level of sub-bash you spawn). Now since /bin/sh isn't bash anyway, you're probably not spawining any sub-bashes, so the issue is largely academic. But still. -- Gary R. Van Sickle Brewer. Patriot. -- 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: [SECURITY] [DSA-096-1] mutt buffer overflow
Oh Lord. Thanks for the heads up Corinna, I had not seen this. I'm not going to get a chance to reroll this until tomorrow evening; do you think this warrants pulling the current build from distribution? If so, by all means do so. I can write up an explanation/warning tomorrow and post it to the main list if you think that's warranted (I guess I do, even if you don't want to pull it). -- Gary R. Van Sickle Brewer. Patriot. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Corinna Vinschen Sent: Thursday, January 03, 2002 5:20 AM To: cygwin Subject: FW: [SECURITY] [DSA-096-1] mutt buffer overflow -Original Message- From: Wichert Akkerman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 02, 2002 6:39 PM To: [EMAIL PROTECTED] Subject: [SECURITY] [DSA-096-1] mutt buffer overflow -BEGIN PGP SIGNED MESSAGE- - -- -- Debian Security Advisory DSA-096-1 [EMAIL PROTECTED] http://www.debian.org/security/ Wichert Akkerman January 2, 2002 - -- -- Package: mutt Problem type : buffer overflow Debian-specific: no Joost Pol found a buffer overflow in the address handling code of mutt (a popular mail user agent). Even though this is a one byte overflow this is exploitable. This has been fixed upstream in version 1.2.5.1 and 1.3.25. The relevant patch has been added to version 1.2.5-5 of the Debian package. wget url will fetch the file for you dpkg -i file.deb will install the referenced file. Debian GNU/Linux 2.2 alias potato - - Potato was released for alpha, arm, i386, m68k, powerpc and sparc. At this moment packages for sparc are not yet available. Source archives: http://security.debian.org/dists/stable/updates/main/source/mu tt_1.2.5-5.diff.gz MD5 checksum: 04f7c13c3bf6a1d4fcb4bf1a594522a1 http://security.debian.org/dists/stable/updates/main/source/mu tt_1.2.5-5.dsc MD5 checksum: 0ba73a6dd8029339329c27b56087ebce http://security.debian.org/dists/stable/updates/main/source/mu tt_1.2.5.orig.tar.gz MD5 checksum: 0ba5367059abdd55daceb82dce6be42f Alpha architecture: http://security.debian.org/dists/stable/updates/main/binary-al pha/mutt_1.2.5-5_alpha.deb MD5 checksum: b206557565607833551219ff67737cd4 ARM architecture: http://security.debian.org/dists/stable/updates/main/binary-ar m/mutt_1.2.5-5_arm.deb MD5 checksum: 57c0c2602c3bfde3f459f01515432eac Intel IA-32 architecture: http://security.debian.org/dists/stable/updates/main/binary-i386/mutt_1.2.5-5_i3 86.deb MD5 checksum: d72fa58b0914762674648a68d410b4b9 Motorola 680x0 architecture: http://security.debian.org/dists/stable/updates/main/binary-m68k/mutt_1.2.5-5_m6 8k.deb MD5 checksum: 266c451cee06693e7f40917b0465981a PowerPC architecture: http://security.debian.org/dists/stable/updates/main/binary-powerpc/mutt_1.2.5-5 _powerpc.deb MD5 checksum: aec60dae6148ac9da29c111e70ea77b0 These packages will be moved into the stable distribution on its next revision. For not yet released architectures please refer to the appropriate directory ftp://ftp.debian.org/debian/dists/sid/binary-$arch/ . - -- - apt-get: deb http://security.debian.org/ stable/updates main dpkg-ftp: ftp://security.debian.org/debian-security dists/stable/updates/main Mailing list: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: 2.6.3ia Charset: noconv iQB1AwUBPDNFlajZR/ntlUftAQHLowMAlDOIzMX02myWrdk4h487ZxhPBK86i47O C8cDu9p4O4+39HkZNU+YNQs3+wZT5JaYnrBBiYryjDDqxXhzMDwbKYv534QuNZH9 t/1AsqUXp+veutwpWXuFT742TwsiCtW4 =xDVb -END PGP SIGNATURE- -- 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: announcements trapped by anti-viral filter
Stoddard, Isaac A wrote: [snip mere *mention* of EXEs trips AV SW] Man, I've heard some MIStapo horror stories in my time, but that one takes the proverbial cake. I simply can't imagine that such a situation can last for long at a place as big as Boeing without rioting in the cubes by the engineering staff. I sympathize with you, but I agree 100% with Chris et al, munging every post merely mentioning an exe just to bypass some rogue MiSS stormtrooper's insanity is just plain wrong. What would munging the announcements gain you anyway though? Surely if they're blocking those, you're being blocked from downloading and installing anything, no? -- Gary R. Van Sickle Braemar Inc. 11481 Rupp Dr. Burnsville, MN 55337
RE: setup.exe splash screen - mini-competition
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Collins [snip] I'm looking for a graphic, 96 px wide, 179 px high (or thereabouts) to replace that rectangle. It actually has to be 152 pixels wide by 290 pixels high, according to occaisionally-reliable MS sources. The 96x179 is the size of the area in dialog units, which are supposed to map variably to screen coords depending on your monitor resolution. MS is silent on how the fixed-size bitmap is supposed to do this as well, but we can always StretchBitBlt() it if need be. -- Gary R. Van Sickle Brewer. Patriot. -- 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: New setup build for people's perusal
-Original Message- From: Robert Collins [mailto:[EMAIL PROTECTED]] - Original Message - From: Gary R. Van Sickle [EMAIL PROTECTED] Ouch, yeah, I don't either. I'll look into that to make sure it wasn't something I did, or fix it if it was. No NT4 here though; I hope it doesn't end It's something you've done :]. Line 52 of net.cc - EnableWindow (GetDlgItem (h, IDOK), enable) - is having no effect. I haven't checked as yet, but my 2c is that it's failing due to the new windowing code. Yep, that was it. Already found and fixed, *plus* I added a Can't get site list, check your net settings MessageBox, no extra charge. That's two for the price of none baby YEAH! Jeez, if I keep making mistakes like this, I'm going to have to start coding under a pseudonym! ;-) I'm not familiar with your code yet, so I hope you don't my my going 'wh please fix waaah' :]. Well, let's get this CVS problem fixed and we'll call it even. ;-) Got your other post and am looking into it. Executive summary is I think there's a bunch of other files of a similar CRLF nature in there; I'm sorting it all out now and will report back. Rob -- Gary R. Van Sickle Brewer. Patriot.
More grist for the CVS line ending mill.
From a post I just made to -patches, in hopes this helps Charles fix it or others avoid it. I've been having no end of problems with CVS claiming every line of a file has changed when they haven't, and I've narrowed it down a bit: I tried simply checking out a file, touching it, and then cvs diffing it. No problems there. I did notice that on at least two files, window.cc and threebar.cc, they check out as CRLF files even though I'm now on binary mounts, and cvs diffing against CRLF files on a binary mount seems to work. But then when I run indent on them they get changed back into LF-only, and then every line cvs diff's as different. BUT, log.cc checks out as LF-only. Completely wiping out the formatting in Textpad (which preserves LF-onlys) and indenting leaves the file as LF-only, and surprise, surprise, cvs diff now works. So it looks to me like the immediate problem is CRLF files in the repository, and the long-term solution to not have CVS care what the line endings of text files in its repository are. On further reflection, perhaps that last part is bass-ackwards: I guess nobody should really care what the files look like once they get into the repository, only when they hit your local disk or are read from it. So for my WAH (Wild-Ass Hypothesis): Is the CVS client wb/rbing all files it touches on the local machine? I swear in the name of all that is Holy, when I get my hands around the neck of the guy who first mixed fgets() into the same object as fseek() -- Gary R. Van Sickle Brewer. Patriot. -- 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/
[PATCH] Setup.exe other URL functionality
Here's a patch that makes the Other URL functionality work. I've merged the IDD_SITE and IDD_OTHER_URL boxes into one, which seems more intuitive (and yes, that list box is getting pretty stubby, it's on the proverbial plate). I also removed test -f ./.bashrc . ./.bashrc from the generated /etc/profile. Bash sources this automatically after it reads /etc/profile, so all it was accomplishing with bash as your shell was to run .bashrc twice, which I doubt was ever the intent, and I have to guess that users of other shells don't really want to be running a ._bash_rc file. Note that I've attached two patches here. The contents are the same, but due to some wackiness in either cvs diff or indent (lemme make a WAG, sit down for this one: CRLF probs? ;-)), the larger one (-pu'ed) ends up replacing the entire contents of several files, while the smaller one (-pub'd) is rather less agressive. Take your pick, it's Gair's Bimonthly 2-for-1 Sale! Every diff must go! ;-) -- Gary R. Van Sickle Brewer. Patriot. ChangeLog.setup.grvs Description: Binary data setup.diff.pu.bz2 Description: Binary data setup.diff.pub.bz2 Description: Binary data
RE: [PATCH] Setup.exe in a property sheet
threads for the install process... Well I'm not about to claim that any of this is complete. In this particular instance I know exactly what you're saying and I agree, I'm not real crazy about how that works either, and will think on that some more and hopefully come up with a better solution. But in the meantime we've gotten rid of what was a redundant dialog and template (well the template's still in there but you know what I mean). Hmm, maybe those copy constructors would help here * I'd rather not see _any_ structs - use class's with all public members if needed. ? Where did I do that? Oh, right, that little one in the Window class (or did you find more, I try to use structs as little as possible too)? Just to be pendantic, a C++ struct *is* actually a class with all public members. * is chooser.o going to be equivalent to choose.o? If so then just fiddle choose.o please. I commit my changes quite frequently so we won't collide much. I honestly don't know yet. As is, it's just a field expedient to bring up your choose.o dialog easily and at the right time. It would be nice I think (as of this moment anyway) to bring that into the PropSheet as well, but I'm still trying to figure out whether that can work or not (issues such as resizing etc). Lastly, I think it would be a good idea (if possible) to do the refactoring bit-by-bit in future. i.e. factor in the Window class and the threeline progress bar. Then the class conversion for the pages. etc. That just reduces the risk of a huge commit. I agree completely, and that was in fact my original intent. As things went on though, I just couldn't see how that would really be possible or practical; the cvs would have been pretty badly broken for too long. Believe me when I tell you I had *zero* fun writing that 10K ChangeLog entry! But once this is checked in, I'm sure this will be a lot easier. Rob -- Gary R. Van Sickle Brewer. Patriot.
RE: [PATCH] Setup.exe in a property sheet
probably just friend the entire classes together, which will at least limit the cross-fertilization to two classes. Sure it's possible. AFAIK it's not possible to only expose particular functions to friends, but it's certainly possible to have a one way friendship. Right, no, it's the first part there that I was thinking about. Ok, sorry. I didn't purposely remove any, and thought they were an automatic CVS deal anyway. That's ok. The updates are, the creation isn't. Please also add to your new .cc files. Will do. [snip] cvs would have been pretty badly broken for too long. Believe me when I tell you I had *zero* fun writing that 10K ChangeLog entry! But once this is checked in, I'm sure this will be a lot easier. I know *exactly* what you mean regarding the ChangeLogs. To be honest I didn't look at yours yet - I figured it was too early in the piece. It's only going to get bigger Rob; like the t-shirt says, Procrastinate NOW!. ;-) Just to clarify, did you want me to get this diffed against the latest before you check any of it in? There's only one or two files that are diffed against non-current HEAD to my knowledge, but I can sure do it, but I'll need a hint as to how I can do a cvs update without bringing back a bunch of stuff that I'll need to cut right back out again. Or am I SOL and I'll just have to do it by hand? Rob -- Gary R. Van Sickle Brewer. Patriot.
[PATCH] Update 2 - Setup.exe property sheet patch
Changes as per your (Rob) last email, plus a few other improvements. Diff, new files, and ChangeLog attached. -- Gary R. Van Sickle Brewer. Patriot. setup.diff.bz2 Description: Binary data setup-newfiles.tar.bz2 Description: Binary data setup.ChangeLog Description: Binary data
Setup.exe new GUI preview
I figured before I went to bed tonight (er... this morning) I'd upload my latest build and source of the work I'm doing on Setup.exe's GUI for people to check out/comment on/pillorie/whatever. While not ready for public consumption, it does download and install Cygwin packages from the web as one would hope, and is largely feature-complete as far as the new GUI goes. File links are here: http://home.att.net/~g.r.vansickle/cygwin/setup/ Actual files are here: http://home.att.net/~g.r.vansickle/cygwin/setup/setup.exe http://home.att.net/~g.r.vansickle/cygwin/setup/setup-src.tar.bz2 So what's new and exciting here? Previously, setup.exe was a number of separate dialog boxes presented in sequence. I've taken the bulk of those dialogs and made them pages in a Wizard-style property sheet, which allows a number of improvements: - No more hide-and-seek where the dialogs end up at different places in the z-order as you next through them, without resorting to always on top. - One line of code, and now we have a minimize box in the corner. A lifesaver for those full Cygwin installs over a 56K modem if you ask me. - Much of the page navigation logic is now handled by the property sheet instead of the individual pages. So let me know what you think, -- Gary R. Van Sickle Brewer. Patriot.
RE: Setup.exe new GUI preview
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Robert Collins Sent: Monday, December 17, 2001 10:16 PM To: Gary R. Van Sickle; Cygwin-Apps Subject: Re: Setup.exe new GUI preview This hung for me, at 99% of the last pacakge, in download only mode. I guess that's not unexpected unfortunately. I've definitely concentrated on getting the mainline of installing from the internet working. Can you post a diff to cygwin-patches? Will do. I'll see if I can't fix the download-only problem first though, I'm pretty sure I know where that is. -- Gary R. Van Sickle Brewer. Patriot.
RE: mutt/procmail lock problem
From: Jason Tishler [mailto:[EMAIL PROTECTED]] Gary, I just discovered a locking problem with mutt 1.3.x that I believe also affects the mutt 1.2.x that you contributed to Cygwin. This lock problem caused procmail to misfile messages to the wrong mbox file when mutt happened to be writing to the mbox file that should have received the message. Under this situation, procmail complains to its logfile with error messages of the following form: Error while writing to x IMO, the root cause is due to incorrect group permissions for /var/spool/mail on the build machine: $ ls -ld /var/spool/mail drwxr-xr-x2 jtishler Administ0 Dec 17 09:06 /var/spool/mail ^ +--- should be writable Sure enough, it isn't here. Good catch! When built on such a machine, mutt's configure does not enable dotlocking: $ mutt -v Mutt 1.2.5i (2000-07-28) [snip] System: CYGWIN_NT-5.0 1.3.6(0.47/3/2) [using ncurses 5.2] Compile options: -DOMAIN -DEBUG -HOMESPOOL -USE_SETGID -USE_DOTLOCK +USE_FCNTL -USE_FLOCK I recommend fixing the permissions of /var/spool/mail on your machine: $ chmod g+w /var/spool/mail Done and done, and of course... it does nothing for me. Either with ntsec or no ntsec, ls -l comes back exactly the same. Dag nabbit. Well at least I know what needs fixing now. If I can't get the group permissions set right, perhaps I can force the configure somehow. and then releasing a new mutt package. Or perhaps... two? ;-) Thanks for the heads-up Jason, this is great info, especially since I don't use procmail currently and would otherwise probably never have caught this, let alone figured out what to do about it. -- Gary R. Van Sickle Brewer. Patriot. -- 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: rxvt and mutt incompatabilities
Is anybody out there running mutt and rxvt together? Yep. I get display problems and inconsistencies when I try to run mutt in rxvt. What kind of inconsitencies? I have literally no problems whatsoever. What do you set -tn to when you run rxvt? If I don't set it to anything, it will default to TERM=xterm, which works fine except mutt has no color (though stuff like ls --color works fine, go figure). If I set it to -tn rxvt, mutt gets color and everything is great. Just a hunch, what's your CYGWIN= set to? -- Gary R. Van Sickle Brewer. Patriot. -- 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: broken setup.hint files
Charles Wilson wrote: the hints may just be old. Originally, the spec for hint files said include curr and prev fields. Later, it was changed to that often causes confusion when folks forget to update the setup.hint. Don't include curr/prev fields unless you must Actually (assuming you're referring to http://cygwin.com/setup.html), there's nothing that specifically states or implies that prev/curr is use only if necessary. Rather the language is, In the event that a package doesn't sort correctly [...] use the setup.hint current, prev and exp labels to override the inbuilt sort during the transition period. That, especially due to the mention of exp, tells me that its optional rather than only-if-necessary. How about this: In the event that a package doesn't sort correctly (for example, from ...-9-... to ...-10-..., or from openssh-2.9p2-3 to openssh-2.9.9p2-1), the setup.hint curr: and prev: entries must be used to override the built-in sort. If your package *does* sort correctly, *don't* include curr: or prev: fields in your setup.hint; it will only serve to cause problems later on if, for instance, you forget to update it and nobody catches it. That said, I have a few questions on this that I'd appreciate if someone could clarify for me, as I'm trying to get a new and improved mutt package together: - The curr, prev, and test lines indicate which versions should be used for which sections of that package. If any of them are valid, they replace /all/ versions in setup.ini. What does that last sentence mean? Actually since the mutt packages will sort, I guess it's not that germain to me right now, but it could still use clarification. - Note that [setup.hint] must be in subdirectories named after the package (i.e. latest/cygwin/setup.hint is for the cygwin package). So... do I put my setup.hint in a latest/mutt-1.2.5i-6/setup.hint in my binary .tar.bz2? Or do I provide three files, foo-nnn-n.tar.bz2, foo-nnn.n-src.tar.bz2, and setup.hint? Or...? Thanks, -- Gary R. Van Sickle Brewer. Patriot.
RE: multiple mirror code setup HEAD
- Original Message - From: Gary R. Van Sickle [EMAIL PROTECTED] Building on cygwin-on-XP with all the cygwin stuff. Looks like a problem with my setup, I do actually have it in /usr/include/g++-3, but that's not on my GCC's include path for some reason. False alarm, sorry! ;-) Are you using gcc-3? Perhaps it changes what goes into lex? No, I'm using the cygwin distro one. I had however at one time been building 3.0 as a cross-compiler to Hitachi, and that's where I figured the /usr/include/g++-3 came from, but it ends up that's actually in the cygwin distro. So a GCC_INCLUDE= or whatever it is should fix me up AFAICT. Or are you saying that you don't see cstdlib in inilex.cc on your end? -- Gary R. Van Sickle Brewer. Patriot.
