[16.0] Fix rungetty.sh to strip non-numeric suffix from console speed parameter#5436
Merged
Conversation
When console= kernel parameter includes format specifiers (e.g., console=ttyS0,115200n8), the script was passing the entire string "115200n8" to agetty. While agetty can parse this format, it's cleaner to extract only the numeric baud rate. Besides getty fails to start on ttyS* and it causes continuous process restart and extra CPU consumption Changes: - Extract and strip non-numeric suffix from speed parameter (e.g., "n8") - Ensure empty or invalid speed values default to 115200 This results in cleaner agetty invocations like: /sbin/agetty -a root -L 115200 ttyS0 vt100 instead of: /sbin/agetty -a root -L 115200n8 ttyS0 vt100 Signed-off-by: Mikhail Malyshev <[email protected]> (cherry picked from commit 39e0fe6)
34 tasks
rene
approved these changes
Nov 24, 2025
This file contains hidden or 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
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.
Description
Backport of #5404
How to test and validate this PR
see original PR
Changelog notes
None
Checklist
I've provided a proper description
I've added the proper documentation
I've tested my PR on amd64 device
I've tested my PR on arm64 device
I've written the test verification instructions
I've set the proper labels to this PR
I've added a reference link to the original PR
PR's title follows the template
I've checked the boxes above, or I've provided a good reason why I didn't
check them.