ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
My program needs to handle very large binary files (bigger than 4GB), and I can't find a way to open those files for reading / writing on my old 32bit laptop.
when trying to use FILE* h=fopen64(filename, "rb"), i get only 4 bytes pointer.
it there some sort of FILE64*, or a way to overcome this issues on 32 bits machines?
I'm fighting a fire with pressure at 4 gals / second. I've changed my pressure gauge to 8 gals / second. Why didn't I get a new hose?
analogy aside, the file pointer is just a descriptor that carries stream information. The thing that overcomes the 32-bit limitation is buried deep within the read/seek/write api that is used with that file descriptor (I think there are separate fread64 and fwrite64 functions that exist, but I could be wrong here).