book

Professional Linux® Programming

Name: Professional Linux® Programming
ISBN: 9780471776130

by Jon Masters, Richard Blum

March 2007

Intermediate to advanced

502 pages

14h 4m

English

Wrox

Read now

Unlock full access

Copyright
About the Authors
Credits
Acknowledgments
Introduction
Who This Book Is ForWhat This Book CoversHow This Book Is StructuredConventionsSource CodeErratap2p.wrox.com
1. Working with Linux
1.1. A Brief History of Linux1.1.1. The GNU Project1.1.2. The Linux Kernel1.1.3. Linux Distributions1.1.4. Free Software vs. Open Source1.2. Beginning Development1.2.1. Choosing a Linux Distribution1.2.1.1. Linux Distributions from Red Hat1.2.1.2. Linux Distributions from Novell1.2.1.3. Debian and Ubuntu GNU/Linux1.2.1.4. Classes of Linux Distribution1.2.1.4.1. RPM based Distributions1.2.1.4.2. Debian Derivatives1.2.1.4.3. Source Distributions1.2.1.4.4. Roll Your Own1.2.2. Installing a Linux Distribution1.2.2.1. Getting Hold of Linux1.2.2.2. Determining Install-Time Package Selection1.2.2.3. Setting Up Your Development Environment1.2.2.3.1. Finding a Terminal1.2.2.3.2. Editing Source Files1.2.2.3.3. Using the Root Account1.2.2.4. Development Releases1.2.2.5. Scratch Boxes and Virtualization Technologies1.2.2.5.1. VWware1.2.2.5.2. Qemu1.2.2.5.3. Xen1.3. Linux Community1.3.1. Linux User Groups1.3.2. Mailing lists1.3.3. IRC1.3.4. Private Communities1.4. Key Differences1.4.1. Linux Is Modular1.4.2. Linux Is Portable1.4.3. Linux Is Generic1.5. Summary
2. Toolchains
2.1. The Linux Development Process2.1.1. Working with Sources2.1.2. Configuring to the Local Environment2.1.3. Building the Sources2.2. Components of the GNU Toolchain2.2.1. The GNU Compiler Collection2.2.1.1. Compiling a Single Source File2.2.1.2. Compiling Multiple Source Files2.2.1.3. Using External Libraries2.2.1.3.1. Shared vs. Static2.2.1.3.2. An Example Shared Library2.2.1.4. GCC options2.2.1.4.1. General Options2.2.1.4.2. Language Options2.2.1.4.3. Warning Levels2.2.1.4.4. Debugging2.2.1.4.5. Optimization2.2.1.4.6. Hardware Options2.2.1.4.7. Further Documentation2.3. The GNU binutils2.3.1.2.3.1.1. The GNU Assembler2.3.1.2. The GNU Linker2.3.1.2.1. Operation of the Linker2.3.1.3. GNU objcopy and objdump2.4. GNU Make2.5. The GNU Debugger2.6. The Linux Kernel and the GNU Toolchain2.6.1. Inline Assembly2.6.2. Attribute Tags2.6.3. Custom Linker Scripts2.7. Cross-Compilation2.8. Building the GNU Toolchain2.9. Summary
3. Portability
3.1. The Need for Portability3.2. The Portability of Linux3.2.1. Layers of Abstraction3.2.2. Linux Distributions3.2.2.1. Packages3.2.2.2. The Linux Standard Base3.2.2.2.1. LSB as a Panacea3.2.2.3. The Role of the Linux vendor3.2.2.3.1. A Word on Quality3.2.2.4. RPM-Based Distributions3.2.2.5. Debian Derivatives3.2.2.6. Source Distributions3.2.2.7. Rolling Your Own3.2.3. Building Packages3.2.3.1. Building RPM Packages3.2.3.1.1. Writing Spec Files3.2.3.1.2. Building an Example RPM3.2.3.1.3. Patching Your Sources3.2.3.1.4. Configuring the Build Environment3.2.3.1.5. Kicking Off the Build3.2.3.1.6. Installing RPMs on Non-RPM-Based Systems3.2.3.2. Debian Packages3.2.3.2.1. Debian Dependencies3.2.3.2.2. Building Debian Packages3.2.3.2.3. Debian Developers (DDs)3.2.3.2.4. Further Information3.2.4. Portable Source Code3.2.4.1. GNU Autotools3.2.4.1.1. Building Autotools Projects3.2.4.2. GNU Autoconf3.2.4.3. GNU Automake3.2.4.4. GNU Libtool3.2.5. Internationalization3.2.5.1.3.2.5.1.1. Languages and Locales3.2.5.1.2. Working with Character Sets3.2.5.1.3. Wide Characters3.2.5.1.4. Speaking Your User's Language3.2.5.1.5. Languages Other Than C/C++3.3. Hardware Portability3.3.1. 64-Bit Cleanliness3.3.2. Endian Neutrality3.3.2.1. Endian "Holy Wars"3.3.3. Summary
4. Software Configuration Management
4.1. The Need for SCM4.2. Centralized vs. Decentralized Development4.3. Centralized Tools4.3.1. The Concurrent Version System4.3.1.1. Creating a CVS Repository4.3.1.2. Creating a New CVS project4.3.1.3. Checking Sources out of CVS4.3.1.4. Checking in Modifications4.3.1.5. Adding and Removing Files and Directories4.3.1.6. Browsing CVS History4.3.1.7. Conflict Resolution4.3.1.8. Tagging and Branching4.3.1.9. Distributed Development4.3.1.9.1. CVS over an SSH Connection4.3.1.9.2. CVS with a Remote pserver4.3.1.10. Limitations4.3.2. Subversion4.3.2.1. Creating a Subversion Repository4.3.2.2. Creating a New Subversion Project4.3.2.3. Checking Sources out of Subversion4.3.2.4. Checking in Modifications4.3.2.4.1. Changesets4.3.2.5. Distributed Development4.4. Decentralized tools4.4.1. Bazaar-NG4.4.1.1. Configuring Bazaar4.4.1.2. Creating a New Bazaar Branch4.4.1.3. Checking in Modifications4.4.1.4. Merging Bazaar Branches4.4.2. Linux kernel SCM (git)4.4.2.1. Everything Is an Object4.4.2.2. Git vs. Cogito4.4.2.3. Creating a New git Repository4.4.2.4. Cloning an Existing git Repository4.4.2.5. Managing Sources with git4.4.2.6. Git as a Debugging Aid4.5. Integrated SCM Tools4.5.1. Eclipse4.5.1.1. The CVS Repository Perspective4.5.1.1.1. Placing a Project under CVS Control4.5.1.1.2. Controlling a CVS Repository4.6. Summary
5. Network Programming
5.1. Linux Socket Programming5.1.1. Sockets5.1.2. Network Addresses5.1.3. Using Connection-Oriented Sockets5.1.3.1. The Server Functions5.1.3.2. The Client Functions5.1.3.3. Closing the Connection5.1.4. Using Connectionless Sockets5.2. Moving Data5.2.1. Datagrams vs. Streams5.2.2. Marking Message Boundaries5.2.3. Using Message Size5.2.4. Using Message Markers5.3. Using Network Programming Libraries5.3.1. The libCurl Library5.3.2. Downloading libCurl5.3.3. Installing libCurl5.3.4. Using the libCurl Library5.3.5. Connecting to Network Resources5.3.6. Storing Retrieved Data5.4. Summary

6. Databases
6.1. Persistent Data Storage6.1.1. Using a Standard File6.1.2. Using a Database6.2. The Berkeley DB Package6.2.1. Downloading and Installing6.2.2. Building Programs6.2.3. Basic Data Handling6.2.3.1. Opening and Closing a Database6.2.3.2. Adding New Data6.2.3.3. Retrieving Data6.2.3.4. Deleting Data6.2.3.5. Using Cursors6.3. The PostgreSQL Database Server6.3.1. Downloading and Installing6.3.2. Building Programs6.3.3. Creating an Application Database6.3.4. Connecting to the Server6.3.5. Executing SQL Commands6.3.5.1. Commands Returning No Data6.3.5.2. Commands Returning Data6.3.5.3. Handling Column Data6.3.6. Using Parameters6.4. Summary
7. Kernel Development
7.1.7.1.1. Starting Out7.1.1.1. Background Prerequisites7.1.1.2. Kernel Sources7.1.1.2.1. A Tour of the Kernel Source7.1.1.2.2. Kernel Versioning7.1.1.2.3. Vendor Kernels7.1.1.3. Configuring the Kernel7.1.1.3.1. Vendor Kernel Configurations7.1.1.3.2. Configuring for Cross-Compilation7.1.1.4. Building the Kernel7.1.1.5. The Built Kernel7.1.1.6. Testing the Kernel7.1.1.6.1. Initial Ramdisks: initrds7.1.1.7. Packaging and Installing Kernels7.2. Kernel Concepts7.2.1. A Word of Warning7.2.2. The Task Abstraction7.2.2.1. The Scheduler7.2.2.2. System Calls7.2.2.3. Execution Contexts7.2.2.3.1. Process vs. Interrupt Context7.2.2.4. Kernel Threads7.2.3. Virtual Memory7.2.3.1. The Page Abstraction7.2.3.2. Memory Mappings7.2.3.2.1. Kernel Memory Mapping7.2.3.3. Task Address Spaces7.2.4. Don't Panic!7.3. Kernel Hacking7.3.1. Loadable Modules7.3.1.1. An Example Module7.4. Kernel Development Process7.4.1. Git: the "Stupid Content Tracker"7.4.1.1. gitk: the Graphical Git Tree Browser7.4.2. The Linux Kernel Mailing List7.4.2.1. Submitting Linux Kernel Patches7.4.2.2. The Kernel Newbies Mailing List7.4.2.2.1. Kernel Janitors7.4.3. The "mm" Development Tree7.4.4. The Stable Kernel Team7.4.5. LWN: Linux Weekly News7.5. Summary
8. Kernel Interfaces
8.1. What Is an Interface?8.1.1. Undefined Interfaces8.2. External Kernel Interfaces8.2.1. System Calls8.2.1.1. Tracing System Calls8.2.1.1.1. Transferring Control to the Kernel: sys_open8.2.1.2. The System Call Table8.2.1.3. Implementing Your Own Syscalls8.2.1.4. The vsyscall Optimization8.2.2. The Device File Abstraction8.2.2.1. Character Files8.2.2.1.1. Creating a Character Device8.2.2.1.2. Building the Driver8.2.2.1.3. A Note on Dynamic Devices8.2.2.1.4. Driver Initialization8.2.2.1.5. Driver Uninitialization8.2.2.1.6. Driver payload8.2.2.2. Block Devices8.2.2.3. Everything Is a File?8.2.2.4. Mechanism vs. Policy8.2.2.5. Procfs8.2.2.5.1. Creating procfs Entries8.2.2.5.2. Building the Driver8.2.2.6. Sysfs8.2.3. Kernel Events8.2.4. Ignoring Kernel Protections8.3. Internal Kernel Interfaces8.3.1. The Kernel API8.3.2. The kernel ABI8.3.2.1. Kernel Module Packages8.4. Summary
9. Linux Kernel Modules
9.1. How Modules Work9.1.1. Extending the Kernel Namespace9.1.2. No Guaranteed Module Compatibility9.2. Finding Good Documentation9.2.1. Linux Kernel Man Pages9.3. Writing Linux Kernel Modules9.3.1. Before You Begin9.3.2. Essential Module Requirements9.3.2.1. module.h9.3.2.2. init.h9.3.3. Logging9.3.4. Exported Symbols9.3.4.1. EXPORT_SYMBOL9.3.4.2. EXPORT_SYMBOL_GPL9.3.4.3. Don't Fight the System9.3.5. Allocating Memory9.3.5.1. kmalloc9.3.5.1.1. GTP_ATOMIC9.3.5.1.2. GFP_KERNEL9.3.5.1.3. GFP_USER9.3.5.2. vmalloc9.3.5.3. plp_kmem: a Kernel Memory Buffer9.3.5.3.1. Build and Test the Example9.3.5.3.2. A Note on udev9.3.6. Locking considerations9.3.6.1. Semaphores9.3.6.2. Spinlocks9.3.6.3. plp_klock: Adding User Tracking to plp_kmem9.3.6.4. Locking Considerations for plp_klock9.3.7. Deferring work9.3.7.1. Work Queues9.3.7.2. Kernel Threads9.3.7.2.1. kthread_create9.3.7.3. Kernel Thread Example9.3.8. Further Reading9.4. Distributing Linux Kernel Modules9.4.1. Going Upstream9.4.2. Shipping Sources9.4.3. Shipping Prebuilt Modules9.5. Summary
10. Debugging
10.1. Debugging Overview10.1.1. A Word about Memory Management10.2. Essential Debugging Tools10.2.1. The GNU Debugger10.2.1.1. Compiling Code for Use with GDB10.2.1.2. Starting GDB10.2.1.2.1. Setting Breakpoints10.2.1.3. Visualizing Data10.2.1.4. Backtrace10.2.1.5. A Buggy Example10.2.1.6. Debugging a Core File10.2.2. Valgrind10.2.2.1. Automated Code Analysis10.3. Graphical Debugging Tools10.3.1. DDD10.3.2. Eclipse10.4. Kernel Debugging10.4.1. Don't Panic!10.4.2. Making Sense of an oops10.4.2.1.10.4.2.1.1. Don't Trust Subsequent oopses10.4.2.2. Reporting Bugs to Upstream10.4.3. Using UML for Debugging10.4.3.1. Building a UML Kernel10.4.4. An Anecdotal Word10.4.5. A Note about In-Kernel Debuggers10.5. Summary
11. The GNOME Developer Platform
11.1. GNOME Libraries11.1.1. Glib11.1.2. GObject11.1.3. Cairo11.1.4. GDK11.1.5. Pango11.1.6. GTK+11.1.7. libglade11.1.8. GConf11.1.9. GStreamer11.2. Building a Music Player11.2.1. Requirements11.2.2. Getting Started: The Main Window11.2.2.1. Compilation11.2.3. Building the GUI11.2.3.1. The Top-Level Container11.2.3.2. Text Labels11.2.3.3. The Slider Control11.2.3.4. The Control Buttons11.2.3.5. Menus11.2.3.6. Keyboard Shortcuts11.2.3.7. Callbacks11.2.3.8. Introducing GStreamer11.2.3.9. Opening Files11.2.3.10. Metadata11.2.3.11. Seeking11.2.4. Summary
12. The FreeDesktop Project
12.1. D-BUS: The Desktop Bus12.1.1. What Is D-Bus?12.1.2. Under D-Hood of D-Bus12.1.3. D-Bus Methods12.2. Hardware Abstraction Layer12.2.1. Making Hardware Just Work12.2.2. Hal Device Objects12.3. The Network Manager12.4. Other Freedesktop Projects12.5. Summary
13. Graphics and Audio
13.1. Linux and Graphics13.1.1. X Windows13.1.2. Open Graphics Library13.1.3. OpenGL Utilities Toolkit13.1.4. Simple Directmedia Layer13.2. Writing OpenGL Applications13.2.1. Downloading and Installing13.2.2. Programming Environment13.2.3. Using the GLUT Library13.2.3.1. Creating a Window13.2.3.2. Drawing Objects13.2.3.3. Processing User Input13.2.3.4. Animation13.3. Writing SDL Applications13.3.1. Downloading and Installing13.3.2. Programming Environment13.3.3. Using the SDL Library13.3.3.1. Displaying an Image13.3.3.2. Playing an Audio File13.3.3.3. Accessing the CD-ROM13.4. Summary
14. LAMP
14.1. What Is LAMP?14.1.1. Apache14.1.2. MySQL14.1.3. PHP14.1.4. The Rebel Platform14.1.5. Evaluating the LAMP Platform14.1.5.1. Cost and Licensing14.1.5.2. Certification14.1.5.3. Support and Services14.1.5.4. Vendor/Developer Community Relationship14.1.5.5. Integration with and Support for Other Technologies14.2. Apache14.2.1. Virtual Hosting14.2.2. Installation and Configuration of PHP 514.2.2.1. PHP Configuration14.2.2.2. Installation of PHP Modules14.2.3. Apache Basic Authentication14.2.4. Apache and SSL14.2.5. Integrating SSL with HTTP Authentication14.3. MySQL14.3.1. Installing MySQL14.3.2. Configuring and Starting the Database14.3.3. Changing the Default Password14.3.4. The MySQL Client Interface14.3.5. Relational Databases14.3.6. SQL14.3.6.1. Creating Tables14.3.6.2. Inserting a Record14.3.6.3. Searching for Records14.3.6.3.1. The SELECT Clause14.3.6.3.2. The WHERE Clause14.3.6.4. Editing a Record14.3.6.5. Deleting Records14.3.7. The Relational Model14.3.7.1. Relations, Tuples, and Attributes14.3.7.2. Keys and Relationships14.3.7.3. Relational Operators14.3.7.4. Data Integrity14.3.7.5. Data Modeling and Normalization14.4. PHP14.4.1. The PHP Language14.4.1.1. Language Basics14.4.1.2. Requiring/Including Files14.4.1.3. Magic Type Casting14.4.1.4. Arrays/Lists/Dictionaries14.4.1.5. Functions14.4.1.6. Scope14.4.1.7. Loops and Iterators14.4.1.8. Objects14.4.1.9. Pass by Reference/Pass by Value?14.4.2. Error Handling14.4.3. Error-Handling Exceptions14.4.4. Optimization Techniques14.4.4.1. Strings14.4.4.2. Arrays14.4.4.3. xdebug: Profiling and/or Debugging PHP Code14.4.5. Installing Additional PHP Software14.4.6. Logging14.4.7. Parameter Handling14.4.7.1. Register Globals14.4.8. Session Handling14.4.9. Unit Testing14.4.10. Databases and PHP14.4.11. PHP Frameworks14.5. The DVD Library14.5.1. Version 1: The Developer's Nightmare14.5.2. Version 2: Basic Application with DB-Specific Data Layer14.5.3. Version 3: Rewriting the Data Layer, Adding Logging and Exceptions14.5.3.1. Adding Database Abstraction14.5.3.2. Exceptions14.5.3.3. Logging14.5.4. Version 4: Applying a Templating Framework14.6. Summary

Content preview from Professional Linux® Programming

Chapter 6. Databases

As a Linux application runs, all of the data used in the program resides in system memory. Once the application stops running, the data contained in the memory area is lost. The next time you start the application, none of the data from the previous session is accessible. Most data-handling applications require that data be available between different sessions of the application (called data persistence). Persistent storage of information is crucial to any application that must handle historical data, such as employee records, inventory information, or class grades.

This chapter describes two methods used for implementing data persistence in Linux programs. First, a method that utilizes a built-in database engine is demonstrated. Incorporating a built-in database engine in your application provides simple persistent data features without the overhead and administration of a separate database server. Next, a method that utilizes a full-featured open source database server is demonstrated. By using a database server, customers can access your data from anywhere on the network, or even the Internet.

Persistent Data Storage

The key to persistent data storage is being able to quickly retrieve stored data. Modern database theory utilizes many techniques and methods to provide for quick retrieval of data. There are many schools of thought on exactly how databases should be designed, configured, and operated. Fortunately, Linux provides products that cover a wide range ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

PHP Advanced for the World Wide Web: Visual QuickPro Guide

Publisher Resources

ISBN: 9780471776130Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

Professional Linux® Programming

by Jon Masters, Richard Blum

Chapter 6. Databases

Persistent Data Storage

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.