EFForg / EFForg/rayhunter

build-firmware-devel produces too large binaries for moxee

Open
#733 1 comment 0 reactions 0 assignees View on GitHub
bug moxee
Dominant language
Rust
Stars
5.8k
Forks
490
Avg merge
3d 10h
Merged PRs (30d)
23

Description

### Prerequisites

- [x] I have read [CONTRIBUTING.md](https://github.com/EFForg/rayhunter/blob/main/CONTRIBUTING.md)

### Bug Report Details

The moxee device has two partitions, root partition and user data:

```
df -h
Filesystem Size Used Available Use% Mounted on
ubi0:rootfs 66.6M 47.8M 18.8M 72% /
tmpfs 64.0K 4.0K 60.0K 6% /dev
tmpfs 78.6M 20.0K 78.6M 0% /run
tmpfs 78.6M 536.0K 78.1M 1% /var/volatile
tmpfs 78.6M 0 78.6M 0% /media/ram
tmpfs 78.6M 536.0K 78.1M 1% /var/lib
ubi0:usrfs 9.3M 1.8M 7.5M 19% /data
/dev/ubi3_0 6.6M 224.0K 6.0M 4% /usrdata
/dev/ubi1_0 34.4M 30.5M 3.9M 89% /firmware
ubi0:cachefs 32.5M 24.0K 30.8M 0% /cache
```

the firmware-devel build of rayhunter-daemon is 14 MB does not fit into /data.

we should reconsider where /data/rayhunter is stored and potentially symlink it onto the `rootfs` filesystem to get more space (similar to tplink installer). As it stands there is barely any room for recordings even with the release firmware.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.