Cosmic Desktop Compared to KDE

COSMIC is a newer desktop environment based on GNOME, designed to provide a modern user experience. In contrast, KDE Plasma is a well-established desktop known for its extensive customization options and a layout similar to Windows.

Performance Comparison

Speed and Responsiveness

Feature COSMIC KDE Plasma
General Speed Slower on some hardware Generally faster
Responsiveness May feel sluggish Feels instant

Users have reported that KDE Plasma often feels more responsive, particularly on older hardware, while COSMIC may lag behind in performance.

Resource Usage

Resource Type COSMIC KDE Plasma
RAM Usage 1,970 MiB 2,670 MiB
CPU Performance (Single Core) 2,713 points 2,695 points
CPU Performance (Multi Core) 11,498 points 11,450 points

KDE Plasma uses more RAM compared to COSMIC, which may impact performance on systems with limited resources.

Customization and User Experience

Customization Options

  • KDE Plasma: Highly customizable with numerous widgets and themes.
  • COSMIC: Offers a clean look but lacks some of the extensive customization features found in Plasma.

User Feedback

Many users transitioning from KDE Plasma to COSMIC have noted that they miss the customization options and speed of Plasma. Some have returned to Plasma after trying COSMIC due to these factors.

Conclusion

While COSMIC provides a modern interface, KDE Plasma remains the preferred choice for users seeking speed, responsiveness, and extensive customization.

Steps to Recover Data from a Failed LXC Container in Proxmox

Steps to Recover Data from a Failed LXC Container in Proxmox

To recover data from a failed LXC container using the command line in Proxmox, follow these steps:
Step 1: Access the Proxmox Host

Open a terminal or SSH into your Proxmox server.

Step 2: Locate the Configuration File

Navigate to the directory containing the LXC configuration files:

cd /etc/pve/nodes//lxc/

Identify the configuration file for the failed LXC container. The filename will be in the format .conf, where is the container ID.

Step 3: Identify the Disk Image

Open the configuration file using a text editor (e.g., nano, vi):

nano .conf

Look for the line starting with rootfs. This line contains the disk image path, typically formatted as local-lvm:vm–disk-0.

Step 4: Create a New LXC Container

Create a new LXC container that will be used to access the data:

pct create local:vztmpl/ubuntu-22.04-standard_22.04-1_amd64.tar.zst --hostname recovery-container --memory 512 --cores 1 --rootfs local-lvm:8 --net0 name=eth0,bridge=vmbr0,ip=dhcp --password

Step 5: Add the Disk Image as a Mount Point

Edit the configuration file of the new LXC container:

nano /etc/pve/nodes//lxc/.conf

Add the following line to mount the disk image from the failed LXC:

mp1: local-lvm:vm--disk-0,mp=/root/

Step 6: Start the New LXC Container

Start the new LXC container:

pct start

Step 7: Access the Data

Enter the new LXC container:

pct enter

Navigate to the mounted directory to access your data:

cd /root/

By following these steps, you can successfully recover data from a failed LXC container in Proxmox.

Restore LXC Backups in Proxmox

Restoring LXC Backups in Proxmox

Restoring LXC backups in Proxmox VE is a straightforward process that allows you to create a new container from an existing backup. Here’s how to do it:

Steps to Restore an LXC Backup

  1. Access Backup Storage
    Navigate to the Backup Storage in the Proxmox web interface.
  2. Select Backup Snapshot
    Find and select the backup snapshot you wish to restore.
  3. Initiate Restore
    Click on the “Restore” button. This action will open a restore window.
  4. Modify Container Name
    In the restore window, you can change the name of the container to a new one. This is essential if you want to avoid overwriting an existing container.
  5. Confirm Restore
    After making the necessary changes, confirm the restore process.

Important Considerations

  • Backup Source: Ensure that the backup is accessible from the Proxmox Backup Server (PBS) or the local storage where it was saved.
  • Disk Space: Verify that there is sufficient disk space on the destination storage for the restored container.
  • VMID Management: If you restore to the original VMID, it will overwrite the existing container. Using a new VMID creates a parallel copy, which is often preferred for testing.

Summary of Restore Options

Backup Source Restore Method Cross-Node Support Granularity
vzdump file PVE web UI → Storage → Backup content Yes Full VM only
PBS datastore PVE web UI → Storage → PBS content, or PBS UI Yes Full VM; flexible

By following these steps, you can effectively restore LXC backups in Proxmox, ensuring that your container data is recoverable and manageable.

SigDigger – A Cheap $20 SDR Dongle That Decodes Radio Signals

A Spanish ham radio operator open-sourced a full signal intelligence tool.

it’s called SigDigger. plug in a cheap $20 SDR dongle and it decodes literally any radio signal floating in the air around you. wireless mics. baby monitors. garage remotes. analog security cams. walkie-talkies. all of it.

→ demodulate FSK, PSK & ASK signals in real-time

→ decode analog video transmissions

→ listen to analog voice channels

→ analyze unknown & bursty signals live

It’s built by one guy in Spain (licensed ham, EA1IYR). the DSP core, the GUI, the widget library, all his own projects, all open source.

Linux and macOS. self-contained AppImage means zero compilation to get started. plugins for Deep Space Network amateur reception, weather satellites, and AntSDR are one flag away.

Signal intelligence work that used to require a Rohde & Schwarz analyzer. now runs on your laptop. 100% Open Source.

https://batchdrake.github.io/SigDigger/

BIOS Patching Tools Guide for Mutant CPUs & Coffee Lake on Skylake/Kaby Lake Boards

Enabling mutant CPUs (or native Coffee Lake/Comet Lake desktop CPUs) on older Z170/Z270 motherboards requires BIOS modifications. The go-to tool is CoffeeTime, an automated modding utility created by the modding community.

Important Warnings

  • Risk of bricking: Always have a backup method (CH341A programmer recommended).
  • This voids warranties and is for advanced users only.
  • Results vary by motherboard — some work flawlessly, others need extra tweaks (pin mods, ME firmware, etc.).
  • Test thoroughly for stability, especially with high-TDP i9 mutants.

Main Tool: CoffeeTime

CoffeeTime (by revlaay and contributors) is the easiest automated tool for patching BIOS files. It handles microcode updates, ME adjustments, GOP/VBIOS, and Coffee Lake compatibility patches.

Latest versions are discussed on Win-Raid forums (search for “CoffeeTime” in the Coffee Lake guide thread).

Step-by-Step Guide Using CoffeeTime

  1. Backup Your Original BIOS
    • Enter your motherboard’s BIOS and use the built-in save/export function.
    • Or dump it with a hardware programmer (CH341A + SOIC clip) for safety.
  2. Download CoffeeTime
    • Check the latest release on Win-Raid Level1Techs forum (main Coffee Lake guide thread).
    • Common recent versions: 0.99 or newer with GUI.
  3. Prepare the BIOS File
    • For some boards (e.g., ASUS), you may need to convert .CAP to .bin first.
    • Optionally downgrade ME firmware to a compatible version (e.g., 11.7.x or specific corporate builds) using tools like ME Analyzer + ME Cleaner.
  4. Run CoffeeTime
    • Launch the tool (Windows-based, may need admin rights).
    • Load your stock BIOS file.
    • Select options:
      • Inject All or full patches (recommended for most).
      • Update microcodes (important for stability and AVX performance).
      • ME region adjustments.
      • Other patches (PCIe fixes, Hyper-Threading enable if needed).
    • Click apply — the tool outputs a modded BIOS file.
  5. Flash the Modded BIOS
    • Preferred safe method: Use a CH341A programmer to flash externally (no boot required).
    • In-system: Use manufacturer tools (ASUS EZ Flash, Gigabyte Q-Flash, etc.) from within the existing BIOS, or DOS/UEFI shell.
    • Some boards support USB BIOS Flashback.
  6. Hardware Considerations for Mutants
    • Pin mods (Kapton tape isolation): Often required on Z170/Z270 for 8-core+ CPUs to fix compatibility. Search for your specific board + “Coffee Lake pin mod map”.
    • Good cooling is essential — mutants can run hot.
    • Test with a known-good Skylake CPU first if possible.
  7. Post-Install Checks
    • Boot and verify CPU recognition in BIOS/Windows.
    • Monitor temps, voltages, and stability (Prime95, etc.).
    • Update chipset drivers and test features like Resizable BAR if added.

Other Useful Tools

  • UEFI BIOS Updater (UBU) by SoniX → For manual microcode/GOP updates.
    github.com
  • ME Analyzer / FIT → For inspecting and cleaning Management Engine regions.
  • CH341A Programmer → Essential hardware for safe flashing.
  • Board-specific mods (e.g., jumper wires on some ASUS boards).

Common Motherboard Examples

  • ASUS Z170 series: Generally excellent support after patching.
  • Gigabyte/MSI/ASRock: Work well but may need extra PCIe or HT fixes.

For the most up-to-date links, detailed per-board guides, and troubleshooting, visit the massive Win-Raid Forum thread: “[Guide] CoffeeLake CPUs on Skylake/KabyLake mainboards”.

winraid.level1techs.com

 

Final Tips

Start with a lower-power mutant (like i7-8750H/9750H) before jumping to an i9-10980HK.
Document every step and keep originals.
The community is helpful — post your exact board model and BIOS version when asking for help.
This modding scene keeps old platforms alive far beyond their official support. Good luck, and build safely! If you specify your motherboard model, I can point to more tailored advice.

Mutant CPUs: Breathing New Life into Old Skylake Motherboards with High-End i9 Power

In the world of PC modding, few projects are as delightfully weird as “mutant CPUs” — laptop mobile processors repurposed with custom adapters to drop into desktop sockets. These Frankenstein creations let enthusiasts run powerful later-generation Intel CPUs, including high-core i9 models, on ancient Skylake (6th-gen) Z170 motherboards.

What Are Mutant CPUs?

These are typically high-end mobile CPUs (like the Core i9-9880HK or i9-10980HK) taken from laptops and soldered onto a small PCB adapter. The adapter has LGA 1151 pins on the bottom, making it physically compatible with desktop sockets. A metal bracket replaces the usual IHS (integrated heat spreader) for cooler mounting.

  • Why “mutant”? They’re hybrids — laptop silicon in a desktop-friendly package. Chinese modders on sites like AliExpress popularized them.
  • Common chips: 8-core/16-thread Coffee Lake or Comet Lake-H mobile CPUs (still 14nm Skylake derivatives).

The Magic: Running Them on Skylake Boards

Official Intel rules say no — Skylake (100-series) and Kaby Lake (200-series) boards don’t support 8th/9th-gen or later CPUs due to pin differences, microcode, and ME firmware. But the modding community found workarounds:

  1. BIOS Patching — Tools like Coffeetime modify the BIOS to enable Coffee Lake support. Many users flash via a CH341A programmer.
  2. ME Firmware Tweaks — Specific Management Engine versions are needed for stability.
  3. Plug & Play (Sort Of) — Once modded, these mutants often work on Z170, B360, or even some Z370 boards.

Result? You can drop an i9-10980HK (8 cores, up to 5.3 GHz turbo) into a 2015-era Z170 board and get modern multi-core performance without buying a new platform.

Performance Payoff

These mutants deliver strong results for their era:

  • Excellent single-thread speeds (true to Skylake roots).
  • Solid multi-core for productivity, content creation, or light gaming.
  • Overclocking potential on unlocked models.

They shine in budget or retro builds where you want to reuse DDR4 RAM, PCIe 3.0 slots, and old cases. Real-world tests show the i9-10980HK rivaling or beating some newer chips in single-threaded tasks — though power/thermals depend heavily on your cooler and board VRM quality.

Pros:
  • Cheap upgrade path for old boards.
  • High-core counts on legacy platforms.
  • Fun modding project.

Cons:

  • Requires BIOS flashing skills (risk of bricking).
  • Potential stability quirks or limited features.
  • No official support — cooling and power delivery vary.
  • Newer platforms (LGA 1700+) are better for longevity.
The Bottom Line
Mutant CPUs are a testament to the creativity of the hardware community. They turn “obsolete” Skylake motherboards into surprisingly capable machines with later i9 muscle.
If you have an old Z170 board gathering dust, hunting for a mutant i9 could be the cheapest way to a high-core refresh.
Just remember: Proceed with caution, back up your BIOS, and enjoy the mad science.
Happy building! Sources include modding forums like Win-Raid, TechPowerUp, and hardware sites covering these adapters.

Overview of Firecracker MicroVM

Overview of Firecracker MicroVM

Firecracker is an open-source virtualization technology developed by Amazon Web Services (AWS). It is specifically designed to create and manage lightweight virtual machines, known as microVMs, which are optimized for running serverless workloads and container-based applications.

Key Features

  • Speed: MicroVMs can boot in less than 125 milliseconds, making them ideal for short-lived tasks.
  • Memory Efficiency: Each microVM has a memory overhead of less than 5 MiB, allowing for high-density deployment on servers.
  • Security: Firecracker provides strong isolation through hardware virtualization using KVM (Kernel-based Virtual Machine), which enhances security compared to traditional VMs.

Architecture

Firecracker’s architecture is streamlined for efficiency and minimalism. Here are its main components:

Component Description
MicroVMs Lightweight virtual machines that run isolated applications or processes.
Jailer Ensures security by managing namespaces, cgroups, and seccomp filters.
VMM (Virtual Machine Monitor) Manages the lifecycle of microVMs and exposes a RESTful API for configuration.

Use Cases

Firecracker is particularly suited for:

  • Serverless Computing: Powers services like AWS Lambda and AWS Fargate.
  • Multi-Tenant Workloads: Provides strong isolation for workloads from different customers.
  • High-Performance Applications: Ideal for scenarios requiring rapid scaling and resource efficiency.

Firecracker’s design allows it to handle a high volume of microVMs, supporting the creation of up to 150 microVMs per second on a single host. This makes it a compelling choice for modern cloud infrastructure, where speed and security are paramount.

How Does Firecracker Compare with traditional Virtualisation Technologies?

Firecracker microVMs provide enhanced security and isolation similar to traditional virtual machines (VMs) but with significantly faster startup times (as low as 125 milliseconds) and lower memory overhead (less than 5 MiB per microVM). This minimalist design allows for higher density of workloads on a single host compared to traditional VMs, which typically require more resources and longer boot times.

What are the Security Features of Firecracker MicroVM’s for container based applications? (for example Docker).

Firecracker microVMs provide strong isolation mechanisms using KVM (Kernel-based Virtual Machine) for secure virtualization, ensuring that workloads from different customers can run safely on the same machine. Additionally, it has a minimal device model that reduces the attack surface area, enhancing overall security. Considered much less risky in multi-tenant situations than say a priviliged container.

Whatever Happened To Rediffusion?

Rediffusion. A company that was once everywhere. Shops in the high street, offering rental TV’s. Cable services in almost every large town or City (I remember those rotary wall switches well).

Its famous “adastral” spinning star symbol a major brand. The last I say of it was on the side of Initial vans, after BET acquired the assets of Rediffusion.

Also in the late 80’s I bought large quantities of ex-rental colour sets (Dorics?) especially after Granada bought their rental business. Very well built and modular sets, made in Rochdale if I recall. The Mk 1 (revamp) a colour hybrid chassis, the Mk 3 and Mk4.

Rediffusion ceased trading in the 1980s as new technologies like satellite TV emerged, leading to the sale of its assets and the breakup of the company. By the early 1990s, most of its operations had been sold off or absorbed by other companies

Overview of Rediffusion’s History

Rediffusion was a pioneering company in the broadcasting industry, known for distributing radio and television signals through wired relay networks. Founded in 1928, it became the first ITV franchisee to go on air in the UK in 1955. The company expanded into various sectors, including manufacturing radios and televisions, and even ventured into music with the establishment of a record label.

Decline and Cessation of Operations

Factors Leading to Decline

  • Technological Changes: The emergence of satellite TV and other new technologies in the 1980s significantly impacted Rediffusion’s business model.
  • Financial Struggles: The company faced financial difficulties, particularly after losing its ITV franchise in 1968, following the IBA imposed shotgun marriage between it and Associated British (ABC) to form Thames Television out of which ABC became the dominant partner.

Final Years

  • Asset Sales: By the early 1990s, Rediffusion’s assets were sold off, and the company was effectively broken up. Most of its operations were absorbed by other companies, marking the end of its presence in the broadcasting industry.

Current Status

Today, the Rediffusion brand has been revived in some markets, such as China for consumer electronics and in the UK for LED televisions. However, the original company and its operations have largely faded from the broadcasting landscape.

Kestra Pricing Overview

Kestra Pricing Overview

Kestra is an open-source platform, which means it is free to use. However, there are additional options available for users who may need more advanced features or support.

Free and Paid Options

Feature Free Version Paid Version
Basic Functionality Yes Yes
Enterprise Features No Yes
Managed Services No Yes
Support Community support Dedicated support with SLAs
Scalability Limited to self-hosting Enhanced for enterprise needs

Key Points

  • Open-Source: The core platform is free and can be self-hosted.
  • Enterprise Edition: Offers additional features for mission-critical workloads, including enhanced security and governance.
  • Kestra Cloud: A fully managed service that simplifies deployment and management, available for a fee.

In summary, while Kestra is free to use, organizations looking for advanced features or managed services will need to consider the paid options.

Laser Printers Cheaper To Run (Obviously)

Cost Efficiency of Laser Printers

Laser printers are generally more economical to operate over time compared to inkjet printers. This is primarily due to the longevity and efficiency of toner cartridges.

Key Factors

  • Toner Longevity: Toner cartridges for laser printers can print significantly more pages than ink cartridges used in inkjet printers. This means fewer replacements and lower costs per page.
  • Cost Per Page: The average running cost per page for laser printers is usually lower, making them a better choice for high-volume printing needs.

Comparison of Running Costs

Printer Type Initial Cost Toner/Ink Cost Pages per Cartridge Cost per Page
Laser Printer Higher Higher 2,000 – 10,000+ Lower
Inkjet Printer Lower Lower 200 – 1,000 Higher

Conclusion

For users who print frequently or in large volumes, laser printers are typically the more cost-effective option in the long run. Their ability to produce more prints per cartridge and lower cost per page makes them ideal for both home offices and businesses.

Basic wireless mono laser printers start from about £130. For colour add about £100.