Skip to content

Commit

Permalink
SLE installation on x86_64 with Agama installer
Browse files Browse the repository at this point in the history
  • Loading branch information
sounix000 committed Jan 23, 2025
1 parent a2a0700 commit e0ed4a1
Show file tree
Hide file tree
Showing 14 changed files with 214 additions and 0 deletions.
19 changes: 19 additions & 0 deletions DC-SLE-agama-installation-x86-64
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
# This file originates from the project https://github.com/openSUSE/doc-kit
# This file can be edited downstream.

MAIN="assembly.asm.xml"
# Point to the ID of the <structure> of your assembly
ROOTID="article-example"
SRC_DIR="articles"
IMG_SRC_DIR="images"

## Profiling
PROFOS="PRODUCT"
#PROFCONDITION="PRODUCTNUMBER"
#STRUCTID="STRUCTURE-ID"
#PROFARCH="x86_64;zseries;power;aarch64"

DOCBOOK5_RNG_URI="urn:x-suse:rng:v2:geekodoc-flat"

STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns"
FALLBACK_STYLEROOT="/usr/share/xml/docbook/stylesheet/suse-ns"
195 changes: 195 additions & 0 deletions articles/sle-agama-installation-x86-64.asm.xml
Original file line number Diff line number Diff line change
@@ -0,0 +1,195 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!-- This file originates from the project https://github.com/openSUSE/doc-kit -->
<!-- This file can be edited downstream. -->
<!DOCTYPE assembly
[
<!ENTITY % entities SYSTEM "../common/generic-entities.ent">
%entities;
]>
<!-- refers to legacy doc: <add github link to legacy doc piece, if applicable> -->
<!-- point back to this document with a similar comment added to your legacy doc piece -->
<!-- refer to README.md for file and id naming conventions -->
<assembly version="5.2" xml:lang="en"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:trans="http://docbook.org/ns/transclusion"
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns="http://docbook.org/ns/docbook">
<!-- resources section references all topic chunks used in the final article
-->
<!-- R E S O U R C E S -->
<!-- Glue files -->
<resources>
<resource xml:id="_glue-example" href="../glues/glue.xml">
<description>Glue example</description>
</resource>
<resource xml:id="_glue-more-info" href="../glues/glue-more-info.xml">
<description>Glue for more information</description>
</resource>
<resource xml:id="_glue-whats-next" href="../glues/glue-whats-next.xml">
<description>Glue what's next</description>
</resource>
</resources>
<!-- Concept files -->
<resources>
<resource xml:id="_concept-example" href="../concepts/concept.xml">
<description>Concept example</description>
</resource>
</resources>
<!-- Tasks -->
<resources>
<resource xml:id="_task-example" href="../tasks/task.xml">
<description>Task example</description>
</resource>
</resources>
<!-- References -->
<resources>
<resource xml:id="_reference-example" href="../references/reference.xml">
<description>Reference example</description>
</resource>
</resources>
<!-- Legal -->
<resources>
<resource href="../common/legal.xml" xml:id="_legal">
<description>Legal Notice</description>
</resource>
<resource href="../common/license_gfdl1.2.xml" xml:id="_gfdl">
<description>GNU Free Documentation License</description>
</resource>
</resources>
<!-- S T R U C T U R E -->
<structure renderas="article" xml:id="article-example" xml:lang="en">
<merge>
<title>Your title (title style), limit to 55 chars, if possible</title>
<subtitle>Subtitle if necessary</subtitle>
<!-- Create revision history to enable versioning: adjust the placeholder revhistory ID,
for each entry add the date of when the updated article will be published,
list most recent date/entry at the top -->
<!-- Check https://documentation.suse.com/style/current/single-html/docu_styleguide/#sec-revhistory for detailed instructions-->
<revhistory xml:id="rh-USE-ROOT-ID">
<revision><date>YYYY-MM-DD</date>
<revdescription>
<!-- briefly sum up the major changes for the reader-->
<para>
Updated CONTENT, extended CONTENT, removed CONTENT
</para>
</revdescription>
</revision>
<revision><date>YYYY-MM-DD</date>
<revdescription>
<para>
Updated for the initial release of &productname; &productnumber;
</para>
</revdescription>
</revision>
</revhistory>
<!-- TODO: provide a listing of possible and validatable meta entry values. Maybe in our geekodoc repo? -->
<!-- add author's e-mail -->
<meta name="maintainer" content="" its:translate="no"/>
<meta name="architecture">
<phrase>&x86-64;</phrase>
<phrase>&power;</phrase>
</meta>
<!-- enter one or more product names and version -->
<meta name="productname" its:translate="no">
<productname version="X.Y">&productname;</productname>
</meta>
<meta name="title" its:translate="yes">title for SEO and social media, max. 55 chars, keep in sync with article title</meta>
<meta name="description" its:translate="yes">short description, max. 150 chars, no full stop: How to perform task xyz </meta>
<meta name="social-descr" its:translate="yes">ultrashort description for social media, max. 55 chars, no full stop: Perform task xyz</meta>
<!-- suitable categories has to be identical with the category selected in the docserv config -->
<meta name="category" its:translate="no">
<phrase>Systems Management</phrase>
</meta>
<!-- Determines "filter by task" filter value -->
<!-- either add link to list or list of tasks-->
<meta name="task" its:translate="no">
<phrase>Configuration</phrase>
<phrase>Installation</phrase>
</meta>
<meta name="series">Products &amp; Solutions</meta>
<dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager">
<dm:bugtracker>
<dm:url>https://bugzilla.suse.com/enter_bug.cgi</dm:url>
<dm:component>Documentation</dm:component>
<dm:product><!--Bugzilla product string--></dm:product>
<!--
if the assembly applies to multiple products/productversions, use profiling:
<dm:product os="sles" condition="16.0">SUSE Linux Enterprise Server 16.0</dm:product>
<dm:product os="sles" condition="16.1">SUSE Linux Enterprise Server 16.1</dm:product>
-->
<dm:assignee>[email protected]</dm:assignee>
<!-- replace with your BUGZILLA e-mail address, otherwise this does not work-->
</dm:bugtracker>
<dm:translation>yes</dm:translation>
</dm:docmanager>
<abstract>
<variablelist>
<varlistentry>
<term>WHAT?</term>
<listitem>
<para>
Describe your topic in one sentence.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>WHY?</term>
<listitem>
<para>
State the reason why one should read this.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>EFFORT</term>
<listitem>
<para>
What's the effort one has to put in?
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>GOAL</term>
<listitem>
<para>
What's the reader's take-away from this article?
</para>
</listitem>
</varlistentry>
<varlistentry>
<term>REQUIREMENTS</term>
<listitem>
<itemizedlist>
<listitem>
<para>
List the requirements to accomplish the task(s) described below.
</para>
</listitem>
</itemizedlist>
</listitem>
</varlistentry>
</variablelist>
</abstract>
</merge>
<!-- pull in all the topic files you need -->
<!-- pick the appropriate type of include to match your needs -->
<!-- pull in a topic as is -->
<module resourceref="_glue-example" renderas="section"/>
<!-- pull in a topic and switch the title -->
<module resourceref="_concept-example" renderas="section">
<merge>
<title>You are a very special concept now!</title>
</merge>
</module>
<module resourceref="_task-example" renderas="section"/>
<module resourceref="_reference-example" renderas="section"/>
<module resourceref="_glue-more-info" renderas="section"/>
<module resourceref="_glue-whats-next" renderas="section"/>
<module resourceref="_legal"/>
<module resourceref="_gfdl">
<output renderas="appendix"/>
</module>
</structure>
<!-- TODO: second structure! -->
</assembly>
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit e0ed4a1

Please sign in to comment.