Skip to content

Conversation

lvicoun
Copy link
Contributor

@lvicoun lvicoun commented Oct 2, 2025

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:

@lvicoun lvicoun added the WIP Work in progress. Do not merge! label Oct 2, 2025
@lvicoun lvicoun self-assigned this Oct 2, 2025
@lvicoun lvicoun marked this pull request as draft October 2, 2025 12:33
@lvicoun
Copy link
Contributor Author

lvicoun commented Oct 13, 2025

Copy link
Contributor

@dariavladykina dariavladykina left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, please see some suggestions for this one. Thanks!

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>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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;.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The topic serves as a link to a SBP.
The topic serves as a link to an SBP.

@lvicoun lvicoun marked this pull request as ready for review October 17, 2025 09:27
@lvicoun lvicoun removed the WIP Work in progress. Do not merge! label Oct 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants