Fix systemd service to run with native root privileges

[Copilot]

The systemd service configuration incorrectly used privilege escalation prefix and sudo commands, preventing proper execution of cryptsetup/mount operations.

Changes

• filurn.service: Removed + prefix from ExecStart directive
• filurn-mount.sh: Removed sudo from all commands (umount, cryptsetup, mkfs, mount, rmdir, touch)

Context

Systemd services run as root by default. The + prefix is for privilege escalation from a non-root user context, which doesn't apply here. The sudo commands would fail in service context due to lack of TTY and authentication unavailability.

[Service]
Type=simple
-ExecStart=+/usr/local/bin/filurn/filurnd.sh
+ExecStart=/usr/local/bin/filurn/filurnd.sh

-sudo cryptsetup open --type plain --cipher aes-xts-plain64 --key-file /dev/urandom "$DISK" "$NAME"
+cryptsetup open --type plain --cipher aes-xts-plain64 --key-file /dev/urandom "$DISK" "$NAME"

Original prompt

Is this project correctly built as a system service ?

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

This PR adjusts Filurn’s systemd/service execution model to rely on systemd’s native root execution rather than in-command privilege escalation, so cryptsetup/mount-related operations can run correctly in a service context.

Changes:

• Removed the + execution prefix from the systemd unit’s ExecStart.
• Removed sudo from privileged commands in filurn-mount.sh (umount/cryptsetup/mkfs/mount/etc.).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
filurn.service	Simplifies ExecStart by removing the + prefix so the service runs normally under systemd.
filurn-mount.sh	Removes sudo usage so privileged operations run directly when invoked by the root-run service.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.