Skip to content

Document why --max-range appears twice on image installs#145

Merged
d4rken merged 1 commit into
devfrom
docs/image-options-max-range
Jul 2, 2026
Merged

Document why --max-range appears twice on image installs#145
d4rken merged 1 commit into
devfrom
docs/image-options-max-range

Conversation

@d4rken

@d4rken d4rken commented Jul 2, 2026

Copy link
Copy Markdown
Member

On a new-image feeder the daemon cmdline carries --max-range 450 twice — once from JSON_OPTIONS and once from FEED_IMAGE_OPTIONS — which reads like a copy-paste bug. It is not: legacy images ship their own JSON_OPTIONS via /boot/airplanes-env without a range cap (so the FEED_IMAGE_OPTIONS copy is the only cap there), while standalone installs get it only from JSON_OPTIONS. readsb takes the last occurrence and both are the same value. Add a comment so the overlap does not get "cleaned up" and silently drop the cap for one population.

JSON_OPTIONS and FEED_IMAGE_OPTIONS both default --max-range 450, so a
new-image cmdline carries it twice. The overlap is load-bearing across
install populations (legacy /boot env lacks the cap; standalone lacks
FEED_IMAGE_OPTIONS), so document it instead of deduping.
@d4rken d4rken merged commit 430651d into dev Jul 2, 2026
13 checks passed
@d4rken d4rken deleted the docs/image-options-max-range branch July 2, 2026 10:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant