Proxmox VE 9 represents a major evolution for open-source virtualization, built on top of the Debian 13 “Trixie” base and featuring an updated Linux kernel for modern hardware integration. Core Highlights of Proxmox VE 9 For step-by-step installation instructions, check out How to Install Proxmox, which walks through setting up the hypervisor platform from start…
The previous chapter explained what the DNS does. This chapter covers the two files that decide where the resolver looks and in what order: /etc/hosts and /etc/resolv.conf. The two are the local configuration of the name resolution, and they are the first place to look when a name does not resolve. The /etc/hosts is the…
Every time a browser opens a website, a mail client sends a message, or a command reaches a server by name, the system translates a human-friendly name — example.com, mail.google.com, api.github.com — into an IP address. That translation is the Domain Name System, the DNS. It is the phone book of the internet, and it…
An IP address can be assigned in two ways. It can be statically configured — written into the device’s configuration and kept until an administrator changes it. Or it can be dynamically assigned — requested from a DHCP server and leased for a period of time, with the server deciding which address the device gets….
A network interface is the device’s connection to a network. It can be a physical card, a wireless adapter, a virtual interface, a bridge, a tunnel, or a loopback. Each has an address, a state, a set of statistics, and a set of properties. The tools for viewing them are the ip addr and the…
A device on a network can reach the other devices on the same subnet directly, but it cannot reach the devices on the other subnets without help. That help is the gateway — the router that connects the local network to the outside. Every packet whose destination is not on the local subnet is sent…
In Angular 54, the injector hierarchy was covered: the EnvironmentInjector, the ElementInjector, and the resolution order that walks the tree. This chapter goes deeper into the two pieces that make the hierarchy work: the providers that tell the injector what to create, and the injection tokens that identify what to create. A provider is a…
Angular’s dependency injection is the framework’s backbone. Every service, every component, every directive, and every pipe lives in an injector hierarchy, and the tokens, the providers, and the resolution rules determine what is created, when, and where. The basic usage — @Injectable({ providedIn: ‘root’ }), the constructor injection, the inject() function — is familiar. The…
The Resource API is Angular’s answer to asynchronous data in a signal-based world. Before it, the standard pattern for fetching data was a combination of toObservable, switchMap, and toSignal — a pipeline that worked but required the developer to manage loading states, errors, cancellation, and reloads manually. The resource() function wraps an async operation and…
The basic signal API — signal, computed, effect — covers the common cases. The advanced patterns cover the cases where the state is more complex: state that derives from an input and resets when the input changes, state that is written asynchronously, state that depends on a resource, state that is stored in a service…