This repository has been archived by the owner on Sep 18, 2020. It is now read-only.
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.
I was spending some time investigating how
update_engine
works, and when firststarting out it took me a little bit to figure out that there were separate
update_engine_client
vsupdate_engine
. Having them both in/usr/sbin
isannoying for bash completion.
This is just a minor "papercut"; I'm mostly using this to test running
through the development/contribution process.
I am assuming nothing tries to find these binaries directly and only uses the
systemd service and/or DBus API; I didn't see any obvious hits in
repo grep update_engine
.Signed-off-by: Colin Walters [email protected]