LiaisonOS — Emergency Communications for Ham Radio
Version 2.2.4 — April 2026 Debian 13 (Trixie) Live/Installable ISO
⚠️ This project has moved!
LiaisonOS is now distributed exclusively through its new home. Downloads, documentation and release notes are available at:
🌐 https://liaisonos.com/download
This SourceForge page will no longer be updated after version 2.2.4.
Français? Voir LISEZMOI.md pour la version française.
What's New in Version 2.2.4
QtTermTCP — BBS Directory
- BBS Directory — Filterable list of known BBS stations (TPRFN network and others). Filters automatically by current band (detected from rigctld), VARA bandwidth setting, and UTC operating hours
- Connection probability — Each station shows an estimated connection probability (%) based on real-time HF band conditions from HamQSL and distance from your grid square
- QSY on select — Selecting a station QSYs the rig automatically via rigctld and opens the VARA connect dialog pre-filled with the callsign
- Auto-add unknown stations — When connecting to a callsign not in the directory, QtTermTCP offers to add it automatically
- Station editor — Add, edit, and delete BBS stations. Supports multiple bands per station and multiple bandwidths (500/2300/2750)
- Local SQLite storage — Directory data stored locally in SQLite. Online refresh merges new stations without overwriting your local edits
- BBS menu — New dedicated BBS menu in the menubar (BBS Directory and BBS Cache)
- VARA HF default — Default bandwidth changed to 500 Hz
USB Live Run — Persistence
- BBS Cache and BBS Directory now persist across reboots on USB Live Run — no more losing your cached bulletin lists after a reboot
What's New in Version 2.2.3
Bug Fix — Overlay Scripts
- Fixed — A script error in v2.2.2 corrupted several overlay files (
wrapper-rigctld.sh,wrapper-gpsd.sh,et-audio,et-log, radio audio profiles, and others), breaking rigctld, gpsd and et-supervisor on startup. All affected files have been restored
What's New in Version 2.2.2
Pat Winlink — Updated to v1.0.0
- Updated to v1.0.0 — Latest upstream release of the Pat Winlink client
QtTermTCP — BBS Session Cache
- BBS session cache — Sessions with packet BBS nodes are now cached locally by callsign using SQLite. Bulletin lists and message bodies are stored automatically during your session
- Offline browsing — Browse cached bulletins and read messages anytime via the BBS Cache dialog, even without a radio connection
What is LiaisonOS?
LiaisonOS is a Debian 13 (Trixie) live and installable Linux ISO purpose-built for ham radio emergency digital communications. It includes a complete suite of pre-configured digital mode software, offline maps, and a web-based dashboard for one-click operation. Two deployment modes: USB Live Run (boot any PC from a USB drive) or HDD install (permanent installation with Calamares). Bilingual English/French interface throughout. Created by Sylvain Deguire (VA2OPS), original concept by Gaston Gonzalez (KT7RUN).
Pre-Installed: Wine, VARA & VarAC
LiaisonOS is the only ham radio Linux distribution that ships VARA and VarAC ready to run. No manual Wine configuration, no downloading installers, no troubleshooting DLL issues.
- Wine 32-bit — Pre-configured
.wine32prefix, ready to launch Windows ham radio applications - VARA HF & VARA FM — High-performance modems pre-installed (included with permission from EA5HVK)
- VarAC — HF chat client for VARA, pre-installed (Limited Distribution Agreement with 4Z1AC — license presented on first launch)
- Complete vs Lite ISO — The build system offers both: the Complete ISO includes Wine/VARA/VarAC, the Lite ISO omits them for a smaller download
- Zero configuration — VARA and VarAC launch from the Dashboard like any native Linux application
Bundled Software
Radio Control
- Hamlib / rigctld — CAT control with udev auto-detection for 24+ radios
- Direwolf — Software TNC (AX.25 packet modem)
- Flrig — Rig control GUI
Winlink Email
- Pat — Winlink client (custom LiaisonOS build)
- ARDOP modem — HF Winlink transport
- VARA HF / VARA FM — High-performance Winlink modems (via Wine)
HF Chat
- VarAC — HF chat client over VARA modem (via Wine)
- Chattervox — Signed AX.25 text chat (built from source, LiaisonOS fork)
APRS
- YAAC — APRS client with mapping
BBS (Bulletin Board System)
- LinBPQ — Packet BBS server with web admin interface
- QtTermTCP — BBS terminal client
- Paracon — BBS / Telnet terminal client
Digital Modes
- WSJT-X — FT8, FT4, and other weak-signal modes
- JS8Call — HF keyboard-to-keyboard messaging
- JS8Spotter — JS8Call activity monitor
- Fldigi / Flmsg / Flamp / Flwrap — Multi-mode digital suite (PSK, RTTY, CW, NBEMS)
Repeater Directory
- et-repeater — Offline repeater browser with RepeaterBook CSV import, distance filtering, favorites, and one-click radio programming via rigctld
Field Logging
- et-logger — POTA/SOTA field logger with auto-QSY, callsign lookup (US/CA), nearest parks, map view, ADIF export, touch-friendly UI
Mapping & Navigation
- Navit — Offline GPS turn-by-turn navigation with OpenStreetMap
- MBTile server — Local map tile server for offline mapping
- OpenStreetMap tiles — Pre-loadable offline map data
Offline Reference
- Kiwix — Offline Wikipedia / encyclopedia reader
- ZIM files — Downloadable offline content packages
HF Propagation
- ET-Predict — HF propagation prediction with VOACAP engine and interactive offline maps, by KT7RUN
General Applications
- QGIS — Geographic Information System
- Thunderbird — Email client
- Firefox ESR — Web browser
- Audacity — Audio editor
- GnuPG — Encryption and signing
System
- Calamares — Graphical installer (live USB to HDD)
- Auto-scaling — Automatic UI scaling for 7" to 10" screens
Operational Modes
The Dashboard provides 16 one-click operational modes:
| Category | Mode | Description |
|---|---|---|
| Winlink | Winlink (VARA HF) | Email over VARA HF modem |
| Winlink | Winlink (VARA FM) | Email over VARA FM modem |
| Winlink | Winlink (Packet) | Email over AX.25 packet radio |
| Winlink | Winlink (ARDOP) | Email over ARDOP modem |
| Chat | JS8Call | HF keyboard messaging |
| Chat | VarAC | HF chat via VARA modem (Wine) |
| Chat | Fldigi | Multi-mode digital (SSB/CW/PSK/RTTY) |
| Chat | Chattervox | Signed packet text chat |
| Chat | Chattervox (BT) | Signed chat via Bluetooth TNC |
| BBS | BBS Client (Paracon) | Connect to packet/Telnet BBS |
| BBS | BBS Client (QtTermTCP) | Connect to packet BBS |
| BBS | BBS Server | LinBPQ server with web interface |
| APRS | APRS Client (YAAC) | Position tracking & messaging |
| APRS | APRS Client (BT) | APRS via Bluetooth TNC |
| APRS | APRS Digipeater | Fill-in digipeater with position beacon |
| Other | FT8/FT4 (WSJT-X) | Weak signal digital modes |
| Other | Direwolf KISS TNC | Network TNC on TCP 8001 |
Web Dashboard & Supervisor
- One-click mode launch from an integrated web dashboard
- Real-time status: process health, audio devices, CAT control, GPS, Bluetooth TNC
- Automatic prechecks: callsign, audio devices, radio connection verified before launch
- Modem selection: BBS modes prompt for modem type (1200/9600/300 baud, VARA HF, VARA FM)
- Single supervisor daemon (
et-supervisor) replaces 12 individual systemd services - Crash recovery with automatic retry (handles PulseAudio timing on USB Live Boot)
- Clean shutdown: processes stopped in reverse order on mode switch
- Bilingual EN/FR interface based on language preference
Persistence System
When running from USB, the persistence system saves and restores your complete environment:
- User files: ~/Documents, ~/Downloads (rsync incremental sync)
- Application configs: Pat Winlink, JS8Call, WSJT-X, Fldigi, VarAC, YAAC, Navit, Direwolf, Chattervox, Repeater Directory
- Browser data: Firefox profile, Thunderbird (full profile compressed)
- System settings: WiFi networks, Bluetooth pairings, active radio selection, VarAC license
- Save & menu: Save & Reboot / Save & Shutdown / Save & Suspend with progress bar
- Hardware restore: WiFi and Bluetooth configs restorable to HDD installs via
et-restore-hw
Offline Capabilities
LiaisonOS is designed to operate with no internet connection:
- Navit — Offline GPS navigation with OpenStreetMap data
- Kiwix — Offline Wikipedia and encyclopedia reader
- MBTile server — Local map tile server for offline mapping
- Repeater Directory — Offline repeater browser (import CSV once, use offline forever)
- Offline patch system — USB-based updates with backup and rollback
- ET-Predict — HF propagation prediction with VOACAP and offline maps (no internet needed)
Supported Radios
LiaisonOS includes pre-configured radio profiles with udev auto-detection, rigctld integration, and documented setup notes for each model.
USB Direct (built-in USB serial)
| Vendor | Model | Notes |
|---|---|---|
| BG2FX | FX-4CR | USB CAT + audio |
| Icom | IC-705 | USB CAT + audio |
| Icom | IC-7100 | USB CAT + audio |
| Icom | IC-7200 | USB CAT + audio |
| Icom | IC-7300 | USB CAT + audio, CP210x dual-port |
| Icom | IC-9700 | USB CAT + audio, CP210x dual-port, VHF/UHF |
| QRP Labs | QMX | USB CAT |
| Xiegu | X6100 | USB CAT + audio |
| Yaesu | FT-710 | USB CAT + audio, CP2105 dual-port (best effort) |
| Yaesu | FT-891 | Via DigiRig DR-891 interface |
| Yaesu | FT-991A | USB CAT + audio, CP2105 dual-port |
| Yaesu | FTX-1 | USB audio + PTT only (no CAT — Yaesu has not published spec) |
Via DigiRig Interface
These radios require an external DigiRig or DigiRig Lite sound card interface for audio and PTT.
| Vendor | Model | Interface |
|---|---|---|
| Elecraft | KX-2 | DigiRig Mobile |
| Lab599 | TX-500MP | DigiRig Mobile |
| Xiegu | G90 | DigiRig Mobile |
| Yaesu | FT-818ND | DigiRig Mobile |
| Yaesu | FT-857D | DigiRig Mobile |
| Yaesu | FT-897D | DigiRig Mobile |
| — | (Any radio) | DigiRig Mobile (no CAT) |
| — | (Any radio) | DigiRig Lite |
Bluetooth TNC (KISS over Bluetooth)
These radios have a built-in hardware TNC and connect via Bluetooth serial (rfcomm). No sound card or Direwolf needed.
| Vendor | Model | Modes |
|---|---|---|
| BTECH | UV-PRO | YAAC, Chattervox |
| Kenwood | TH-D74 | YAAC, Chattervox |
| Kenwood | TH-D75 | YAAC, Chattervox |
| VGC | VR-N76 | YAAC, Chattervox |
Persistence (introduced in 1.5.2)
When you boot LiaisonOS from a USB drive, any changes you make — radio configurations, callsign settings, Winlink credentials, custom scripts, desktop preferences — are normally lost when you shut down. You start fresh every time.
Persistence changes that. Your entire user environment is saved to a dedicated partition on the USB drive (EMCOMM-DATA). The next time you boot, everything is exactly as you left it: your radio profiles, your Pat Winlink mailbox, your JS8Call settings, your bookmarks — everything.
Three Ways to Use Persistence
1. USB Live Boot (Primary Use Case)
Boot any PC from your USB drive and pick up right where you left off. Configure your station once, then carry it in your pocket. Plug it into any computer — your complete EmComm station is ready in minutes.
2. Backup Your Permanent Installation
Even if you run LiaisonOS installed on a dedicated PC, you can export your entire configuration to a USB drive. If your main system fails during an emergency, boot from the USB on any available computer — your settings, credentials, and radio profiles are all there.
3. Migrate Between Devices
Setting up a new laptop or replacing a damaged Toughpad? Instead of reconfiguring everything from scratch, export your persistence data from the old device and import it on the new one. Your complete station configuration moves with you — callsign, radio profiles, Winlink setup, digital mode settings, everything transfers in one step.
Why This Matters for Emergency Communications
In a real emergency, you don't have time to reconfigure software. Persistence means your USB drive becomes a complete, portable EmComm station that works on any available hardware. Lose your laptop? Borrow any PC, plug in your USB, and you're back on the air with your full configuration.
Important: Choosing the Right Installation Method
Before proceeding, understand when to use USB boot versus permanent installation.
Permanent Installation (Recommended for Operations)
A dedicated PC or laptop with LiaisonOS installed on the internal drive is always the best solution for serious emergency communications work.
- Maximum reliability — No USB drive to fail, lose, or forget
- Full performance — Native disk speed, no USB bottleneck
- Persistence built-in — All configurations saved automatically
- Ready when needed — Power on and operate immediately
- Professional deployments — Field hospitals, EOCs, shelters
Use permanent installation when:
- Operating a fixed EmComm station
- Running 24/7 BBS or gateway services
- Supporting critical emergency operations
- Maximum reliability is essential
USB Boot with Ventoy (Recommended for Testing & Backup)
USB boot is ideal for testing, training, demonstrations, and as a backup deployment option.
- Rapid testing — Try new ISO builds without touching your main system
- Portability — Carry LiaisonOS in your pocket
- Multi-boot — Keep multiple ISO versions on one drive
- Emergency backup — Boot any available PC in a crisis
- Training — Let students practice without permanent changes
Use USB boot when:
- Testing new ISO releases before deployment
- Training new operators
- Demonstrating LiaisonOS at events
- Backup option when primary system fails
- Temporarily converting any PC to an EmComm station
USB Speed Matters: Use a USB 3.x drive for Live Boot. USB 2.0 drives cause noticeably slower boot times, application launches, and persistence save/restore operations. A quality USB 3.0+ drive on a USB 3.0 port makes a significant difference in overall responsiveness.
Standard USB Boot (Quick Method)
The simplest way to create a bootable USB is to write the ISO directly to a drive. This is the recommended method for most users who just need to boot or install LiaisonOS.
The only software you need is a USB boot creator. Here are the most reliable options by platform:
Windows
- Rufus — Fast, reliable, open-source. The gold standard for Windows. rufus.ie
- balenaEtcher — Simple 3-step process, validates writes, cross-platform. etcher.balena.io
- Ventoy — Multi-boot capable, put multiple ISOs on one USB. ventoy.net
macOS
- balenaEtcher — Best choice for Mac, simple, reliable, native app. etcher.balena.io
- UNetbootin — Cross-platform, works well for Linux ISOs. unetbootin.github.io
- dd (Terminal) — Built-in, powerful but requires care.
sudo dd if=image.iso of=/dev/diskN bs=4M
Linux
- balenaEtcher — Same simple interface as other platforms. AppImage available.
- Ventoy — Install once, then just copy ISO files to USB. ventoy.net
- GNOME Disks — Built into most GNOME desktops, "Restore Disk Image" feature. Pre-installed.
- dd — Classic Unix tool, fast and reliable.
sudo dd if=image.iso of=/dev/sdX bs=4M status=progress
Recommendation
For beginners: balenaEtcher — Works on all platforms, impossible to accidentally overwrite your hard drive, validates the write.
For advanced users: Ventoy — Install it once on your USB drive, then simply copy ISO files to it. You can have LiaisonOS, a Windows installer, and system rescue tools all on one USB. See the detailed Ventoy guide below.
Why Ventoy? The Recommended USB Strategy
Traditional USB boot methods (dd, Rufus, balenaEtcher) write the ISO directly to the drive, which has significant limitations.
Traditional vs Ventoy:
- One ISO per drive → Multiple ISOs on same drive
- Must reflash entire drive for updates → Just copy/delete ISO files
- All drive space used for boot → Dedicated data partition available
- Data lost with each reflash → Data partition survives ISO updates
- Complex process each time → Simple file copy operation
The Ventoy Advantage
Ventoy transforms your USB drive into a boot manager that can launch any ISO file simply by copying it to the drive. This is revolutionary for LiaisonOS users:
- Test new builds instantly — Download a new LiaisonOS ISO, copy it to USB, reboot. No reflashing, no data loss.
- Keep multiple versions — Maintain the current stable release alongside beta versions for testing.
- Separate boot from data — Your maps, Wikipedia ZIM files, and configurations live on a separate partition that survives ISO updates.
- Emergency flexibility — In a real emergency, boot the proven stable ISO. For testing, try the latest build.
Partition Strategy Overview
This guide creates a USB drive optimized for LiaisonOS with the following layout:
┌─────────────────────────────────────────────────────────────────────┐
│ 64 GB USB Drive Layout │
├─────────────────────────────────────────────────────────────────────┤
│ │
│ ┌─────────────────┐ ┌──────┐ ┌────────────────────────────────┐ │
│ │ EMCOMM-ISO │ │ EFI │ │ EMCOMM-DATA │ │
│ │ ~12 GB │ │ 32MB │ │ ~46 GB │ │
│ │ │ │ │ │ │ │
│ │ • ISO files │ │ Boot │ │ • Maps (.mbtiles) │ │
│ │ • Ventoy │ │ sys │ │ • Wikipedia (.zim) │ │
│ │ │ │ │ │ • Documents │ │
│ │ exFAT │ │FAT16 │ │ • Config backups │ │
│ └─────────────────┘ └──────┘ └────────────────────────────────┘ │
│ Partition 1 Part 2 Partition 3 │
└─────────────────────────────────────────────────────────────────────┘
- Partition 1 — EMCOMM-ISO, ~12 GB, exFAT — Bootable ISOs via Ventoy
- Partition 2 — (EFI), 32 MB, FAT16 — Boot system (automatic)
- Partition 3 — EMCOMM-DATA, ~46 GB, ext4/exFAT — Maps, ZIM files, offline data
Why This Layout?
- ISO partition sized for multiple versions — 12 GB holds 3-4 LiaisonOS ISOs
- Data partition maximized — Maps and Wikipedia files can be several gigabytes each
- Cross-platform compatible — exFAT on boot partition works with Windows/Mac/Linux
- Linux-optimized data — ext4 provides better reliability (or exFAT if Windows access needed)
Prerequisites
- 64 GB (or larger) USB drive
- LiaisonOS ISO file
- Administrator/root access
WARNING: This process will erase all data on the USB drive. Back up any important files first!
Step 1: Download Ventoy
Download the latest Ventoy release:
- Official website: https://ventoy.net
- GitHub: https://github.com/ventoy/Ventoy/releases
Downloads:
- Windows:
ventoy-x.x.xx-windows.zip - Linux:
ventoy-x.x.xx-linux.tar.gz - macOS: See macOS section below
Step 2: Identify Your USB Drive
CRITICAL: Identifying the correct drive is essential. Using the wrong device will destroy data on that device!
Windows
- Open Disk Management (press
Win + X, select "Disk Management") - Locate your USB drive by size (~58 GB for a 64 GB drive)
- Note the disk number (e.g., "Disk 2")
Or use Command Prompt:
diskpart
list disk
exit
Linux
lsblk
Look for your USB drive by size. It will typically be /dev/sdb or /dev/sdc.
NAME SIZE TYPE MOUNTPOINTS
sda 500G disk
├─sda1 512M part /boot/efi
└─sda2 499G part /
sdb 58.2G disk ← Your 64 GB USB
└─sdb1 58.2G part /media/user/USB
macOS
diskutil list
Look for your USB drive (e.g., /dev/disk2). Verify by size (~58 GB for 64 GB drive).
Step 3: Back Up Existing Data
If your USB drive contains important data, copy it to a safe location first.
Windows
Use File Explorer to copy files to your computer.
Linux
mkdir -p ~/usb-backup
cp -av /media/$USER/YOUR_USB/* ~/usb-backup/
macOS
mkdir -p ~/usb-backup
cp -av /Volumes/YOUR_USB/* ~/usb-backup/
Step 4: Install Ventoy
Windows
- Extract
ventoy-x.x.xx-windows.zip - Run
Ventoy2Disk.exeas Administrator - Select your USB drive from the dropdown menu
- Click Options → Partition Configuration
- Check "Preserve some space at the end of the disk"
- Enter
47000MB (47 GB for your data partition) - Click Install
- Confirm the warning (this will erase the drive)
- Wait for completion
Linux
- Extract and navigate to Ventoy:
cd ~/Downloads
tar -xzf ventoy-x.x.xx-linux.tar.gz
cd ventoy-x.x.xx
- Unmount the USB drive:
sudo umount /dev/sdb1 2>/dev/null
sudo umount /dev/sdb2 2>/dev/null
- (Optional) Wipe existing partition table:
sudo wipefs -a /dev/sdb
- Install Ventoy with reserved space for data partition:
sudo ./Ventoy2Disk.sh -i -g -r 47000 /dev/sdb
Options explained:
-i: Install Ventoy-g: Use GPT partition table (recommended for UEFI)-
-r 47000: Reserve 47000 MB (47 GB) for data partition -
Confirm with
ywhen prompted.
Example output:
Ventoy: /dev/sdb will be formatted as GPT style.
Reserve 47000 MB disk space at the end of the disk.
Disk: /dev/sdb Size: 58.2 GB
Partition Style: GPT
Install Ventoy to /dev/sdb? (y/n) y
...
Install Ventoy to /dev/sdb successfully finished.
macOS
Ventoy does not have a native macOS GUI. Use one of these methods:
Option A: Boot into a Linux environment (VM or Live USB) and follow Linux instructions.
Option B: Use the Ventoy Web UI (experimental):
cd ventoy-x.x.xx
sudo ./VentoyWeb.sh
Then open http://127.0.0.1:24680 in your browser.
Option C: Prepare the USB drive on a Windows or Linux computer.
Step 5: Create the EMCOMM-DATA Partition
After Ventoy installation, you'll have two partitions and a block of free space at the end of the drive:
sdb1: Ventoy boot partition (~12 GB, exFAT)sdb2: EFI system partition (32 MB, FAT16)- Free space: ~47 GB — no partition exists yet!
You must create a new partition in that free space and then format it. Simply running mkfs won't work — the partition must be created first.
Windows
- Open Disk Management (press
Win + X, select "Disk Management") - Find your USB drive — you'll see the Ventoy partitions and an Unallocated block
- Right-click the Unallocated space → New Simple Volume
- Click Next, use all available space
- Assign a drive letter, click Next
- Format as exFAT, volume label:
EMCOMM-DATA - Click Finish
Linux — GNOME Disks (Recommended)
GNOME Disks is the easiest way to create the partition on Linux. It is pre-installed on most desktops including LiaisonOS.
- Open Disks from the application menu (or run
gnome-disksin a terminal) - Select your USB drive in the left panel (identify it by size, e.g. 64 GB)
- You'll see a visual bar showing the partitions. Look for the large block of Free Space at the end (~47 GB)
- Click on the Free Space block to select it
- Click the + (plus) button below the partition bar
- In the dialog that appears:
- Partition Size: Use the full available space (default)
- Volume Name:
EMCOMM-DATA - Type: Select Ext4 (recommended) or Other → exFAT if you need Windows access
- Click Create
- The partition is created and formatted — you're done!
Linux — Command Line (Alternative)
If you prefer the command line, use these two steps — first create the partition, then format it:
# Step 1: Create partition 3 in the free space
sudo sgdisk -n 3:0:0 -t 3:8300 -c 3:"EMCOMM-DATA" /dev/sdb
# Step 2: Format as ext4 (recommended)
sudo mkfs.ext4 -L EMCOMM-DATA /dev/sdb3
Options explained:
sgdisk -n 3:0:0: Create partition 3 using all remaining space-t 3:8300: Set type to Linux filesystem-c 3:"EMCOMM-DATA": Set the partition name
For exFAT (if you need Windows access):
sudo mkfs.exfat -n EMCOMM-DATA /dev/sdb3
Verify the final layout:
lsblk /dev/sdb
NAME SIZE TYPE
sdb 58.2G disk
├─sdb1 12.3G part ← Ventoy (EMCOMM-ISO)
├─sdb2 32M part ← EFI
└─sdb3 45.9G part ← EMCOMM-DATA (new!)
Important: After creating the partition, set ownership so your user can write to it:
# Mount, set ownership, then it's ready to use
sudo mount /dev/sdb3 /mnt
sudo chown $USER:$USER /mnt
sudo umount /mnt
macOS
- Open Disk Utility
- Select your USB drive in the sidebar
- Click Partition
- Click the + button to add a partition in the free space
- Name:
EMCOMM-DATA - Format: ExFAT
- Click Apply
Step 6: Rename Ventoy Partition (Optional)
Rename "Ventoy" to "EMCOMM-ISO" for clarity:
Windows
Right-click the Ventoy drive in File Explorer → Rename → EMCOMM-ISO
Linux
sudo umount /dev/sdb1
sudo exfatlabel /dev/sdb1 EMCOMM-ISO
macOS
Right-click in Finder → Rename
Step 7: Copy Your Files
Copy LiaisonOS ISO to Boot Partition
Simply copy your ISO file to the EMCOMM-ISO partition:
Windows / macOS: Drag and drop the ISO file using File Explorer / Finder.
Linux:
cp liaisonos-debian.iso /media/$USER/EMCOMM-ISO/
Pro tip: You can keep multiple ISOs on the same partition. Ventoy will show a menu to choose which one to boot.
Copy Data Files to Data Partition
Copy your maps, ZIM files, and other offline resources to EMCOMM-DATA.
Recommended folder structure:
EMCOMM-DATA/
├── Maps/
│ ├── osm-ca-zoom0to10-20251120.mbtiles
│ ├── osm-us-zoom0to11-20251120.mbtiles
│ └── osm-world-zoom0to7-20251121.mbtiles
├── Wikipedia/
│ ├── wikipedia_en_simple_all_nopic.zim
│ ├── wikipedia_en_medicine_nopic.zim
│ └── wikipedia_fr_simple_all_nopic.zim
├── Documents/
│ ├── emergency-procedures.pdf
│ └── frequency-plans.pdf
├── HamRadioEncyclopedia/
│ └── ham-radio-encyclopedia.zim
└── Backups/
└── config-backup.tar.gz
Step 8: Boot from USB
- Insert the USB drive into your computer
- Restart and enter the boot menu:
- Common keys: F12, F2, F10, ESC, or DEL (varies by manufacturer)
- Mac: Hold Option key during startup
- Select your USB drive from the boot menu
- Ventoy will display a menu of available ISOs
- Select your LiaisonOS ISO and press Enter
BIOS/UEFI Settings
If USB boot doesn't work, check these settings:
- Secure Boot — Disabled
- Boot Mode — UEFI (or try Legacy/CSM)
- Fast Boot — Disabled
- USB Boot — Enabled
Updating Your ISO
One of the biggest advantages of Ventoy: to test a new ISO build, simply:
- Delete the old ISO from
EMCOMM-ISO(optional — you can keep both) - Copy the new ISO to
EMCOMM-ISO - Reboot and select the new ISO from Ventoy menu
Your data on EMCOMM-DATA remains untouched!
Updating Ventoy
To update Ventoy without losing your ISOs or data:
Windows
- Run the new
Ventoy2Disk.exe - Select your USB drive
- Click Update (not Install)
Linux
cd ventoy-x.x.xx
sudo ./Ventoy2Disk.sh -u /dev/sdb
Linking Data Partition to LiaisonOS
When booted into LiaisonOS, you can create symlinks to use data from your USB data partition:
# Mount the data partition (if not auto-mounted)
sudo mount /dev/sdb3 /mnt/usb-data
# Create symlinks to map files
ln -s /mnt/usb-data/Maps/*.mbtiles ~/.local/share/liaisonos/mbtileserver/tilesets/
# Create symlinks to Wikipedia files
ln -s /mnt/usb-data/Wikipedia/*.zim ~/wikipedia/
Note: The exact device name may vary. Use lsblk to identify the correct partition.
Troubleshooting
USB drive not showing in boot menu
- Ensure Secure Boot is disabled in BIOS/UEFI settings
- Try both UEFI and Legacy boot modes
- Some older systems may require MBR instead of GPT
"Logical sector size is zero" error when renaming
- The partition is exFAT, not FAT32
- Use
exfatlabelinstead offatlabel
ISO won't boot
- Verify the ISO is not corrupted (check SHA256 hash)
- Try Ventoy's "memdisk" mode: Press F1 in Ventoy menu, select memdisk
- Check Ventoy documentation for any ISO-specific requirements
Partition not recognized after creation
- Unplug and replug the USB drive
- On Linux, run:
sudo partprobe /dev/sdb
Slow performance
- USB 3.0 drives in USB 3.0 ports perform significantly better
- Consider a high-quality USB drive rated for sustained read/write speeds
- For critical operations, permanent installation is recommended
MBR alternative for older systems:
sudo ./Ventoy2Disk.sh -i -r 47000 /dev/sdb # Without -g
exFAT label fix:
sudo exfatlabel /dev/sdb1 EMCOMM-ISO
Quick Reference
Linux Commands Summary
# Identify USB drive
lsblk
# Install Ventoy (64 GB drive)
sudo ./Ventoy2Disk.sh -i -g -r 47000 /dev/sdb
# Create data partition
sudo sgdisk -n 3:0:0 -t 3:8300 -c 3:"EMCOMM-DATA" /dev/sdb
# Format data partition ext4
sudo mkfs.ext4 -L EMCOMM-DATA /dev/sdb3
# Set ownership
sudo mount /dev/sdb3 /mnt && sudo chown $USER:$USER /mnt && sudo umount /mnt
# Rename Ventoy partition
sudo exfatlabel /dev/sdb1 EMCOMM-ISO
# Copy ISO
cp liaisonos.iso /media/$USER/EMCOMM-ISO/
# Update Ventoy
sudo ./Ventoy2Disk.sh -u /dev/sdb
Final Partition Layout
/dev/sdb (64 GB USB Drive)
├── sdb1 EMCOMM-ISO ~12 GB exFAT [Ventoy + ISOs]
├── sdb2 (EFI) ~32 MB FAT16 [Boot system]
└── sdb3 EMCOMM-DATA ~46 GB ext4 [Data]
Summary: When to Use What
- Primary EmComm station → Permanent installation on dedicated hardware
- 24/7 BBS or gateway → Permanent installation
- Testing new ISO builds → USB with Ventoy
- Training sessions → USB with Ventoy
- Demonstrations → USB with Ventoy
- Backup deployment → USB with Ventoy
- Emergency field deployment → Either — USB = flexibility, Permanent = reliability
Remember: A well-maintained USB boot drive is an excellent backup, but a dedicated EmComm computer with permanent installation remains the gold standard for serious emergency communications work.
Resources
- VA2OPS: https://va2ops.ca
- LiaisonOS Project: https://liaisonos.ca
-
Email: info@liaisonos.com
-
Ventoy Official Site: https://ventoy.net
- Ventoy GitHub: https://github.com/ventoy/Ventoy
- Ventoy Documentation: https://ventoy.net/en/doc_news.html
Document version: 2.1.8 Last updated: March 2026 Created for LiaisonOS Debian Edition
