/mnt/SysLinuxOS_backup/

├── .backup_meta          ← metadata file (date, distro, size)
└── .rootfs_cache/        ← btrfs subvolume (the live rsync target)
    └── .snapshots/       ← btrfs subvolume managed by snapper
        ├── 1/
        │   ├── info.xml
        │   └── snapshot/ ← read-only btrfs snapshot of .rootfs_cache
        ├── 2/
        │   ├── info.xml
        │   └── snapshot/
        └── ...

META_DATE="2026-06-17 14:30"
META_DISTRO="SysLinuxOS"
META_SIZE="8.2G"

2026-06-17 14:30 | SysLinuxOS | 8.2G

[ ] Build from DCB cache (2026-06-17 14:30 | SysLinuxOS | 8.2G)

if [ "$SOURCE_MODE" != "cache" ] && [ "$SOURCE" != "/" ]; then
    # live validation only runs in live mode
fi

--exclude=/.snapshots
--exclude=/.snapshots/*
--exclude=/@.rollback-bak-*

btrfs root (top-level, subvolid=5)
├── @               ← mounted at /
├── @home           ← mounted at /home
└── .snapshots      ← snapper snapshots of @ /mnt/SysLinuxOS_backup/ (separate btrfs volume or subvolume)
└── .rootfs_cache/  ← subvolume, rsync target
    └── .snapshots/ ← subvolume, snapper config "distroclone-backup"
        ├── 1/snapshot   (read-only)
        ├── 2/snapshot   (read-only)
        └── ...

# 1. Delete each read-only snapshot leaf
sudo btrfs subvolume delete /mnt/SysLinuxOS_backup/.rootfs_cache/.snapshots/1/snapshot
sudo btrfs subvolume delete /mnt/SysLinuxOS_backup/.rootfs_cache/.snapshots/2/snapshot
# ... repeat for each numbered snapshot

# 2. Delete the .snapshots subvolume itself
sudo btrfs subvolume delete /mnt/SysLinuxOS_backup/.rootfs_cache/.snapshots

# 3. Delete the .rootfs_cache subvolume
sudo btrfs subvolume delete /mnt/SysLinuxOS_backup/.rootfs_cache

# 4. Now rm -rf works on the remainder
sudo rm -rf /mnt/SysLinuxOS_backup/

curl -fsSL https://fconidi.github.io/SysLinuxOS-Tools/client/install-repo.sh | sudo bash
sudo apt install distroclone distroclone-backup snapper btrfs-progs

wget https://github.com/fconidi/distroClone/releases/latest/download/distroClone_1.4.10_all.deb
wget https://github.com/fconidi/distroClone-backup/releases/latest/download/distroclone-backup_1.3.4_all.deb
sudo apt install ./distroClone_1.4.10_all.deb ./distroclone-backup_1.3.4_all.deb

share

L'articolo Build a Live ISO from DistroClone Backup Cache proviene da SysLinuxOS.

I am excited to announce that the official SysLinuxOS AP  is now live and publicly accessible. All SysLinuxOS tools and packages are now installable and upgradable directly via apt, with GPG signature verification and automatic updates.

What it is

The SysLinuxOS-Tools repository is a GPG-signed APT repository hosted on GitHub Pages and managed with reprepro. It distributes the packages developed for SysLinuxOS: tools that extend Debian with snapshot management, live ISO creation, system monitoring and more.

Repository URL: https://fconidi.github.io/SysLinuxOS-Tools

Source code and metadata on GitHub: https://github.com/fconidi/SysLinuxOS-Tools

Available packages (repo constantly updated)

• distroclone — builds a bootable live ISO directly from your running Debian system
• distroclone-backup — automatic Btrfs snapshot integration for distroClone
• grub-btrfs — Btrfs snapshots in the GRUB menu (SysLinuxOS build)
• syslinuxos-ring-conky — ring-style Conky theme with auto-scaling
• syslinuxos-snapshots — Btrfs snapshot management with GRUB integration
• conky-window — minimal Conky window theme for SysLinuxOS

Tip

After installing SysLinuxOS 13.2, I recommend reinstalling the packages, to update configuration files, and align all packages with apt.

Installation

A single command sets up the repository, imports the GPG key and configures the APT source:

curl -fsSL https://fconidi.github.io/SysLinuxOS-Tools/client/install-repo.sh | sudo bash

After that, install any package as usual:

sudo apt install syslinuxos-snapshots
sudo apt install syslinuxos-ring-conky
sudo apt install distroclone

Updates will be delivered automatically via apt upgrade, like any standard Debian package.

Manual setup

If you prefer to configure the repository by hand:

# Import the signing key
curl -fsSL https://fconidi.github.io/SysLinuxOS-Tools/syslinuxos-archive-keyring.asc \
  | sudo gpg --dearmor -o /usr/share/keyrings/syslinuxos-archive-keyring.gpg

# Add the APT source (deb822 format)
sudo tee /etc/apt/sources.list.d/syslinuxos-tools.sources >/dev/null <<'EOF'
Types: deb
URIs: https://fconidi.github.io/SysLinuxOS-Tools
Suites: tirreno
Components: main
Architectures: amd64
Signed-By: /usr/share/keyrings/syslinuxos-archive-keyring.gpg
EOF

sudo apt update

Technical details

• Hosting: GitHub Pages (branch main)
• Signing: GPG RSA-4096, key ID 5FADCAF45BC3FA1D
• Suite: tirreno — Component: main — Architecture: amd64
• Package management: reprepro — one version per package, index rebuilt and re-signed on each update

The grub-btrfs package is a customized build for SysLinuxOS. To ensure it always takes precedence over any Debian-provided version, the install script configures an APT pin at priority 1001 in /etc/apt/preferences.d/99-syslinuxos-tools.pref. No other packages are pinned.

Why a dedicated repository

Managing SysLinuxOS packages individually — downloading .deb files, tracking versions, running dpkg -i manually — is error-prone and does not scale. A proper APT repository means:

• Packages are installed and upgraded with standard apt commands
• GPG signature verification on every apt update
• Correct dependency resolution handled by APT
• No manual intervention needed when new versions are released

The repository is already used in the SysLinuxOS ISO build process and on all active SysLinuxOS installations.

Franco Conidi aka edmond — francoconidi.it — syslinuxos.com

share

L'articolo SysLinuxOS Official APT Repository Now Live proviene da SysLinuxOS.

SysLinuxOS – Snapshot Management Guide

1. Introduction

SysLinuxOS 13.2 uses btrfs as its default filesystem and integrates snapper, grub-btrfs, and the syslinuxos-rollback helper to provide automatic, GRUB-bootable filesystem snapshots.

Every time the system is updated or a snapshot is created manually, a copy of the root filesystem is stored in /.snapshots. These snapshots appear as boot entries in the GRUB menu, making it possible to boot into a previous state without losing data or needing a live ISO.

This guide covers the commands you will use day-to-day to inspect, create, delete, and restore snapshots on SysLinuxOS.

2. Requirements

The following packages must be installed and active (default in SysLinuxOS):

• syslinuxos-snapshots — provides syslinuxos-rollback, the grub.d helpers, and the setup script
• snapper >= 0.10
• grub-btrfs >= 4.14
• btrfs-progs

To verify the setup is complete:

sudo snapper -c root list
systemctl status snapper-timeline.timer snapper-cleanup.timer grub-btrfsd.service

If /.snapshots is missing or the snapper config does not exist, re-run the setup:

sudo /usr/sbin/syslinuxos-snapshots-setup

3. Viewing Snapshots

List all existing snapshots:

sudo snapper -c root list

The output shows the snapshot number, type (single, pre, post), date, description, and whether the snapshot is read-only. Row 0 is always the current live state and is not a real snapshot.

To show detailed information about a specific snapshot:

sudo snapper -c root info N

Replace N with the snapshot number.

4. Creating a Snapshot

Create a manual single snapshot with a description:

sudo snapper -c root create --description "before kernel upgrade" --type single

Create a pre/post pair around an operation (for example a package install):

sudo snapper -c root create --type pre --description "pre apt upgrade"
sudo apt upgrade
sudo snapper -c root create --type post --description "post apt upgrade"

5. Deleting Snapshots

Delete a single snapshot by number:

sudo snapper -c root delete N

Delete a range of snapshots:

sudo snapper -c root delete N-M

Snapper also runs automatic cleanup via the snapper-cleanup.timer service. The active limits are:

• Maximum regular snapshots kept: 5
• Maximum important snapshots kept: 5
• Daily timeline snapshots kept: 7
• GRUB snapshot entries shown: 8

These values are set by syslinuxos-snapshots-setup and can be overridden manually:

sudo snapper -c root set-config "NUMBER_LIMIT=10"
sudo snapper -c root set-config "TIMELINE_LIMIT_DAILY=14"

6. Automatic Snapshots (Timeline)

The timeline creates one snapshot per hour and keeps the most recent daily snapshots according to the configured limits. This is handled by two systemd timers:

systemctl status snapper-timeline.timer
systemctl status snapper-cleanup.timer

To check the timeline configuration:

sudo snapper -c root get-config

Timeline creation is enabled by default (TIMELINE_CREATE="yes"). To disable it:

sudo snapper -c root set-config "TIMELINE_CREATE=no"

7. Booting from a Snapshot (GRUB)

At boot, the GRUB menu includes a submenu named SysLinuxOS — snapshots. Select a snapshot entry to boot the system in the state it was at the time the snapshot was taken.

The system boots from a read-only copy of the snapshot. From this temporary state you can verify the system works and then decide whether to proceed with the rollback.

The submenu is generated by grub-btrfsd, which monitors /.snapshots and updates /boot/grub/grub-btrfs.cfg automatically when snapshots are created or deleted. To regenerate it manually:

sudo update-grub

8. Rolling Back to a Snapshot

Rolling back replaces the current root subvolume (@) with a read-write copy of the chosen snapshot. The previous @ is preserved as @.rollback-bak-<timestamp> on the btrfs top-level volume for recovery purposes.

8.1 Method 1 — From a Booted Snapshot (Recommended)

Boot into the snapshot you want to restore via the GRUB snapshot submenu, then run:

sudo syslinuxos-rollback

The tool auto-detects the snapshot number from the current subvolume path.

8.2 Method 2 — From the Running System or a Live ISO

Pass the snapshot number explicitly:

sudo syslinuxos-rollback N

In both cases the tool asks for confirmation before making any changes, then prints the steps it will execute:

1. Rename @ to @.rollback-bak-<timestamp>
2. Create a new read-write @ from snapshot N
3. Recreate @/.snapshots as an empty btrfs subvolume (snapper resumes normally)

After the tool completes, reboot:

sudo reboot

After verifying the rolled-back system works correctly, you can delete the backup subvolume (see the next section).

9. Cleaning Up Rollback Backups

Each rollback leaves a @.rollback-bak-<timestamp> subvolume on the btrfs top-level volume. These are kept intentionally as a safety net and do not appear in the GRUB snapshot menu.

To list and remove them:

sudo mkdir -p /mnt/tmp
sudo mount -o subvolid=5 /dev/sdXN /mnt/tmp
ls /mnt/tmp | grep rollback-bak
sudo btrfs subvolume delete -R -c /mnt/tmp/@.rollback-bak-<timestamp>
sudo umount /mnt/tmp

Replace /dev/sdXN with your btrfs partition (visible with lsblk).

10. Accessing Snapshots from Another SysLinuxOS Install

If multiple SysLinuxOS installs are present on different partitions, the GRUB menu includes two additional sections generated by the syslinuxos-snapshots package:

• Other Linux installs on btrfs: top-level entry for each secondary install plus an Advanced options submenu with all available kernels and recovery entries. This replaces the missing os-prober detection for btrfs @ layouts (Debian bugs 921004, 940710).
• SysLinuxOS — Snapshots of other installs: a submenu that chainloads the grub-btrfs.cfg of each secondary install. Selecting an entry boots that install’s specific snapshot.

Both sections are generated by /etc/grub.d/13_syslinuxos-btrfs-otheros and /etc/grub.d/14_syslinuxos-snapshots-otheros. They can be disabled individually in /etc/default/grub:

GRUB_DISABLE_BTRFS_OTHEROS=true
GRUB_DISABLE_BTRFS_SNAPSHOTS_OTHEROS=true

After changing these variables, regenerate the GRUB configuration:

sudo update-grub

11. Re-running Setup

The setup script is idempotent and safe to re-run at any time. It will skip steps that are already complete and only apply what is missing:

sudo /usr/sbin/syslinuxos-snapshots-setup

Use this after a manual change to the snapper configuration, after a failed snapper-boot.service, or when setting up a system that was installed without the syslinuxos-snapshots package.

share

L'articolo SysLinuxOS Snapshot Management Guide proviene da SysLinuxOS.

sudo syslinuxos-install-extras networking   # DNS, DHCP, VPN, BGP/OSPF, HA, proxy, SNMP, IDS
sudo syslinuxos-install-extras devops       # monitoring, logging, containers, K8s, IaC
sudo syslinuxos-install-extras cloud        # AWS/Azure/GCP CLI, virtualization, storage, K8s
sudo syslinuxos-install-extras full         # all TIER2 in one operation
sudo syslinuxos-install-extras repos        # add official Grafana, HashiCorp, Helm APT repos

share

L'articolo SysLinuxOS 13.2 Revolution proviene da SysLinuxOS.

distroClone and distroClone-backup: A Complete System Protection Strategy for Debian-Based Distributions

Anyone maintaining a customised GNU/Linux system eventually faces two distinct but related needs: a reliable backup to restore from in case of failure, and a bootable live ISO to deploy on new machines or preserve as a system snapshot. Until now, covering both scenarios required separate tools and manual procedures. distroClone and distroClone-backup solve both problems in a single, graphical, automated workflow.

This guide covers the features of each tool individually, then walks through the integrated workflow for running them together as a two-tier protection strategy.

distroClone — Live ISO Builder

distroClone is a graphical tool that generates bootable live ISO images directly from the running system. It works on any Debian-based distribution: Debian, Ubuntu, Linux Mint, LMDE, Elementary OS, SysLinuxOS, ZorinOS, and their derivatives.

How It Works

At startup, distroClone automatically detects the installed distribution, version, desktop environment, architecture, and kernel. The graphical interface is built on YAD (preferred) with Zenity as a fallback, and supports custom branding. A TTY mode is also available for headless or display-less environments.

The build process runs through approximately 30 automated steps:

– System detection and information gathering
– Welcome screen with a configuration summary
– Squashfs compression profile selection
– Live system password and hostname configuration
– Automatic installation of required packages (xorriso, mtools, isolinux, etc.)
– Full rootfs clone into a temporary working directory
– Compressed Squashfs filesystem generation
– Calamares installer integration with automatic branding
– Optional pause for custom branding insertion
– Dual boot support: UEFI and Legacy BIOS
– Final ISO assembly with xorriso

The output ISO is automatically named in the format `DistroName-Version-Desktop.iso`.

Squashfs Compression Profiles

distroClone offers three compression profiles selectable from the GUI:

Standard xz: 15–20 min Balanced size and speed
Fast lz4: 5–10 min Quick testing builds
Maximum xz+bcj: 25–35 min Minimum file size for distribution

System Requirements

– Debian-based system (Bookworm or later, Ubuntu 22.04+, Mint, LMDE, SysLinuxOS, ZorinOS 18+)
– At least 10–25 GB of free space on `/mnt`
– Runtime dependencies installed automatically: `yad`, `rsync`, `imagemagick`

Installation

wget https://github.com/fconidi/distroclone/releases/download/v1.3.4/distroClone_1.4.10_all.deb
sudo apt install ./distroClone_1.4.10_all.deb
sudo apt install -f

Usage

sudo distroClone

distroClone-backup — Incremental Rootfs Backup and Restore

distroClone-backup is the companion tool for ongoing system protection. It handles continuous rootfs backup, scheduled incremental backups, and one-click restore when something goes wrong.

How It Works

The GTK/YAD graphical interface presents a dashboard on first launch showing the detected distribution, kernel version, current cache status, backup size, and active cron schedule. All operations are controlled from this single interface without touching the terminal.

The backend is built on `rsync`. A full backup clones the entire rootfs to the configured cache directory, excluding virtual filesystems (`/proc`, `/sys`, `/dev`), system caches, temporary directories, and snap folders. Incremental backups use `rsync –checksum` to transfer only files changed since the last run.

Key Features

**Full Backup**
Complete rootfs clone via rsync. This is the mandatory baseline before any incremental backup can run. The cache is stored at `<cache-dir>/<distro>_backup/.rootfs_cache`. Typical duration: 5–20 minutes depending on system size.

**Incremental Backup**
Transfers only files modified since the last execution. Fast, space-efficient, and well-suited for automated nightly runs.

**Btrfs Snapshots**
When the destination resides on a btrfs filesystem, each backup automatically generates a read-only snapshot named `@YYYY-MM-DD_HH:MM`. Excess snapshots are deleted automatically based on a configurable retention policy (0–20 snapshots, default: 3). Any available snapshot can be selected for restore directly from the GUI.

**Cron Scheduler**
Automated backup scheduling is handled entirely from the GUI: choose frequency (daily, weekly, monthly), day of the week (for weekly schedules), execution time, and whether to receive a desktop notification on completion. The crontab entry is written automatically to the root crontab.

**Safe Restore**
The restore operation overwrites system files from the cache using rsync, always protecting `/home`, `/root`, and `/boot/efi`. The confirmation dialog displays the backup date, saved distribution name, saved kernel version, and cache size before proceeding.

**Configurable Cache Directory**
The cache can point to any path: an internal partition, an external USB drive, or an NFS mount. The default is `/mnt`.

**Optional /home Inclusion**
An option to include `/home` in the backup is available, with an explicit warning about the impact on disk space and backup duration.

**Real-Time Log**
Every operation is visible live in the log window and saved persistently to `/var/log/distroclone-backup.log`.

**Multilingual Interface**
Language is detected automatically from the `LANG` environment variable. Supported languages: Italian, English, German, French, Spanish.

System Requirements

– Debian-based system (Bookworm or later, Ubuntu 22.04+, Mint, LMDE, SysLinuxOS, ZorinOS 18+)
– At least 10–25 GB of free space on the destination
– Runtime dependencies installed automatically: `yad`, `rsync`, `imagemagick`
– Recommended: `btrfs-progs` for snapshot versioning

Installation

wget https://github.com/fconidi/distroclone-backup/releases/download/v1.2/distroclone-backup_1.2_all.deb
sudo dpkg -i distroclone-backup_1.2_all.deb
sudo apt install -f

# Optional — for btrfs snapshot support:
sudo apt install btrfs-progs

Usage

distroClone-backup

Using Both Tools Together: The Two-Tier Protection Strategy

The real strength of these two tools becomes clear when they are used in combination. distroClone-backup protects the system on a daily basis; distroClone crystallises the system into a deployable live ISO. They are two complementary layers of protection and portability.

The Concept

Running System
│
├──► distroClone-backup → rsync cache + btrfs snapshots → FAST RESTORE
│ (automatic daily backup, continuous protection)
│
└──► distroClone → bootable live ISO → NEW HARDWARE / DISASTER RECOVERY
(run after each significant set of customisations)

Practical Workflow — Step by Step

**Phase 1 — System Preparation**

Install and configure your Debian-based system to the desired state: packages, configurations, desktop customisations, networking tools. This is the starting point for everything that follows.

**Phase 2 — First Full Backup with distroClone-backup**

Before any risky operation (major upgrade, kernel change, critical configuration edits), run a full backup:

1. Launch distroClone-backup from the application menu or run `distroClone-backup` in a terminal
2. Go to Settings and configure the cache directory (recommended: an external USB drive or a separate volume)
3. Click “Full Backup” and wait for completion (5–20 minutes)
4. Go to “Schedule Backup” and configure an automatic daily or weekly incremental backup

From this point, the system is protected. If anything breaks, clicking “Restore System” returns to the saved state within minutes.

**Phase 3 — Live ISO Creation with distroClone**

Once the system is in the desired state and the backup is current, generate the ISO:

1. Ensure sufficient free space is available on `/mnt`
2. Launch distroClone with `sudo distroClone`
3. On the welcome screen, verify the detected data: distribution, version, desktop environment
4. Select a compression profile (lz4 for speed, xz for minimum size)
5. Set the live system password and hostname
6. Click “Start Build” and wait (10–30 minutes)
7. The finished ISO will be in `/mnt/`, ready to write to a USB drive or archive as a snapshot

**Phase 4 — Routine Maintenance Cycle**

In the normal system lifecycle:

1. distroClone-backup runs automatically each night in the background, keeping the cache current
2. After any significant set of changes to the system (new tools installed, updated configurations), distroClone is run to refresh the ISO
3. Before major system upgrades, run a manual backup with distroClone-backup first, then proceed with the upgrade

Scenario: Kernel Upgrade

# Step 1 — Manual backup before the upgrade
distroClone-backup # Click “Full Backup” or run with –incremental-silent

# Step 2 — Upgrade the kernel

sudo apt update && sudo apt full-upgrade

# Step 3 — Reboot with the new kernel

sudo reboot

# Step 4 — Verify everything works

# Step 5 — If all is well: generate a new ISO with the updated kernel

sudo distroClone

If something fails at Step 4, open distroClone-backup and click “Restore System” to return to the pre-upgrade state.

Scenario: Disaster Recovery on New Hardware

The primary system fails irreversibly — a damaged disk, a dead motherboard. With both layers in place:

1. Boot the new machine from the ISO created with distroClone — a fully functional live environment with all your tools is immediately available
2. Install the system on the new hardware using Calamares (bundled in the ISO)
3. Mount the volume containing the distroClone-backup cache and run the restore — within minutes the system is identical to the original

Tips for Optimal Use

**Separate the destinations.** Use different directories for the distroClone-backup cache and for distroClone ISOs. Ideally, the backup cache goes on a dedicated volume or external drive; the ISOs go on a separate partition or NAS share.

**Schedule the backup, not the ISO.** distroClone-backup is well-suited for automatic scheduling. distroClone produces an ISO that should be run deliberately, as it requires 10–30 minutes and significant system resources.

**Back up before building.** Before every distroClone build, always run an updated incremental backup. This keeps the ISO and the backup cache synchronised in time.

**Use btrfs for the cache.** If possible, format the distroClone-backup destination volume as btrfs. Automatic snapshot versioning adds a third dimension of protection: not just the current system state, but also previous dated snapshots, all selectable from the GUI.

Quick Command Reference

Full backup (GUI): distroClone-backup
Silent incremental backup (cron): distroClone-backup –incremental-silent
Build a live ISO: sudo distroClone
Force English language: distroClone –lang=en

Both tools are open source, available on GitHub, and actively maintained as part of the SysLinuxOS project.

– distroClone: (https://github.com/fconidi/distroClone)
– distroClone-backup: (https://github.com/fconidi/distroclone-backup)

Guide to distroClone and distroClone-backup

enjoy

share

L'articolo Guide to distroClone and distroClone-backup proviene da SysLinuxOS.

share

L'articolo DistroClone Backup & Restore proviene da SysLinuxOS.

share

L'articolo DistroClone Live ISO Builder proviene da SysLinuxOS.

SysLinuxOS 13.1 MATE ISO

SysLinuxOS 13.1 GNOME ISO

SysLinuxOS 13.1 Mate Torrent

SysLinuxOS 13.1 Gnome Torrent

THINGS to DO

SysLinuxOS 13.1 for System Integrators Released

 

I’m proud to announce the release of SysLinuxOS 13.1

SysLinuxOS 13.1 is a maintenance and stabilization release of the Debian-based Linux distribution specifically designed for System Integrators and System Administrators.This release focuses on reliability, consistency, and long-term maintainability, providing a production-ready operating system for professional IT environments. SysLinuxOS delivers a fully preconfigured system with an extensive set of networking, diagnostic, integration, and monitoring tools, reducing deployment time and eliminating the need for post-installation configuration.

---

Design Philosophy

SysLinuxOS is engineered as a professional working platform, not a general-purpose desktop distribution.
It targets environments where rapid deployment, predictable behavior, and operational readiness are critical.

Key design principles include:

• Preconfigured networking and system services

• Immediate operational readiness in live and installed modes

• Consistent behavior across hardware platforms

• Full compliance with Debian standards

• Long-term maintainability and reproducibility

---

Release Highlights

System Stability and Reliability

SysLinuxOS 13.1 resolves multiple issues identified in version 13.0, with a strong focus on system robustness and predictable behavior:

• Optimized boot sequence, reducing startup times

• Improved UEFI compatibility on modern hardware platforms

• Resolution of post-installation configuration inconsistencies

• Refined dependency handling to prevent update-time conflicts

• Definitive resolution of critical package dependency issues (including nagios4, exim4-base, and related components)

---

Live Environment Configuration

Both desktop editions (MATE and GNOME) provide automatic login in live mode, enabling immediate system access without authentication prompts.
This configuration is intended for:

• Rapid hardware evaluation

• On-site diagnostics and recovery

• Incident response and emergency troubleshooting

• Demonstrations and proof-of-concept deployments

---

Networking and Wireless Analysis

Sparrow-Wifi Integration

SysLinuxOS 13.1 integrates Sparrow-Wifi, extending the distribution’s wireless diagnostics capabilities:

• Comprehensive scanning of surrounding Wi-Fi networks

• Real-time signal strength and quality analysis

• Channel optimization and interference detection

• Advanced troubleshooting of wireless connectivity issues

• Integration with existing analysis tools such as Wireshark, EtherApe, and Ettercap

---

Desktop Environment Consistency

A key objective of this release was achieving functional and visual parity between MATE and GNOME editions.
SysLinuxOS 13.1 delivers a uniform desktop experience across both environments:

• Consistent themes and icon sets

• Unified branding and wallpapers

• Identical application menu structures

• Harmonized UI configuration parameters

• Persistent graphical customizations across system updates

---

System Monitoring (Conky Suite)

SysLinuxOS 13.1 includes a standardized Conky-based monitoring framework, available on both desktop editions.

System Monitoring

• Per-core CPU utilization

• Real-time RAM and swap usage

• Thermal monitoring (CPU, GPU, storage devices)

• Disk utilization and mounted filesystems

• Top resource-consuming processes

• System load averages

Network Monitoring

• Local IP addresses per interface

• Real-time network throughput (ingress/egress)

• Interface status (e.g., eth0, wlan0)

• Default gateway and routing information

Public Connectivity

• Public IP address detection

• ISP and organization identification

• Internet connectivity status

The monitoring layout is optimized for 1920×1080 displays and remains fully configurable for alternative resolutions and multi-monitor deployments.

---

Installation Framework (Calamares)

The Calamares installer has been extensively customized to meet enterprise deployment requirements:

• Native SysLinuxOS branding and visual identity

• Predefined installation profiles optimized for professional use

• Recommended partitioning schemes for system integrators

• Automated post-installation configuration of services

• Full compatibility with both desktop environments

• Support for UEFI and legacy BIOS systems

• Rapid installation workflow without sacrificing completeness

---

Application Menu Stability

Menu instability following customization with Mozo (MATE) or Alacarte (GNOME) has been fully resolved:

• Menu structures compliant with freedesktop.org standards

• Stable behavior after menu editor usage

• Persistence across system updates

• Removal of duplicate application entries

• Preservation of user-defined customizations

---

Build Process and Compliance

SysLinuxOS 13.1 is built using live-build, the official Debian live system creation framework, ensuring:

• Full adherence to Debian packaging and build standards

• Reproducible and auditable build processes

• Long-term maintainability without third-party build tools

• Direct integration with official Debian repositories

• Enterprise-grade system consistency

---

Kernel and System Behavior

SysLinuxOS 13.1 ships with the Liquorix 6.16.8-1 kernel, selected for its balance between performance and stability:

• Low-latency scheduling suitable for real-time workloads

• Improved desktop and interactive responsiveness

• Extended support for modern hardware platforms

• Performance optimizations without compromising system stability

OS-Prober remains enabled by default, ensuring reliable detection of existing operating systems during GRUB configuration.

---

Network Interface Naming

Traditional network interface naming conventions (eth0, wlan0, etc.) are used in place of systemd’s predictable naming scheme. This decision supports:

• Simplified scripting and automation

• Faster operational troubleshooting

• Compatibility with existing enterprise documentation

• Portability of network configurations across systems

---

Available Editions

• SysLinuxOS 13.1 MATE
  Lightweight and resource-efficient desktop environment suitable for classic workflows and performance-sensitive systems.

• SysLinuxOS 13.1 GNOME
  Modern desktop environment offering a contemporary user interface while maintaining full professional functionality.

---

System Requirements

• Architecture: 64-bit (amd64)

• Memory: Minimum 4 GB RAM (8 GB recommended for professional environments)

• Storage: Minimum 25 GB available disk space

• Firmware: Legacy BIOS or UEFI

SysLinuxOS 13.1 for System Integrators Released

share

L'articolo SysLinuxOS 13.1 Released proviene da SysLinuxOS.

SysLinuxOS 13 Gnome released

SysLinuxOS 13 Gnome released. Following the recent release of SysLinuxOS 13 Mate, the SysLinuxOS project is pleased to announce the availability of the new edition: SysLinuxOS 13 GNOME.
This release introduces the GNOME 48 desktop environment, designed to deliver a modern, clean, and productivity-oriented experience while maintaining the core values of stability and reliability.

---

Release Goals

SysLinuxOS is a Linux distribution built to be stable, modular, and secure, aimed primarily at system integrators, system administrators, and IT professionals.
It is not a “plug & play” distribution for beginners: it requires a solid knowledge of Linux and system management. The goal is to provide a reliable platform for production environments, adaptable to the needs of those who integrate, maintain, and manage infrastructures.

---

Technical Details

• Base: Debian 13 (Trixie – Stable branch)
• Kernel: Liquorix, optimized for superior desktop and multitasking performance
• Desktop Environment: GNOME 48 with GTK 4 libraries
• Package Management: APT with official Debian repositories
• Default Tools: LibreOffice, Firefox ESR, GNOME Terminal, GNOME Software, and essential administration/monitoring utilities
• Security: constant updates via Debian Security channels.
• Optimizations: preconfigured for faster boot times, reduced resource usage, and improved responsiveness on modern hardware

---

Changelog – Key Differences between Mate and GNOME Editions

• Desktop Environment: Mate 1.26 → GNOME 48
• Graphics Framework: GTK 3 → GTK 4
• Window Manager: Marco → Mutter
• File Manager: Caja → Nautilus
• Terminal Emulator: MATE Terminal, Terminator → GNOME Terminal, Terminator
• Control Center: Mate Control Center → GNOME Settings
• Software Ecosystem: Synaptic, GNOME Extensions integration
• User Experience: GNOME Shell workflow, minimalist interface, and optimized multitasking

---

Conclusion

With SysLinuxOS 13 GNOME, we expand the SysLinuxOS family by providing a modern, responsive, and tightly integrated desktop environment, built on Debian 13 Trixie and powered by the Liquorix kernel (you can also use the official debian kernel).
The project continues to grow, offering IT professionals a Linux distribution that is reliable, secure, and ready to be deployed in complex production environments.

 

SysLinuxOS 13 (for System Integrators)

SysLinuxOS 13 Gnome released

 

DOWNLOAD

Login:

user = admin

password = root

 

enjoy

 

share

L'articolo SysLinuxOS 13 Gnome released proviene da SysLinuxOS.

share

L'articolo SysLinuxOS 13 Mate released proviene da SysLinuxOS.