Micro's developers guide #549
Merged
Conversation
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
Comment on lines
81
to
82
| <meta name="description" its:translate="yes">How to customize deployment images, kernel modules and kernel drivers | ||
| modules a </meta> |
There was a problem hiding this comment.
Suggested change
| <meta name="description" its:translate="yes">How to customize deployment images, kernel modules and kernel drivers | |
| modules a </meta> | |
| <meta name="description" its:translate="yes">How to customize deployment images, kernel modules and kernel drivers </meta> |
| <term>WHY?</term> | ||
| <listitem> | ||
| <para> | ||
| You want to create an deployment image completely suited to your needs. |
There was a problem hiding this comment.
Suggested change
| You want to create an deployment image completely suited to your needs. | |
| You want to create a deployment image completely suited to your needs. |
| the OEM solution, the file <filename>/etc/os-release</filename> shall be amended. For details | ||
| about the file structure, refer to the <link | ||
| xlink:href="https://documentation.suse.com/sles/16.0/html/SLE-os-identification">&slea; | ||
| OS indetification</link> .</para> |
There was a problem hiding this comment.
Suggested change
| OS indetification</link> .</para> | |
| OS identification</link>.</para> |
| and mitigate risk. However, when &slea; family products are being bundled with a | ||
| system or integrated into a solution by an OEM, the system or solution needs to state the | ||
| OEM status to customers, users and any compliance team. An important reason for this is that the | ||
| terms and conditions of an OEM license agreement usually differ from a common end user |
There was a problem hiding this comment.
Suggested change
| terms and conditions of an OEM license agreement usually differ from a common end user | |
| terms and conditions of an OEM license agreement usually differ from a common end-user |
| </info> | ||
| <para> | ||
| This article explains how to transform the provided raw OS image into a purpose-built system. The | ||
| process may involve installing necessary software from RPMs and applying custom configurations |
There was a problem hiding this comment.
Suggested change
| process may involve installing necessary software from RPMs and applying custom configurations | |
| process may involve installing the necessary software from RPMs and applying custom configurations |
| background on kernel ABI stability to the step-by-step process of building, packaging, signing, and | ||
| deploying your own kernel modules correctly. For details, refer to the <link | ||
| xlink:href="https://documentation.suse.com/en-us/sbp/systems-management/html/SBP-KMP-Manual-SLE12SP2/index.html">Kernel | ||
| Modules Packages Manual</link>. |
There was a problem hiding this comment.
Suggested change
| Modules Packages Manual</link>. | |
| Module Packages Manual</link>. |
| xmlns:xlink="http://www.w3.org/1999/xlink" | ||
| xmlns:trans="http://docbook.org/ns/transclusion"> | ||
| <info> | ||
| <title>Creating custom dirvers</title><!-- can be changed via merge in the assembly --> |
There was a problem hiding this comment.
Suggested change
| <title>Creating custom dirvers</title><!-- can be changed via merge in the assembly --> | |
| <title>Creating custom drivers</title><!-- can be changed via merge in the assembly --> |
| </abstract> | ||
| </info> | ||
| <para> | ||
| Installing third-party hardware drivers into a mission-critical environment can be a source of significant concern, from ensuring compatibility to guaranteeing support. The &suse; SolidDriver Program directly addresses these challenges by creating a standardized framework for our hardware partners. This ensures that kernel drivers are delivered in a uniform, proven, and reliable manner, giving customers the confidence to integrate the latest technology into their &sle;. |
There was a problem hiding this comment.
Suggested change
| Installing third-party hardware drivers into a mission-critical environment can be a source of significant concern, from ensuring compatibility to guaranteeing support. The &suse; SolidDriver Program directly addresses these challenges by creating a standardized framework for our hardware partners. This ensures that kernel drivers are delivered in a uniform, proven, and reliable manner, giving customers the confidence to integrate the latest technology into their &sle;. | |
| Installing third-party hardware drivers in a mission-critical environment can be a source of significant concern, from ensuring compatibility to guaranteeing support. The &suse; SolidDriver Program directly addresses these challenges by creating a standardized framework for our hardware partners. This ensures that kernel drivers are delivered in a uniform, proven, and reliable manner, giving customers the confidence to integrate the latest technology into their &sle;. |
| Installing third-party hardware drivers into a mission-critical environment can be a source of significant concern, from ensuring compatibility to guaranteeing support. The &suse; SolidDriver Program directly addresses these challenges by creating a standardized framework for our hardware partners. This ensures that kernel drivers are delivered in a uniform, proven, and reliable manner, giving customers the confidence to integrate the latest technology into their &sle;. | ||
| </para> | ||
| <para> | ||
| For a detailed description of the &suse; SolidDriver Program refer to the <link |
There was a problem hiding this comment.
Suggested change
| For a detailed description of the &suse; SolidDriver Program refer to the <link | |
| For a detailed description of the &suse; SolidDriver Program, refer to the <link |
| <meta name="maintainer" content="[email protected]" its:translate="no"/> | ||
| <abstract><!-- can be changed via merge in the assembly --> | ||
| <para> | ||
| The topic serves as a link to a SBP. |
There was a problem hiding this comment.
Suggested change
| The topic serves as a link to a SBP. | |
| The topic serves as a link to an SBP. |
| the OEM solution, the file <filename>/etc/os-release</filename> shall be amended. For details | ||
| about the file structure, refer to the <link | ||
| xlink:href="https://documentation.suse.com/sles/16.0/html/SLE-os-identification">&slea; | ||
| OS identification</link> .</para> |
There was a problem hiding this comment.
Suggested change
| OS identification</link> .</para> | |
| OS identification</link>.</para> |
Co-authored-by: Daria Vladykina <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
PR creator: Description
Describe the overall goals of this pull request.
PR creator: Are there any relevant issues/feature requests?
PR reviewer: Checklist for editorial review
Apart from the usual checks, please double-check also the following: