For years, every time I booted into Linux, I'd SSH into my own machine just to grab a file from my Windows partition. Or worse — I'd reboot, wait for Windows updates, grab the file, and reboot back. Sound familiar?
Dual-booting should be the best of both worlds. In practice? It's a constant dance of "which OS has my files?"
That's why I built Lindy.
The Problem
Every Linux dual-boot user knows this pain:
- Windows NTFS partitions don't mount automatically with write access
- chown, chmod, fstab edits — it's 2026, why is this still manual?
- Every distro handles mount differently
- New Linux users give up and stay on Windows
What Lindy Does
Lindy is a Tauri 2 + React desktop app that detects your Windows partitions, scans for user folders, and mounts them with one click. No terminal, no fstab editing, no permission headaches.
One click. Your Windows folders appear in your Linux home.
Features
- Smart Auto-Map — Detects Windows partitions (NTFS/exFAT), finds usernames, maps Desktop, Documents, Downloads, Pictures, Music, Videos automatically
- Manual Auto-Map — Power users can specify custom mount points and folder selections
- Secure — Proper permissions via polkit, no wild chmod 777
- Built with Tauri 2 + React + Rust — Lightweight, fast, native performance
The Tech Side
Built entirely in the open:
- Tauri 2 for the native desktop shell (tiny bundle vs Electron)
- React for the UI
- Rust backend handles partition detection and mount logic via Tauri commands
- pnpm for dependency management
- Cargo.toml: tauri 2, serde, serde_json, tauri-plugin-opener, tauri-plugin-dialog
The mount backend parses lsblk output, detects NTFS/exFAT partitions, finds Windows user directories, and mounts them using system utilities with polkit elevation. All the complexity is hidden behind a clean UI.
Try It
Lindy is open source and available now:
GitHub: https://github.com/ziuus/lindy
Installers: .deb, .rpm, .AppImage available in the repo
I'd love feedback, contributions, or just to hear if this solves the same problem for you that it solved for me.
Have you been fighting with dual-boot file access? Drop a comment — I want to hear your setup horror stories too.
Top comments (0)