Skip to content

FAQ/Charge Control C: Add question about full root partition#98

Merged
lategoodbye merged 1 commit intoeverest/charge_control_cfrom
everest/charge_control_c_full_rootfs
May 5, 2026
Merged

FAQ/Charge Control C: Add question about full root partition#98
lategoodbye merged 1 commit intoeverest/charge_control_cfrom
everest/charge_control_c_full_rootfs

Conversation

@lategoodbye
Copy link
Copy Markdown
Member

Since the latest Charge Control C EVerest development images had a full root partition, this should at least provide a workaround.

@lategoodbye lategoodbye requested review from barsnick and mhei April 30, 2026 13:17
Copy link
Copy Markdown
Contributor

@barsnick barsnick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one grammar nit.

Comment thread docs/source/troubleshooting.rst Outdated

The latest EVerest development images doesn't have much space left on the root
partition. As a temporary solution you can remove the boost header files,
in order to free some space:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it necessary to mention what there files are actually good for? ("You will no longer be able to compile Boost C++ programs on the target.")

But frankly, it doesn't matter, no-one will need this.

Since the latest Charge Control C EVerest development images had a full
root partition, this should at least provide a workaround.

Signed-off-by: Stefan Wahren <stefan.wahren@chargebyte.com>
@lategoodbye lategoodbye force-pushed the everest/charge_control_c_full_rootfs branch from 4e64725 to 7e24246 Compare May 4, 2026 14:53
@lategoodbye lategoodbye requested a review from barsnick May 4, 2026 14:54
@lategoodbye lategoodbye merged commit 661adae into everest/charge_control_c May 5, 2026
1 check failed
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.

3 participants