Re: mkstemp bug
* Gary R. Van Sickle [EMAIL PROTECTED] [2005-04-28 21:01:07 -0500]: [snip] So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? I did not just tell you that they are broken. I also gave you a test case for FIFOs: Try mkfifo foo xterm -e 'tty foo; cat foo' (now foo can be used by other tty application to communicate with the user via the dedicated xterm - works in linux but not cygwin). I think such a test case is useful for development and debugging. Dude, you are just *asking* for one heck of a zinger! http://www.m-w.com/cgi-bin/netdict?zinger Sorry, I am not sure I understand what you mean. (PS it may be because English is not my native language...) -- Sam Steingold (http://www.podval.org/~sds) running w2k http://www.jihadwatch.org/ http://www.memri.org/ http://www.honestreporting.com http://pmw.org.il/ http://www.camera.org The only thing worse than X Windows: (X Windows) - X -- 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: mkstemp bug
On Apr 29 10:19, Sam Steingold wrote: * Gary R. Van Sickle [EMAIL PROTECTED] [2005-04-28 21:01:07 -0500]: Dude, you are just *asking* for one heck of a zinger! http://www.m-w.com/cgi-bin/netdict?zinger Sorry, I am not sure I understand what you mean. (PS it may be because English is not my native language...) It might not be important... 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/
Re: mkstemp bug
On Thu, Apr 28, 2005 at 09:01:07PM -0500, Gary R. Van Sickle wrote: [snip] So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? I did not just tell you that they are broken. I also gave you a test case for FIFOs. I think such a test case is useful for development and debugging. Dude, you are just *asking* for one heck of a zinger! Hey Gary! I'm responding to you again! (cue to Gary, in a Sound Of Music shot, arms outswept singing to the sky) I'm disappointed. I sent you the signed photograph that you kept pestering me for and I thought that now we'd be internet buddies. Was it because I didn't sign it Hugs and Kisses, cgf as you'd requested? I guess there just is no way to salve your poor hurt feelings and wounded ego and that means another couple of years of truly hilarious (and high class) references to me in your email. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: mkstemp bug
On Fri, Apr 29, 2005 at 10:19:56AM -0400, Sam Steingold wrote: * Gary R. Van Sickle [EMAIL PROTECTED] [2005-04-28 21:01:07 -0500]: [snip] So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? I did not just tell you that they are broken. I also gave you a test case for FIFOs: Try mkfifo foo xterm -e 'tty foo; cat foo' (now foo can be used by other tty application to communicate with the user via the dedicated xterm - works in linux but not cygwin). I think such a test case is useful for development and debugging. Dude, you are just *asking* for one heck of a zinger! http://www.m-w.com/cgi-bin/netdict?zinger Sorry, I am not sure I understand what you mean. (PS it may be because English is not my native language...) It's nothing to worry about. Gary spends a lot of time second guessing people, assuming that he knows what is going to happen, and sometimes even takes credit for people's behavior. He likes to inject personal attacks and observations into technical discussions. So, he was assuming that a message that you sent at 9AM EDT on Thursday was going to see some sort of harsh response more than twelve hours later. If you've read this list for any length of time you'll note that Gary rarely offers anything of merit to a discussion. He usually wanders in hours after a discussion has wound down and either offers duplicate advice or uses the discussion as a platform for an ad hominem innuendo. That is not to say that he doesn't occasionally have a good idea. Who can forget Cyppy, after all? http://www.cygwin.com/ml/cygwin/2003-02/msg00084.html 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: mkstemp bug
On Thu, Apr 28, 2005 at 09:01:07PM -0500, Gary R. Van Sickle wrote: [snip] So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? I did not just tell you that they are broken. I also gave you a test case for FIFOs. I think such a test case is useful for development and debugging. Dude, you are just *asking* for one heck of a zinger! Hey Gary! I'm responding to you again! Oh heavens! I hope its manic day! At any rate, I do appreciate the public, as opposed to private, responses. (cue to Gary, in a Sound Of Music shot, arms outswept singing to the sky) Yeah, don't really get that one, sorry. I hope it isn't important. No wait, I hope it *is* important, otherwise I'd have to throw a fit because it was off-topic. No, wait, I mean I'm disappointed. Well we can't have that! The entire Cygwin project exists explicitly to *prevent* that! What can I do to sooth your damaged ego, my dear man? I sent you the signed photograph that you kept pestering me for and I thought that now we'd be internet buddies. Was it because I didn't sign it Hugs and Kisses, cgf as you'd requested? If you aren't just pulling somebody's leg there: - I never requested any such photograph. - I never received any such photograph. - You told me before we were email enemies or some gosh dern thing, now we're internet buddies? I frankly don't know what either term is supposed to mean, but they both sound pretty creepy. - Didn't this list buy you a new laptop at some point? - Didn't this list also buy you a hyperthreaded machine a while back? - Don't you feel even a little sheepish when you repay that with childish tantrums that aren't even explicable, let alone warranted? I guess there just is no way to salve your poor hurt feelings and wounded ego Wait, now it's *me* that's got the wounded ego? I don't follow. I don't do inexplicable things such as, oh, I don't know, make snide comments when somebody *agrees* with a statement I make in a cygwin@ post (feel free to spend hours scouring the archives for evidence to the contrary though, but don't expect that to ease the pain; for that, I'd simply suggest again that you get over me). and that means another couple of years of truly hilarious (and high class) references to me in your email. *blush* I do have a way with words, don't I? Oh, and Chris, seriously, I don't think you should be talking to anybody about high class when you're making smart-a** comments to people who are doing what they can to help the project. Oh, sorry, your project. But maybe Sam can speak to that better than I - oh I see he has. Never mind. -- Gary R. Van Sickle -- 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: mkstemp bug
* Gary R. Van Sickle [EMAIL PROTECTED] [2005-04-28 21:01:07 -0500]: [snip] So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? I did not just tell you that they are broken. I also gave you a test case for FIFOs: Try mkfifo foo xterm -e 'tty foo; cat foo' (now foo can be used by other tty application to communicate with the user via the dedicated xterm - works in linux but not cygwin). I think such a test case is useful for development and debugging. Dude, you are just *asking* for one heck of a zinger! http://www.m-w.com/cgi-bin/netdict?zinger Sorry, I am not sure I understand what you mean. (PS it may be because English is not my native language...) Oh, sorry, by zinger I was referring to a type of response such as the snotty one you got in reply to your statement Yes, it appears that they are heavily broken and your test case. And no need to be sorry; I do tend to abuse the English language rather badly. -- Gary R. Van Sickle -- 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: mkstemp bug
On Fri, Apr 29, 2005 at 10:19:56AM -0400, Sam Steingold wrote: * Gary R. Van Sickle [EMAIL PROTECTED] [2005-04-28 21:01:07 -0500]: [snip] So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? I did not just tell you that they are broken. I also gave you a test case for FIFOs: Try mkfifo foo xterm -e 'tty foo; cat foo' (now foo can be used by other tty application to communicate with the user via the dedicated xterm - works in linux but not cygwin). I think such a test case is useful for development and debugging. Dude, you are just *asking* for one heck of a zinger! http://www.m-w.com/cgi-bin/netdict?zinger Sorry, I am not sure I understand what you mean. (PS it may be because English is not my native language...) It's nothing to worry about. Gary spends a lot of time second guessing people, assuming that he knows what is going to happen, and sometimes even takes credit for people's behavior. He likes to inject personal attacks and observations into technical discussions. Quick quiz Chris. 1. Who made this statement?: So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? 2. For what possible reason did that person make that statement? 3. Such statements advance the discussion how, exactly? So, he was assuming that a message that you sent at 9AM EDT on Thursday was going to see some sort of harsh response more than twelve hours later. If you've read this list for any length of time you'll note that Gary rarely offers anything of merit to a discussion. Not sure about that, but I do know that I rarely take anybody to task for helping. Who amongst us can cast that first stone? He usually wanders in hours after a discussion has wound down and either offers duplicate advice or uses the discussion as a platform for an ad hominem innuendo. No, I usually avoid innuendo, and try to make my statements as clear as possible. Innuendo is for high class folks, ain't it? That is not to say that he doesn't occasionally have a good idea. Who can forget Cyppy, after all? http://www.cygwin.com/ml/cygwin/2003-02/msg00084.html Indeed! Cyppy was a big hit. Who knows, maybe he'll still pop up some day! But also don't forget that I'll occasionally rewrite large portions of the setup app when others don't want to. We all remember the dialog box days shudder, do we not? cgf Wow, I had no idea I bothered you so Chris - well, no more than every other person in the world apparently bothers you anyway - nor that you kept such close tabs on how many hours pass between a post and my reply to that post. I'm impressed, and by impressed I of course mean terribly saddened that somebody as obviously talented as you is filled with such inexplicable animosity toward his fellow man. Dude, seriously, get over me. Get over yourself. Have a homebrew. Try to enjoy life, and by life I don't mean the number of hours it takes Gary, my hated nemesis who has the nerve to call me on my poor behavior (on my own personal turf no less!), to respond to a post. Oh, and perhaps most importantly, take to heart this verse from Ecclesiastes: A time to be a jerk, and a time to behave yourself. To everything there is a season, my good man. Turn, turn, turn. -- Gary R. Van Sickle -- 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: mkstemp bug
On Fri, Apr 29, 2005 at 07:39:04PM -0500, Gary R. Van Sickle wrote: On Thu, Apr 28, 2005 at 09:01:07PM -0500, Gary R. Van Sickle wrote: [snip] So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? I did not just tell you that they are broken. I also gave you a test case for FIFOs. I think such a test case is useful for development and debugging. Dude, you are just *asking* for one heck of a zinger! Hey Gary! I'm responding to you again! Oh heavens! I hope its manic day! At any rate, I do appreciate the public, as opposed to private, responses. Hmm. Let's see if I can respond to this without questioning *your* mental state. It's going to be very hard but I will try. (cue to Gary, in a Sound Of Music shot, arms outswept singing to the sky) Yeah, don't really get that one, sorry. Ya see, Gary. I haven't been responding to you for years but you've been calling me names in email every few months. Sometimes you respond to something I've said. Sometimes you you feel the need to comment on what you think I'm going to do. Sometimes you speculate that you've done something to change my behavior. You did all this while I was almost completely silent. That led me to believe that you were desperately hoping for some contact with me. I can see that I must have been somewhat right given the length of your reply. Anyway, I'm glad I've finally given your urges some tangible outlet. I sent you the signed photograph that you kept pestering me for and I thought that now we'd be internet buddies. Was it because I didn't sign it Hugs and Kisses, cgf as you'd requested? If you aren't just pulling somebody's leg there: - I never requested any such photograph. - I never received any such photograph. Right. Gotcha. *wink* 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: mkstemp bug
On Fri, Apr 29, 2005 at 08:19:45PM -0500, Gary R. Van Sickle wrote: Dude, seriously, get over me. Here's how email works. You send email. Someone either responds or doesn't respond. For a while I didn't respond but you kept sending. I'm responding now. I'm trying to do so in the fashion that you have typified. I think I'm doing just what you wanted. I'm using you as an example for how I should comport myself. I haven't yet gotten to the point where I feel comfortable speculating about your sanity or questioning your childhood. I am thinking about maybe branching out and commenting on your hygiene or maybe imagining some kind of comical drinking problem, though. Oh, wait. I forgot to demand something from you. How can I claim to be trying to emulate you if I didn't demand something? Where's the apology for using the name of the Lord in vain? Afraid to admit you were wrong? 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: mkstemp bug
* Christopher Faylor [EMAIL PROTECTED] [2005-04-27 22:29:34 -0400]: On Wed, Apr 27, 2005 at 07:39:37PM -0400, Sam Steingold wrote: * Christopher Faylor [EMAIL PROTECTED] [2005-04-27 18:20:31 -0400]: the problem is that mkstemp() does not regard FIFOs (as created by mkfifo() or mknod()) as existing files. e.g. char s1[] = /tmp/foo-XX; char s2[] = /tmp/foo-XX; int fd = mkstemp(s1); close(fd); remove(s1); mkfifo(s1,0644); mkstemp(s2); strcmp(s1,s2) === 0 fifos just barely work under cygwin. I wouldn't recommend using them. Yes, it appears that they are heavily broken. So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? I did not just tell you that they are broken. I also gave you a test case for FIFOs. I think such a test case is useful for development and debugging. -- Sam Steingold (http://www.podval.org/~sds) running w2k http://www.openvotingconsortium.org/ http://www.camera.org http://www.honestreporting.com http://www.dhimmi.com/ http://ffii.org/ Isn't Microsoft Works an advertisement lie? -- 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: mkstemp bug
[snip] So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? I did not just tell you that they are broken. I also gave you a test case for FIFOs. I think such a test case is useful for development and debugging. Dude, you are just *asking* for one heck of a zinger! ;-) -- Gary R. Van Sickle -- 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: mkstemp bug
I'm surprised your example doesn't segfault. My Linux man page says explicitly that the template should not be a string constant but must be a character array, i.e. use char t1[] = /tmp/clisp-x-io-XX; char t2[] = /tmp/clisp-x-io-XX; char t3[] = /tmp/clisp-x-io-XX; mkstemp(t1); mkstemp(t2); mkstemp(t3); instead. Tony Richardson p.s. Don't use char *t1 = /tmp/clisp-x-io-XX; either. It's not the same. Constant strings like this and in your original program can be stored in a read-only segment and so are not necessarily writeable. Sam Steingold wrote: Hi, it appears that mkstemp() returns a temp FD pointing to the same file: mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 -- 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: mkstemp bug
* Tony Richardson [EMAIL PROTECTED] [2005-04-27 12:41:20 -0500]: I'm surprised your example doesn't segfault. My Linux man page says explicitly that the template should not be a string constant but must be a character array, i.e. use char t1[] = /tmp/clisp-x-io-XX; char t2[] = /tmp/clisp-x-io-XX; char t3[] = /tmp/clisp-x-io-XX; mkstemp(t1); mkstemp(t2); mkstemp(t3); instead. that's what I did. I was sloppy in my posting. the strings passed to mkstemp where explicitly allocated with alloca and properly filled. -- Sam Steingold (http://www.podval.org/~sds) running w2k http://ffii.org/ http://www.dhimmi.com/ http://www.mideasttruth.com/ http://www.honestreporting.com http://www.memri.org/ The world is coming to an end. Please log off. -- 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: mkstemp bug
Sam Steingold: * Tony Richardson [EMAIL PROTECTED] I'm surprised your example doesn't segfault. My Linux man page says explicitly that the template should not be a string constant but must be a character array, i.e. use char t1[] = /tmp/clisp-x-io-XX; char t2[] = /tmp/clisp-x-io-XX; char t3[] = /tmp/clisp-x-io-XX; mkstemp(t1); mkstemp(t2); mkstemp(t3); instead. that's what I did. I was sloppy in my posting. the strings passed to mkstemp where explicitly allocated with alloca and properly filled. I'm sorry for misreading your post. I can see that what you posted wasn't actual code. mkstemp() works fine for me though. Cygwin version 1.5.15 and Win XP. 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: mkstemp bug
* Sam Steingold [EMAIL PROTECTED] [2005-04-27 13:24:29 -0400]: it appears that mkstemp() returns a temp FD pointing to the same file: mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 this is note quite as easy to reproduce. sorry. the problem is that mkstemp() does not regard FIFOs (as created by mkfifo() or mknod()) as existing files. e.g. char s1[] = /tmp/foo-XX; char s2[] = /tmp/foo-XX; int fd = mkstemp(s1); close(fd); remove(s1); mkfifo(s1,0644); mkstemp(s2); strcmp(s1,s2) === 0 -- Sam Steingold (http://www.podval.org/~sds) running w2k http://www.openvotingconsortium.org/ http://www.camera.org http://www.jihadwatch.org/ http://www.memri.org/ http://pmw.org.il/ Do not worry about which side your bread is buttered on: you eat BOTH sides. -- 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: mkstemp bug
On Wed, Apr 27, 2005 at 06:06:09PM -0400, Sam Steingold wrote: * Sam Steingold [EMAIL PROTECTED] [2005-04-27 13:24:29 -0400]: it appears that mkstemp() returns a temp FD pointing to the same file: mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 this is note quite as easy to reproduce. sorry. the problem is that mkstemp() does not regard FIFOs (as created by mkfifo() or mknod()) as existing files. e.g. char s1[] = /tmp/foo-XX; char s2[] = /tmp/foo-XX; int fd = mkstemp(s1); close(fd); remove(s1); mkfifo(s1,0644); mkstemp(s2); strcmp(s1,s2) === 0 fifos just barely work under cygwin. I wouldn't recommend using them. 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: mkstemp bug
On Wed, Apr 27, 2005 at 07:39:37PM -0400, Sam Steingold wrote: * Christopher Faylor [EMAIL PROTECTED] [2005-04-27 18:20:31 -0400]: On Wed, Apr 27, 2005 at 06:06:09PM -0400, Sam Steingold wrote: * Sam Steingold [EMAIL PROTECTED] [2005-04-27 13:24:29 -0400]: it appears that mkstemp() returns a temp FD pointing to the same file: mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 this is note quite as easy to reproduce. sorry. the problem is that mkstemp() does not regard FIFOs (as created by mkfifo() or mknod()) as existing files. e.g. char s1[] = /tmp/foo-XX; char s2[] = /tmp/foo-XX; int fd = mkstemp(s1); close(fd); remove(s1); mkfifo(s1,0644); mkstemp(s2); strcmp(s1,s2) === 0 fifos just barely work under cygwin. I wouldn't recommend using them. Yes, it appears that they are heavily broken. So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? 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: mkstemp bug
On Wed, Apr 27, 2005 at 06:06:09PM -0400, Sam Steingold wrote: * Sam Steingold [EMAIL PROTECTED] [2005-04-27 13:24:29 -0400]: it appears that mkstemp() returns a temp FD pointing to the same file: mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 mkstemp (/tmp/clisp-x-io-XX); == /tmp/clisp-x-io-000592 this is note quite as easy to reproduce. sorry. the problem is that mkstemp() does not regard FIFOs (as created by mkfifo() or mknod()) as existing files. e.g. char s1[] = /tmp/foo-XX; char s2[] = /tmp/foo-XX; int fd = mkstemp(s1); close(fd); remove(s1); mkfifo(s1,0644); mkstemp(s2); strcmp(s1,s2) === 0 This has been fixed in CVS. 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: mkstemp bug
fifos just barely work under cygwin. I wouldn't recommend using them. Yes, it appears that they are heavily broken. So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? cgf And your pathological touchiness serves what purpose exactly? Take your meds already. Christ. -- Gary R. Van Sickle -- 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: mkstemp bug
On Wed, Apr 27, 2005 at 11:26:32PM -0500, Gary R. Van Sickle wrote: fifos just barely work under cygwin. I wouldn't recommend using them. Yes, it appears that they are heavily broken. So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? And your pathological touchiness serves what purpose exactly? Take your meds already. Christ. Ah, Gary. There you are. When I don't hear from my groupies in a long while I get sort of concerned. Is that poster I sent you serving you well? Or have you used it all up by now? 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: mkstemp bug
On Wed, Apr 27, 2005 at 11:26:32PM -0500, Gary R. Van Sickle wrote: fifos just barely work under cygwin. I wouldn't recommend using them. Yes, it appears that they are heavily broken. So when I say fifos just barely work you felt the need to inform me that they don't work? And that advances the discussion how, exactly? And your pathological touchiness serves what purpose exactly? Take your meds already. Christ. By the way, I think I've previously implied that I don't appreciate the use of this kind of profanity here. I would appreciate it if you would refrain from using this type of language in the cygwin mailing lists. Re: http://www.cygwin.com/ml/cygwin/2003-03/msg00299.html 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/
