move sysupdate.log to ssd

[kristapsk]

To reduce unnecessary wear on uSD card.

Resolves #42.

Summary by CodeRabbit

• Chores
  • Default system update log location changed from /var/log/sysupdate.log to /ssd/sysupdate.log.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The update.sh script's default log file path is relocated from /var/log/sysupdate.log to /ssd/sysupdate.log. This is a configuration path change with no modifications to script logic, error handling, or control flow.

Changes

Cohort / File(s)	Summary
Log file path update update.sh	Changed default sysupdate log file destination from /var/log/sysupdate.log to /ssd/sysupdate.log. No other code or control flow changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related issues

• nakamochi/img#31: Matches the objective of moving the sysupdate log location from /var/log to /ssd to reduce wear on the microSD card.

Poem

🐰 I hopped a path from card to speedy drive,
A tiny change so logs may thrive,
SSD so cosy, wear fades away,
A quiet hop that saves the day,
— nibble, code, and carrot jive.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR only updates the default log file path but does not implement the symlink requirement specified in issue #42.	Implement the symlink in /var/log pointing to the log file on the SSD as required by issue #42.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarises the main change: updating the sysupdate.log file path from /var/log to /ssd.
Out of Scope Changes check	✅ Passed	The changes are entirely within scope, addressing the log file relocation objective from issue #42.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1d6de44 and b23f541.

📒 Files selected for processing (1)

• update.sh (1 hunks)

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: kristapsk
Repo: nakamochi/sysupdates PR: 43
File: update.sh:18-18
Timestamp: 2025-11-27T08:38:05.930Z
Learning: In the nakamochi/sysupdates repository, the update.sh script is deployed to and executed from /ssd/sysupdates/ (via cron at /etc/cron.hourly/sysupdate). If /ssd is not mounted, the script cannot execute at all, making additional validation of /ssd availability unnecessary.

📚 Learning: 2025-11-27T08:38:05.930Z

Learnt from: kristapsk
Repo: nakamochi/sysupdates PR: 43
File: update.sh:18-18
Timestamp: 2025-11-27T08:38:05.930Z
Learning: In the nakamochi/sysupdates repository, the update.sh script is deployed to and executed from /ssd/sysupdates/ (via cron at /etc/cron.hourly/sysupdate). If /ssd is not mounted, the script cannot execute at all, making additional validation of /ssd availability unnecessary.

Applied to files:

• update.sh

🔇 Additional comments (1)

update.sh (1)

18-18: Change aligns with PR objectives and is correct.

The relocation of LOGFILE from /var/log/sysupdate.log to /ssd/sysupdate.log directly addresses the goal of reducing unnecessary wear on the uSD card. Based on learnings, the script is deployed to and executed from /ssd/sysupdates/ via cron, so /ssd must be available for the script to run at all, making additional SSD availability validation unnecessary.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5f2e8b7 and 1d6de44.

📒 Files selected for processing (1)

• update.sh (1 hunks)

🔇 Additional comments (1)

update.sh (1)

18-18: Verify symlink creation is handled elsewhere per PR objective #42.

The PR objectives state: "Create a symlink in /var/log pointing to the log on the SSD." However, this update.sh script does not create such a symlink. Clarify whether:

1. The symlink is expected to be created as part of separate system setup/provisioning.
2. Another script or step in this PR creates the symlink.
3. The symlink creation should be added to this script.

If the symlink is a requirement of issue #42, ensure it is created before this script first writes to the log file; otherwise, systems relying on the /var/log/sysupdate.log path may miss logs.