-
Notifications
You must be signed in to change notification settings - Fork 235
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added bootargs variable to KERNEL_ARGS #200
Added bootargs variable to KERNEL_ARGS #200
Conversation
Looks good. Thanks! |
Without this, in some cases devices get a new client ID and IP address assigned after each mender update. Requires the patch at OE4T/meta-tegra#200
Without this, in some cases devices get a new client ID and IP address assigned after each mender update. Requires the patch at OE4T/meta-tegra#200
Thanks @nielsavonds for sharing. I think I should make @madisongh would you prefer separate PRs for warrior and master branches or are you already planning to cherry pick there as well? |
Without this, in some cases devices get a new client ID and IP address assigned after each mender update. Requires the patch at OE4T/meta-tegra#200
@dwalkes I've cherry-picked this to master, warrior, and zeus. |
Without this, in some cases devices get a new client ID and IP address assigned after each mender update. Requires the patch at OE4T/meta-tegra#200
Without this, in some cases devices get a new client ID and IP address assigned after each mender update. Requires the patch at OE4T/meta-tegra#200
Without this, in some cases devices get a new client ID and IP address assigned after each mender update. Requires the patch at OE4T/meta-tegra#200 Signed-off-by: Dan Walkes <danwalkes@trellis-logic.com>
This is required for Mender's 'mender-persist-systemd-machine-id' feature to work properly, but in my opinion it should be added to meta-tegra so anyone using 'bootargs' will be able to use them as expected.