uname: add configurability of sysname and release #2008
Merged
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
With this change, it is possible to configure the kernel to insert
arbitrary strings in the `sysname` and `release` fields of the
struct used in the uname syscall. This allows running user programs
that expect these fields to have specific values (e.g. programs
that expect the sysname to be "Linux", or programs that parse the
release string to infer a Linux kernel version).
To configure the sysname and release fields, a "uname"
configuration tuple is used: this tuple can contain a "sysname"
string and a "release" string, which allow configuring the
respective fields; if a given string is not present in the
configuration, its default value is used (i.e., "Nanos" for the
sysname field, and "5.0-<NANOS_VERSION>" for the release field).
Example snippet of Ops configuration file:
```
"ManifestPassthrough": {
"uname": {
"sysname": "Linux",
"release": "5.0.5"
}
}
```
francescolavra
force-pushed
the
feature/uname
branch
from
6bf580f
to
fea96ad
Compare
|
How would we detect that we are running on nanos if |
|
The default behavior is not changing, i.e. if the user doesn't override the sysname, the kernel will continue to output "Nanos". |
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.
With this change, it is possible to configure the kernel to insert arbitrary strings in the
sysnameandreleasefields of the struct used in the uname syscall. This allows running user programs that expect these fields to have specific values (e.g. programs that expect the sysname to be "Linux", or programs that parse the release string to infer a Linux kernel version).To configure the sysname and release fields, a "uname" configuration tuple is used: this tuple can contain a "sysname" string and a "release" string, which allow configuring the respective fields; if a given string is not present in the configuration, its default value is used (i.e., "Nanos" for the sysname field, and "5.0-<NANOS_VERSION>" for the release field). Example snippet of Ops configuration file: