Evelyn Herzog foxyfocus

Everything in C is a pointer!

That’s right. I’m making this statement. This little write-up is an attempt at explaining how any why everything in the c programming language is actually just a pointer. This is simply an attempt at explaining how memory in the computer is arranged in a narrowed view and my real goal is to consider the most simple examples possible.

I will be focusing on x86 specifically.

Types in c (bits and bytes) - and pointers

I would feel pretty confident that you, by now, understand that the types in c are simply identifiers in how much space is used to represent a number. I have no interest in explaining the difference between signed vs unsigned integers. Nor am I going to explain how floating point numbers are represented. If you are interested in those things take a look at these two links. C data types and [[https://en.wikipedia.org/wiki/Floating-point_ari

Project Name

Write a project description

Prerequisites

This project requires NodeJS (version 8 or later) and NPM.

Arch Linux Installation

LVM on LUKS Arch installation with systemd-boot

Sources:

Note: If you want a simpler encryption setup (with LUKS only), you can instead use the archinstall "guided" installer included with Arch since April 2021.

Understanding the Memory Layout of Linux Executables

Required tools for playing around with memory:

hexdump
objdump
readelf
xxd
gcore

	#!/bin/bash

	# This is a script that will install a minimal GNOME on a minimal Fedora Everything install
	# This script was made for Fedora 38
	# 1. Get the Fedora Everything ISO: https://alt.fedoraproject.org/
	# 2. When installing select "Minimal install" where you select software.

	# Install curl to download and run this script trough that, or just copy paste the lines

	# Let's make dnf a little bit faster first

	use std::io;
	use std::str;
	use std::error::Error;
	use std::io::{Read, Write};
	use std::net::TcpStream;

	#[allow(unused_variables)]
	pub trait Events {
	fn on_connect(&self, host: &str, port: i32) {}
	fn on_error(&self, err: &str) {}