Introduction

- Objectives
- Who You Are
- The Linux Foundation
- Copyright and No Confidential Information
- Linux Foundation Training
- Certification Programs and Digital Badging
- Linux Distributions
- Platforms
- Preparing Your System
- Using and Downloading a Virtual Machine
- Things Change in Linux and Open Source Projects

Preliminaries

- Procedures
- Standards and the LSB

How to Work in OSS Projects **

- Overview on How to Contribute Properly
- Know Where the Code is Coming From: DCO and CLA
- Stay Close to Mainline for Security and Quality
- Study and Understand the Project DNA
- Figure Out What Itch You Want to Scratch
- Identify Maintainers and Their Work Flows and Methods
- Get Early Input and Work in the Open
- Contribute Incremental Bits, Not Large Code Dumps
- Leave Your Ego at the Door: Don’t Be Thin-Skinned
- Be Patient, Develop Long Term Relationships, Be Helpful

Compilers

- GCC
- Other Compilers
- Major gcc Options
- Preprocessor
- Integrated Development Environments (IDE)
- Labs

Libraries

- Static Libraries
- Shared Libraries
- Linking To Libraries
- Dynamic Linking Loader
- Labs

Make

- Using make and Makefiles
- Building large projects
- More complicated rules
- Built-in rules
- Labs

Source Control

- Source Control
- RCS and CVS
- Subversion
- git
- Labs

Debugging and Core Dumps

- gdb
- What are Core Dump Files?
- Producing Core Dumps
- Examining Core Dumps
- Labs

Debugging Tools

- Getting the Time
- Profiling and Performance
- valgrind
- Address Sanitizer
- Labs

System Calls

- System Calls vs. Library Functions
- How System Calls are Made
- Return Values and Error Numbers
- Labs

Memory Management and Allocation

- Memory Management
- Dynamical Allocation
- Tuning malloc()
- Locking Pages
- Labs

Files and Filesystems in Linux **

- Files, Directories and Devices
- The Virtual File System
- The ext2/ext3 Filesystem
- Journaling Filesystems
- The ext4/ Filesystem
- Labs

File I/O

- UNIX File I/O
- Opening and Closing
- Reading, Writing and Seeking
- Positional and Vector I/O
- Standard I/O Library
- Large File Support (LFS)
- Labs

Advanced File Operations

- Stat Functions
- Directory Functions
- inotify
- Memory Mapping
- flock() and fcntl()
- Making Temporary Files
- Other System Calls
- Labs

Processes - I

- What is a Process?
- Process Limits
- Process Groups
- The proc Filesystem
- Inter-Process Communication Methods
- Labs

Processes - II

- Using system() to Create a Process
- Using fork() to Create a Process
- Using exec() to Create a Process
- Using clone()
- Exiting
- Constructors and Destructors
- Waiting
- Daemon Processes
- Labs

Pipes and Fifos

- Pipes and Inter-Process Communication
- popen() and pclose()
- pipe()
- Named Pipes (FIFOs)
- splice(), vmsplice() and tee()
- Labs

Asynchronous I/O**

- What is Asynchronous I/O?
- The POSIX Asynchronous I/O API
- Linux Implementation
- Labs

Signals - I

- What are Signals?
- Signals Available
- Dispatching Signals
- Alarms, Pausing and Sleeping
- Setting up a Signal Handler
- Signal Sets
- sigaction()
- Labs

Signals - II

- Reentrancy and Signal Handlers
- Jumping and Non-Local Returns
- siginfo and sigqueue()
- Real Time Signals
- Labs

POSIX Threads - I

- Multi-threading under Linux
- Basic Program Structure
- Creating and Destroying Threads
- Signals and Threads
- Forking vs. Threading
- Labs

POSIX Threads - II

- Deadlocks and Race Conditions
- Mutex Operations
- Semaphores
- Futexes
- Conditional Operations
- Labs

Networking and Sockets

- Networking Layers
- What are Sockets?
- Stream Sockets
- Datagram Sockets
- Raw Sockets
- Byte Ordering
- Labs

Sockets - Addresses and Hosts

- Socket Address Structures
- Converting IP Addresses
- Host Information
- Labs

Sockets - Ports and Protocols

- Service Port Information
- Protocol Information
- Labs

Sockets - Clients

- Basic Client Sequence
- socket()
- connect()
- close() and shutdown()
- UNIX Client
- Internet Client
- Labs

Sockets - Servers

- Basic Server Sequence
- bind()
- listen()
- accept()
- UNIX Server
- Internet Server
- Labs

Sockets - Input/Output Operations

- write(), read()
- send(), recv()
- sendto(), recvfrom()
- sendmsg(), recvmsg()
- sendfile()
- socketpair()
- Labs

Sockets - Options

- Getting and Setting Socket Options
- fcntl()
- ioctl()
- getsockopt() and setsockopt()
- Labs

Netlink Sockets**

- What are netlink Sockets?
- Opening a netlink Socket
- netlink Messages
- Labs

Sockets - Multiplexing and Concurrent Servers

- Multiplexed and Asynchronous Socket I/O
- select()
- poll()
- pselect() and ppoll()
- epoll
- Signal Driven and Asynchronous I/O
- Concurrent Servers
- Labs

Inter Process Communication

- Methods of IPC
- POSIX IPC
- System V IPC**
- Labs

Shared Memory

- What is Shared Memory?
- POSIX Shared Memory
- System V Shared Memory**
- Labs

Semaphores

- What is a Semaphore?
- POSIX Semaphores
- System V Semaphores**
- Labs

Message Queues

- What are Message Queues?
- POSIX Message Queues
- System V Message Queues**
- Labs

Closing and Evaluation Survey

- Evaluation Survey

Aug 2024

The material is thorough, and the resources are detailed and plenty.

The labs are pretty helpful. To have the code, and be able to read it later is the best part.

Really happy about the content.

Feb 2024

Instructor Frank Edwards was top knotch! His tangents away from, and insights into the source material where very interesting, and helped keep the content engaging.

The instructor was exceptionally knowledgeable about each topic covered in the course, providing a more practical, "real-world" insight into how the topics connect, rather than just simply linearly going through them.

The system call section onwards was incredibly useful, I would say that's where 70-80% of the value was for our team.

Nov 2023

Very good course, I really liked it. I look forward to taking LFD420 in a few years time, once I have more experience.

The instructor, Frank Edwards, was clearly very knowledgeable, and could give practical tips on how something might be useful to a developer, or why something works a certain way. He was also able to answer questions in depth, and communicated clearly.

Developing Applications for Linux (LFD401)

Stay Up to Date