RE: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
At 08:47 PM 7/11/2004, you wrote: On Sat, Jul 10, 2004 at 09:54:05AM -0500, Eduardo Chappa wrote: That was CGF himself, he volunteered to not to volunteer. He brought this topic onto himself. This statement is disingenuous. For shame. Perhaps, perhaps not. I'm still waiting for somebody, other than you Chris[1], to tell me who asked you to do anything about anything discussed here (prior to the replied-to post; I see there was a deal subsequently proposed that did in fact ask for some tit-for-tat action). [1] This exception is of course an attempt to help prevent this message from being misinterpreted as a demand for you to do anything. It is not, and is not to be misconstrued as such. Nor, in fact, is it to be construed as a demand for anybody else to do anything either. One would hope this would be clear from the complete lack of demands or implications of demands contained herin, but when in Rome Oh, and BTW, whatever anybody wants to convince themselves of, if you're pointing folks to Google to get info out of your archives (which contain their own seach feature), your archives are broken. DISCLAIMER: That was the Royal Your, not to be construed as Chris' archives etc. Remember, denial is stage one. I'm not sure what you're looking to get from someone responding to your inquiry Simply clarification on who did the deed. If in fact a deed was done. but from my perspective, based on what you've said, this just prolongs a thread that has drifted beyond the scope of the original inquiry and no longer serves a constructive purpose. If you can succinctly point to one, then perhaps it's still worthwhile to continue this thread. Last I checked we were talking about broken archives, for some definition of broken anyway. You'll note that my post mentions a shortcoming I've noticed pertaining to that very subject. At the same time you are of course right, there is no point in continuing this thread. It has served its purpose... if that purpose was to get a maintainer to quit. Otherwise, let's just let it die and move on. I think all relevant points have been made already. Indeed. Truth is the most valuable thing we have. Let us economise it. - Mark Twain -- 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: cygwin: /proc and /cygdrive insvisible
Mit freundlichen Grüssen, ? With friendly Grüssen. I knew that high school German would come in handy some day... ;-) -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
On Sat, Jul 10, 2004 at 09:54:05AM -0500, Eduardo Chappa wrote: That was CGF himself, he volunteered to not to volunteer. He brought this topic onto himself. This statement is disingenuous. For shame. Perhaps, perhaps not. I'm still waiting for somebody, other than you Chris[1], to tell me who asked you to do anything about anything discussed here (prior to the replied-to post; I see there was a deal subsequently proposed that did in fact ask for some tit-for-tat action). [1] This exception is of course an attempt to help prevent this message from being misinterpreted as a demand for you to do anything. It is not, and is not to be misconstrued as such. Nor, in fact, is it to be construed as a demand for anybody else to do anything either. One would hope this would be clear from the complete lack of demands or implications of demands contained herin, but when in Rome Oh, and BTW, whatever anybody wants to convince themselves of, if you're pointing folks to Google to get info out of your archives (which contain their own seach feature), your archives are broken. DISCLAIMER: That was the Royal Your, not to be construed as Chris' archives etc. Remember, denial is stage one. -- 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: PCYMTNQREAIYR Please Configure Your Mailer To Not Quote Raw E-mail Addresses In Your Replies.
On Sun, July 11, 2004 10:22 pm, LDR said: --- Igor Pechtchanski [EMAIL PROTECTED] wrote: *PCYMTNQREAIYR* -- Please Configure Your Mailer To Not Quote Raw E-mail Addresses In Your Replies. http://cygwin.com/acronyms/#PCYMTNQREAIYR. - What mailers (mail clients?) do support this auto-editing function? - Does Mozilla? Lee Well, if you're using outlook/outlook express, there's a program called Outlook-quotefix or OE-quotefix, depending on which you're using. They latch into outlook/oe to provide this functionality. Are you sure this is true? I downloaded it and can't get it to provide that functionality. Am I missing some checkbox somewhere? -- 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: PCYMTNQREAIYR Please Configure Your Mailer To Not Quote Raw E-mail Addresses In Your Replies.
cygwin-ownerXXXYOU_KNOW_THE_REST wrote on Sunday, July 11, 2004 7:54 PM: On Sun, July 11, 2004 10:22 pm, LDR said: --- Igor Pechtchanski [EMAIL PROTECTED] wrote: *PCYMTNQREAIYR* -- Please Configure Your Mailer To Not Quote Raw E-mail Addresses In Your Replies. http://cygwin.com/acronyms/#PCYMTNQREAIYR. - What mailers (mail clients?) do support this auto-editing function? - Does Mozilla? Lee Well, if you're using outlook/outlook express, there's a program called Outlook-quotefix or OE-quotefix, depending on which you're using. They latch into outlook/oe to provide this functionality. Are you sure this is true? I downloaded it and can't get it to provide that functionality. Am I missing some checkbox somewhere? -- Gary R. Van Sickle Ok, it can be configured to do what's mentioned in the acronym dealy, but it will always say something like: Cygwin Owner wrote on Wednesday, Smarch 25 So I guess it can't hurt, but -- 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: Extending long threads
GARY VANSICKLE wrote: There's three reasons people knee-jerk against HTML email: 1. It isn't ASCII (i.e. the Back in my day a child would open up a gift and within seconds he'd either burst into flames or lose a limb! That's the way it was and we liked it![1] Defense). 2a. There isn't an email program alive which can do a Reply to an HTML email properly. I'm using one right now... Mozilla (Thunderbird) handles replying to HTML email just fine. Yep, it does the best job last I checked. 2b. ...especially those which support VT-100 terminals. 3. The lines are longer than 80 characters ;-). I fall under category 2a, but my knee isn't jerking: If Outlook didn't absolutely s*ck *ss at editing HTML I wouldn't care. You can't blame everything on your choice to use Outlook. I don't blame anything on my choice to use Outlook. -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Responding before I read the whole thread, as I'm sure this gets a whole lot uglier: On Jul 9 11:03, William Blunn wrote: I think not. I think the counter argument would be Yes we know it makes the occasional command-line appear line-wrapped, but that is a nano-issue compared to the downside which is that it will mess up the display for all the flowed messages, which is a far bigger issue. My 2ct are simply this: If somebody wants to be read, he or she should stick to the common rules. Common rules? I prefer to stick to Standards if at all possible. Like RFCs and such. If somebody isn't able or willing to learn these rules, bad luck for him or her. I'm against pampering clueless people so that they can lean back and stay clueless. Call me mean. You're mean ;-). -- 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: Extending long threads (was: RE: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?))
As a person who regularly uses HTML style email and posting (much to many peoples chargrin and complaints) I rarely fester them with all sorts of colors and fonts. Other HTML emails and posts I receive are also rarely festered with all sorts of colors and fonts. Why? Because doing so takes time, knowledge and effort and most people simply don't take the time, have the knowledge nor can be bothered with the effort required. As such I don't think such an argument holds much water. IOW I think if people of your opinion see just one bolding they'll call it festered with all sorts of colors and fonts. There's three reasons people knee-jerk against HTML email: 1. It isn't ASCII (i.e. the Back in my day a child would open up a gift and within seconds he'd either burst into flames or lose a limb! That's the way it was and we liked it![1] Defense). 2a. There isn't an email program alive which can do a Reply to an HTML email properly. 2b. ...especially those which support VT-100 terminals. 3. The lines are longer than 80 characters ;-). I fall under category 2a, but my knee isn't jerking: If Outlook didn't absolutely s*ck *ss at editing HTML I wouldn't care. -- Gary R. Van Sickle [1] Dana Carvey, Grumpy Old Man, SNL -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
Nobody's trying to force you to read. You shouldn't try to force them to write in a particular style. In the end communication, at least civil communication and I'd say any communication that is, in the long term, successsful, always requires *compromise* on both parties. Your stated opinion, Corina, is uncompromising. Hit the bricks DeFaria, we don't need your cool head and clear thinking 'round these parts! ;-) -- 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: Wrapping long lines (Was Re: FAQ update suggestion for I'm having basic problems with find. Why?)
I never used the word fix, please do not misunderstand me. I refer to this as enhance. Yes, it is broken, by the way. So, it's broken and you want me to enhance it so that it won't be broken anymore but you were not suggesting a fix. Got it. Can somebody show me where anybody made even the slightest indication that they want Chris do anything with respect to this? DISCLAIMER: I am not asking Chris to do anything with respect to this post. -- 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: higher-level IO very slow with cygwin1.dll 5.10 (due to set_flags?)
Possibly I should add that I am comparing the behavior of version 1.5.10 to a much older version that I was using before. It wasn't by chance... oh... say... B20? ;-) So whatever is causing this odd behavior on my system may not be a feature that was new to version 1.5.10. I am thinking somehow that it might in fact have something to do with how mounts are handled differently in more recent versions. Previously I did not have to mount any directories, Yikes. I can't recall a time when you didn't have to mount directories, and I've been round these parts forever. That must be some *old* Cygwin! now though I am having trouble finding any set of mount commands that will allow me to open files in text mode by default, which was how the earlier version of cygwin I had worked. Nor does setting the CYGWIN environment variable to nobinmode seem to have any effect. Don't worry about the CYGWIN var anymore, it's all mounts these days. mount --help and umount --help is what you want. Set up your mount table like this: C:\unix\bin on /usr/bin type system (textmode) C:\unix\lib on /usr/lib type system (textmode) C:\unix on / type system (textmode) c: on /cygdrive/c type user (textmode,noumount) d: on /cygdrive/d type user (textmode,noumount) e: on /cygdrive/e type user (textmode,noumount) And you're all set. You have to umount before mounting if any of the directories are already mounted unfortunately (last I checked anyway). -- 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/ -- 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: Delete key... was home directory.
Am I the only one that thinks reading a 12 page document, and possibly editing 5 different config files is a hell of a lot of work just to get the delete key to work?!?!?! You want to make the delete key delete in bash? No, he just wants the delete key to work as God intended it to work. The chapter about bash isn't even one page long. That's too long. Browsing the document would help you to understand why solving your problem in bash won't solve it in all other application (zsh, vim, mutt, X). Nobody wants to understand why certain keys don't work in Unix the way they should. They just want the keys to work. Refusing to read and learn isn't going to get you anywhere - especially in a Unix/Cygwin environment. I agree. The Unii of the world should take a page from the playbook of every other OS which ever existed, and read the part where it says, The delete key deletes stuff without all kinds of configuration contortions by the user. -- 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: Generic build script instructions
So, to answer that question, why not something like this:
# --- BEGIN_DEFS ---
if [ -f ${FULLPKG}.defs ]; then
. ${FULLPKG}.defs
fi
# --- END_DEFS ---
So, if my source package name is foo.tar.Z, then I can put the
[snip]
following in my defs file:
# Maintainer defs file for package foo
src_orig_pkg_name=foo.tar.Z
opt_decomp=z
This would allow a package maintainer to put specializatons/
definitions within a defs file for each package, making for
easier maintentance (except in cases of siginificantly unusual
packages).
That's the first thing that came to my mind when I switched over to using
gbs for packaging mutt. I'd put an else clause in though and croak if
there's no defs file.
--
Gary R. Van Sickle
[SEMI-OT]: XP SP2 (was: RE: Unable to open files including Korean names)
Hello from Gregg C Levine Actually Gary, its called SP2 RC1, for XP. Its going through that phase, with SP1 RC2 due out towards the end of the month, and the actual SP2 going to the RTM phase so that its in time to be released by the 21 July, date. (If you can believe that.) I of course cannot. ;-) Also, can you tell me, off list, where you got your copy? I was at an OEM meeting for that guy's operating system, yesterday. The meeting was held here in NYC. Well, I'll reply to both in case anybody else is interested. It's available for download right off of msdn.microsoft.com, 200MB plus tax. I've only been using it for a few days now, but everything Cygwin that I use (gcc et al, perl, rxvt, etc) seems to still work fine. There's all kinds of massive security-related changes that I'm guessing could raise hell with a few programs though. Helpful hint though to anybody brave/foolish enough to install it: don't bother reporting any Cygwin problems to Cygwin until SP2 is actually released; doing so will serve no purpose. Probably can't hurt to send bug reports to MS though. One change that they're making could be a gigantic problem for Cygwin: Finally, after all these years, Windows will be keeping the hot side hot and the cool side cool, or in non-McDLT-speak, tagging program and data memory areas and preventing code execution in data areas. This is a good (fantabulous?) if belated feature, but if I understand fork() correctly (which I don't), doesn't fork() allocate memory, copy some data and code over, and jump to the code? From what I read I think this would no longer work. -- 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: Unable to open files including Korean names
I did some test and found out that ``every file whose path includes Korean characters weren't openable.'' Still, I could move arround those [snip] I just installed the XP SP2 preview or whatever they call it. One of the things in the very long list of things it claims to fix is some problem with... Japanese I think?... filenames. Perhaps this is in some way related to that... As I remember, there wasn't any problem like this before my update few days ago. [snip] ...or possibly not. -- 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: Please include unsubscribe information in announcement email
I hesitate to enforce a standard template for all announcements but I really would like to see people start including unsubscribe instructions in their announcement email. Please do me a favor and include unsubscribe instructions in your announcement email. Please just copy the few lines that I put in my last cygwin DLL release announcement. cgf Huh? Can't whoever's running the mailing list now just set things up to put the same unsubscribe info that's on every post in [EMAIL PROTECTED] Wait, won't it be there anyway? -- Gary R. Van Sickle
RE: more pain - YAM
When you send messages to a mailing list, you invite discussion. That is why we have mailing lists. Well, that's why other organizations have mailing lists anyway. (Please send all we're just means to the list or not at all. I have a very thin skin and get offended if somebody sends me tantrums via personal email. TIA.) -- 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: flushall
Not sure what an hdf5 is, but in general it is not possible to do sync-to-backing-storage from an arbitrary account in Windows. Not even on removable media, which of course is where you often need it most. Microsoft's rationale behind this escapes me, but there it is. Furthermore, even when you can do it, the method is completely different in Win9x and the NT series. Gary Are you saying this can be done with admin privs? Yep. Where would I find out how to do this on NT? I think you have to look in the Windows DDK documentation, under mass storage IOCTLs. You essentially have to do the following: 1. Get a handle to the physical disk. IIRC this is the real trick, because for some reason it's almost impossible to map a volume back to a physical disk or disks. But I was trying to commit volumes to backing store; if you're really trying to emulate sync() you might just be able to enumerate all physical disks and commit them. 2. Lock the disk. This is what requires the admin privs. 3. Send the sync message. 4. Unlock the disk. 5. Close the handle. This is all done (again, on the NT-XP series) by sending IOCTLs. I don't recall the exact details unfortunately; I did this quite a while ago, and am still suffering from PTSD ;-). IIRC, once you get it figured out (no thanks to Microsoft), it's not that big a deal, but like everything else it's the figuring-out part that's the problem. Keep in mind though that neither sync() nor the sync command (as I understand it) are actually guaranteed to do *anything at all*, even on Unii. To wit: http://www.opengroup.org/onlinepubs/007908799/xsh/sync.html The sync() function causes all information in memory that updates file systems to be scheduled for writing out to all file systems. The writing, although scheduled, is not necessarily complete upon return from sync(). Since this scheduling must by definition be done at the end of every call that is intended to modified the disk (e.g. the modification is either complete or scheduled to be completed when write() returns), Cygwin's stub is a conforming implementation. And since FWICT the sync command is only required to call sync, it isn't actually required to do anything either. What I'm getting at here is, make sure you really truly need to sync to the physical media before spending all kinds of time fighting this one. What does hdf5 use this for? Thanks, david HTH, -- 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: flushall
I'm trying to port some code that uses flushall() to cygwin. The non-windows version of the code uses 'system(sync)' but this fails the builtin tests. The code is hdf5-1.6.2, in case that helps. Not sure what an hdf5 is, but in general it is not possible to do sync-to-backing-storage from an arbitrary account in Windows. Not even on removable media, which of course is where you often need it most. Microsoft's rationale behind this escapes me, but there it is. Furthermore, even when you can do it, the method is completely different in Win9x and the NT series. This functionality could probably be added to the cygserver by somebody with sufficient reason to do so. Until that happens, if you really truly need an all-the-way-to-the-media flush in cygwin, you're SOL. -- 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: Data loss in Cygwin's creator?
I got this *System Error* message in my e-mail: *plonk* Ahh... cgf I'm concerned that creator might be dropping some critical data. However someone more knowledgeable in these matters will have debug this. I also don't have a 64 sheet test roll installed in my bathroom. Brian Kelly Heheheheeh! Good humor. Maybe Charmin would be willing to donate a dual-ply 64-sheet test roll ;-). -- 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: Data loss in Cygwin's creator?
I got this *System Error* message in my e-mail: *plonk* Ahh... cgf I'm concerned that creator might be dropping some critical data. However someone more knowledgeable in these matters will have debug this. I also don't have a 64 sheet test roll installed in my bathroom. Brian Kelly BTW: CGF is not Cygwin's creator. -- 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: Maildir and Cygwin
On Thu, Apr 22, 2004 at 08:26:00AM -0700, Eduardo Chappa wrote: :) that Cygwin is different (e.g. we could do this in the cygwin :) applications mailing list). :) :) Why do you want to change so many programs when all you need is a :) cygwin managed mount? IMO, the correct solution for mutt to make everyone happy would be a new configuration variable to specify the character (presumably defaulting to non-: for cygwin). I think I've seen both ; and - suggested in different places. No, all that would do is guarantee that a mutt using ; couldn't read a Maildir written by a fetchmail using - (i.e. the disagreement would simply move from being hardcoded to being defined at compile time). The correct solution is to implement a corrected spec. -- 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: Maildir and Cygwin
Hello, I have been trying to fix a patch for maildir for Pine, and while thinking about this I recalled that support for Maildir in Cygwin (e.g Mutt) has been discussed a couple of times. It seems to be that the only thing stopping people from being able to use it is a agreement on the format of the name among the different programs that do maildir. Explicitly this means to deprecate the use of : in the filename. I've been testing the maildir patch (for Pine) and changing : to ; works perfectly well, so I was wondering how compatible is this with other tools designed for maildir. I am not advocating for the use of ;, I am asking the questions as to Can we agree to use something different than ':'? and Can we use ';'?. Thanks for your feedback! Well first of all, remember that managed mounts do seem to allow Maildirs to work on Cygwin, so that's an interim solution. However, to get to the core of the problem: I guess it depends on who the we is, and how many wes there are. Maildir is, AFAICT, less of a spec and more of a web page somebody put up. I have no idea how many apps are using this format, though I guess the only thing we care about for the most part is which Cygwin ports use it. What would be best though is to clean up the Maildir spec and push it upstream; probably a rather Herculean task. To have any chance of success, I'd almost guarantee[1] that any Maildir 2 spec would have to add more value than POSIX-compatible filenames. I don't know what that might be, but there's always something that can be improved or added to anything. As sometimes-maintainer of Mutt, I'm certainly willing to agree to use something different than ':'. However, I'm also an upstream release behind, and not seeing the light at the end of the no-time tunnel. -- Gary R. Van Sickle Brewer. Patriot. [1] This is not a guarantee. -- 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: Comparative Performance of C++ Compilers (including gcc cygming special)
[snip] New copying methods have been added and checked: Test file modes : text, binary -- Testsuites -- C-01 : Functions getc() and putc() C-02 : Functions fgetc() and fputc() C-03 : Functions fread() and fwrite() UNIX-C-04 : Function mmap CPP-01: Operators and CPP-02: Methods get() and put() CPP-03: Methods sbumpc() and sputc() CPP-04: Method sbumpc() and operator CPP-05: Method rdbuf() and operator CPP-06: Methods read() and write() with const buffer CPP-07: Methods read() and write() with max buffer CPP-08: Method getline CPP-09: Method ifstream getline CPP-10: Method iterators (istream_iterator, ostream_iterator) See: http://article.gmane.org/gmane.comp.lang.c++.perfometer/45 http://article.gmane.org/gmane.comp.lang.c++.perfometer/44 So much reading... I need charts and/or graphs man! ;-) -- 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: working sync() code
Hi all,
I found a way to issue an actual sync() on win32, and as browsing
through winsup directory gave me only this
winsup/sygwin/syscalls.cc #1128
extern C int
sync ()
{
return 0;
}
I think cygwin DLL might benefit from a code I found by looking in
sync.exe by M.Russinovich, which is schematically as such:
int
sync( char drive)
{
HANDLE f;
int ret;
char file[7] = .\\X:;
file[5] = drive;
f = CreateFile( file, GENERIC_READ|GENERIC_WRITE,
FILE_SHARE_READ|FILE_SHARE_WRITE,
NULL, OPEN_EXISTING, 0, NULL);
if ((int) f 0)
return -1;
ret = FlushFileBuffers(f) ? 0 : -1;
CloseHandle(f);
return ret;
}
FlushFileBuffers() doesn't actually do much last I checked. Despite its
misleading name, it is not a
commit-to-disk-and-don't-return-until-its-done at any rate, which is
what's needed here. The only way I ever found to actually do this is to
open a handle to the underlying physical drive (and just try mapping drive
letters to physical drives!) and then there's an IOCTL_ that will do the
trick. And as long as the account has the right privileges, you can do
that, otherwise you can't.
--
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: working sync() code
[snip] SUSv3 has this to say about sync(): quote The sync() function shall cause all information in memory that updates file systems to be scheduled for writing out to all file systems. The writing, although scheduled, is not necessarily complete upon return from sync(). /quote scheduled for writing out? Isn't that done at the time any file/filesystem calls are made? Unless I'm missing something, that quote translates to, sync() does nothing. -- 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: Bogus assumption prevents d2u/u2d/conv/etal working on mixed files.
Noo... Please, remove all of these safety checks. There must be some kind of user sanity presupposition. Or else the tools soon will be crippled to a state where they are unusable for normal work. FWIW I'm with Hannu. Should rm ask you, Do you *really* want to delete this file?, or make a backup of every file you delete (ala the Recycle Bin)? It should according to the thinking in this thread. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: cygwin... from Turkey
Subject: Re: cygwin... from Turkey ...NER NERRR! Keep on rockin' in the Free world!... ;-) -- 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: ITP moratorium still in effect?
On Sat, Mar 27, 2004 at 03:05:11PM -0500, Igor Pechtchanski wrote: Is the ITP moratorium declared in http://cygwin.com/ml/cygwin-apps/2004-03/msg00036.html still in effect? Nope. Daniel's back. Sorry that I never made that clear. I'd like to explore new methods for getting packages into the distribution, however. Possibly we need a gdb packages steering committee which decides on these things. It could have rules like a package needs a simple majority vote to be a candidate for inclusion. I'd envision seven people on the committee. I have names in mind but the only two definites are really Corinna and me, both of whom would also have veto power. I'd also like to see a formal justification for why a package should be included, remembering that we have a software web page at cygwin.com which can be used to advertise packages that aren't quite up to snuff for the cygwin release. I think we have accepted a couple of packages here which really only deserve to be advertised on the web site. Keep in mind that encouraging unofficial packages in this manner will: 1. Result in more packages that aren't reviewed by anybody (e.g. Harold) and hence don't meet necessary Cygwin requirements (esp. FHS). 2. Ergo will result in messages to cygwin@ of the template: software web-page package totally screws up Cygwin. 3. Ergo will raise CGF's blood pressure to dangerous levels. 4. Ergo will result in long, unproductive cygwin@ threads trying to tell the OP what one sentence could: You're on your own with these packages. I agree the lets add everything situation is problematic, but I don't think encouraging people to use a method that has the smell of semi-support is going to do anything but make matters worse.
