1. See https://github.com/adafruit/Raspberry-Pi-Installer-Scripts/iss… #93
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ntpd started from 'systemctl' (via dhcpcd hook) can not follow symlink
from /etc/resolv.conf to /tmp/dhcpcd.resolv.conf. For now should remain
in /etc/resolv.conf (hard coded).
stat64("/etc/resolv.conf", 0xbea7af80) = -1 ENOENT (No such file or
directory)
2. Never fsck on any volumne. Linux runs a fsck every 6 month even on
ro-volumnes. Any fs corruption makes fsck stall during bootup and
requires user to confirm to continue.
3. Disable viminfo to stop vim from complaining about ~/.viminfo not
writeable.
|
Oops. bug is easier fixed in /lib/systemd/system/ntp.services with PrivateTmp=false |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ntpd started from 'systemctl' (via dhcpcd hook) can not follow symlink
from /etc/resolv.conf to /tmp/dhcpcd.resolv.conf. For now should remain
in /etc/resolv.conf (hard coded).
stat64("/etc/resolv.conf", 0xbea7af80) = -1 ENOENT (No such file or directory)
Never fsck on any volume. Linux runs a fsck every 6 month even on
ro volumes. Any fs corruption makes fsck stall during boot-up and
requires user to confirm to continue.
Disable viminfo to stop vim from complaining about ~/.viminfo not
writeable.