| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 26 Mar 2009 20:35:15 +0100 From: Leon Woestenberg <leon.woestenberg@...il.com> To: Adam Turk <bofh1234@...mail.com> Cc: linux-kernel@...r.kernel.org Subject: Re: recommended programming practices for writing (was Linux 2.6.29) Hello Adam, On Thu, Mar 26, 2009 at 8:03 PM, Adam Turk <bofh1234@...mail.com> wrote: > > I have been reading the Linux 2.6.29 thread with interest. I have written several (10 or so) C programs that write large amounts of data (between 1 and 2 GB file sizes are common). A snippet of code looks like this: > > I learned C about 15 years ago and there was no mention of a fsync. My C book doesn't mention fsync either. Granted I have written only 25-30 applications in the last 15 years or so so I am not an expert C programmer. > Your question is really off-topic for the Linux Kernel mailing list, but let me point you somewhere else: There is (1) the C library and (2) the functions provided by your operating system. Linux follows to some extend the POSIX functions for (2). A good read is the book "Linux Systems Programming" if you want to go beyond what the C library offers, for starters. Regards, -- Leon -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists