How to Set Up Pardus Image Creator for Custom OS Deployment

Start with the right tool: Pardus Image Writer writes images; it does not build them

There is no verified Pardus application named “Pardus Image Creator” in the current official Pardus application documentation. The closest official tool is Pardus Image Writer. Pardus describes it as a utility for writing Linux or Windows image files to a USB drive, and its source repository describes ISO and IMG writing as its purpose. It does not assemble packages, customize a Pardus installation, or create a new operating-system ISO.

For custom OS deployment, treat image creation and USB deployment as two separate jobs. Build or obtain a bootable ISO that already contains the operating system and configuration you need; then use Pardus Image Writer to copy that ISO to a USB drive. This is a good fit when you already have a tested ISO and want a repeatable installer USB. If you need to add software, change branding, or configure an installer inside the ISO, Image Writer alone is not the right tool.

The steps below use Pardus Image Writer for the supported write-to-USB task and explain what must be decided before you build a custom image. Menu wording and package availability can differ by Pardus release. The official Pardus download page currently lists Pardus 25.2 editions; check the release that matches your deployment target before choosing a base image.

Decide whether you need a custom ISO or just a deployment USB

If all target computers should install the same official Pardus edition, download its ISO from the Pardus download page and use Image Writer. If every machine needs the same extra application or settings, consider applying those after installation with a documented setup script or configuration-management tool. That is usually simpler to update than maintaining a modified installer.

Build a custom ISO only when the content must be present before first boot—for example, a controlled live environment, a specialized recovery image, or an installer workflow managed by your organization. Pardus Image Writer is not the builder for this work. Debian’s live-build is the documented tool for assembling Debian Live images, with package lists, hooks, and other build configuration. A generic Debian Live configuration does not automatically produce an official Pardus image. A Pardus-derived image requires a release-matched package source, signing keys, boot configuration, and installer choices that are supported and tested for that Pardus release.

In particular, decide whether you need a live session, an installer that places the system on disk, or both. A bootable live ISO is not necessarily an installable system. Follow the matching release’s build documentation and test the resulting artifact in a virtual machine before using it on real hardware. Do not label a generic Debian build as a Pardus release.

Install Pardus Image Writer

On a Pardus system, refresh package metadata and check whether the package is available in the enabled repositories:

sudo apt update
apt policy pardus-image-writer

If APT shows a candidate version, install the repository package:

sudo apt install pardus-image-writer

Open Pardus Image Writer from the application menu. If the package is unavailable for your release, do not add an unfamiliar repository just to obtain it. The official source repository documents a source-run option for Debian-based systems. It lists the application’s dependencies and these commands:

sudo apt install gir1.2-glib-2.0 gir1.2-gtk-3.0 python3-gi python3-requests python3-pyudev parted
git clone https://github.com/pardus/pardus-image-writer.git ~/pardus-image-writer
python3 ~/pardus-image-writer/src/Main.py

Source dependencies or permissions can change, so check the repository README and use a branch compatible with your Pardus release. A package from the Pardus repository is generally easier to keep updated and audit than an unpinned development checkout.

Prepare the ISO before writing it

Use a completed ISO file, not a folder of files and not an installed system’s root directory. If you are building the ISO yourself, keep the build configuration and versioned package list with the release notes so the image can be rebuilt. Record the Pardus base release, architecture, included packages, and intended boot mode. This makes a later rebuild easier to compare.

Check the file’s integrity before writing it. When the image publisher provides a checksum or signature, compare against that independently obtained value. A local hash command can calculate a digest:

sha256sum custom-pardus.iso

This command only reports a hash. It does not prove authenticity by itself; the result must match a trusted value published by the image maintainer. Pardus download directories provide checksum files for official releases. Use the checksum algorithm and verification instructions supplied for the exact ISO you downloaded.

Also confirm that the ISO is intended for the target architecture and firmware setup. An image built for one architecture may not boot on another. If you need Secure Boot, encryption, unattended installation, or a specific partition layout, verify those requirements in the image’s own documentation rather than assuming the writer configures them.

Write the ISO to a USB drive

1. Back up anything on the USB drive. Writing an image overwrites its existing contents.
2. Connect the USB drive and identify it by its capacity and device name in the operating system. Disconnect other removable drives if that makes selection clearer.
3. Open Pardus Image Writer, choose the prepared ISO file, and select the intended USB device. Read the device details carefully before starting.
4. Start the write and wait for the application to report completion. Do not unplug the device while it is writing.
5. Safely eject the drive, then use it to boot a test machine or virtual machine if the workflow supports USB passthrough.

Interface details may vary by release. The important check is the selected source ISO and destination USB device, not a particular button label. Never select the computer’s internal system disk. Image writing is destructive to the chosen target device.

Test the deployment before using it at scale

Boot the USB on at least one representative target. Confirm that the firmware sees the device, the boot menu appears, the live session or installer starts, storage is detected, and the included network and input devices work. If the image is meant to install Pardus, complete one test installation on a spare machine or virtual disk and check the first boot, user creation, updates, and required applications.

A successful write is not the same as a successful deployment. The practical pass criteria are that the intended ISO was written to the intended USB, the USB boots on the target hardware, and the resulting live or installed system meets the stated deployment requirements. If the USB does not appear in the boot menu, check the firmware’s boot mode and USB boot settings before rebuilding the image. If boot begins but the installer or hardware fails, investigate the image configuration, package sources, and device compatibility rather than repeatedly rewriting the same ISO.

For a fleet, pilot the image on a small sample of each hardware model and keep a tested rollback image. Avoid baking personal accounts, passwords, machine-specific identifiers, or private keys into a reusable image. Rebuild and retest after changes to the base release, kernel, package list, or installer configuration.

Quick decision guide

Official references

• Pardus Applications: Image Writer description
• Pardus Image Writer source repository and README
• Pardus download page and release information
• Debian Live Manual
• Debian live-build manual page