docs: add complete SBOM, ignore local deployment resources, remove stale third-party references

1 files changed, 6 insertions, 6 deletions

diff --git a/wiki/open-iov.org/index.php?title=Mdev-GPU&oldid=23740.html b/wiki/open-iov.org/index.php?title=Mdev-GPU&oldid=23740.html
index 512ff16..6d9b197 100644
--- a/wiki/open-iov.org/index.php?title=Mdev-GPU&oldid=23740.html
+++ b/wiki/open-iov.org/index.php?title=Mdev-GPU&oldid=23740.html
@@ -36,7 +36,7 @@
 		<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-parser-output"><p>This page makes use of terms that are defined in the <a rel="nofollow" class="external text" href="https://open-iov.org/index.php/Glossary"><i>Open-IOV Glossary</i></a>. If you're curious what a given term means you can check there for a definition.
 </p><p><br />
 </p><p>This page will be used to document the <b>Mdev-GPU API</b> as well as provide an overview of the internals of the Mdev-GPU package.
-</p><p>Mdev-GPU's source code can be found <a rel="nofollow" class="external text" href="https://github.com//Mdev-GPU">here</a>.
+</p><p>Mdev-GPU's source code can be found here.
 </p><p>
 Module docs can be found <a rel="nofollow" class="external text" href="">here</a>.</p><blockquote><p>An absence of critical technical documentation has historically slowed growth and adoption of developer ecosystems for GPU virtualization.
 </p><p>This <a rel="nofollow" class="external text" href="https://creativecommons.org/licenses/by/4.0/">CC-BY-4.0</a> licensed content can either be used with attribution, or used as inspiration for new documentation, created by GPU vendors for public commercial distribution as developer documentation.
@@ -85,17 +85,17 @@ Where possible, this documentation will clearly label dates and versions of obse
 
 <h3><span class="mw-headline" id="Compilation">Compilation</span></h3>
 <p>Compiling Mdev-GPU from source is very simple however it can take a long time to complete (10 minutes for existing sources).
-</p><p>If you'd like to compile Mdev-GPU yourself you can do so by cloning <a rel="nofollow" class="external text" href="https://github.com//Mdev-GPU">the repo</a> and running the following two commands from within the repository directory:
+</p><p>If you'd like to compile Mdev-GPU yourself you can do so by cloning the repo and running the following two commands from within the repository directory:
 </p><p><code>curl -sSL https://get.haskellstack.org/ | sh</code>
 </p><p><code>stack install</code>
 </p><p>These commands will generate all binaries provided by Mdev-GPU under the path <code>~/.local/bin/</code>.
-</p><p>If you would prefer not to wait for the program to compile you can find pre-compiled x86_64 binaries under the <a rel="nofollow" class="external text" href="https://github.com//Mdev-GPU/releases/tag/0.1.0.0">Releases section of the repository on GitHub</a>.
+</p><p>If you would prefer not to wait for the program to compile you can find pre-compiled x86_64 binaries under the Releases section of the repository on GitHub.
 </p>
 <h3><span class="mw-headline" id="Installation">Installation</span></h3>
-<p>The binaries compiled on your local machine by Stack in the <code>~/.local/bin/</code> path or downloaded from <a rel="nofollow" class="external text" href="https://github.com//Mdev-GPU/releases">Releases on GitHub</a> should be copied to <code>/usr/bin/</code>. This can be accomplished both via install script (currently testing in ) or via management layer-agnostic package.
+<p>The binaries compiled on your local machine by Stack in the <code>~/.local/bin/</code> path or downloaded from Releases on GitHub should be copied to <code>/usr/bin/</code>. This can be accomplished both via install script (currently testing in ) or via management layer-agnostic package.
 </p>
 <h3><span class="mw-headline" id="Mdev-GPU_Configuration">Mdev-GPU Configuration</span></h3>
-<p>The Mdev-GPU repository provides Systemd service and example configurations for Mdev-CLI in the <a rel="nofollow" class="external text" href="https://github.com//Mdev-GPU/tree/master/etc">/etc/ folder</a>. On installation the directories &amp; files contained in the repository's /etc/ folder should be copied to the absolute path <code>/etc/</code> on the user's computer.
+<p>The Mdev-GPU repository provides Systemd service and example configurations for Mdev-CLI in the /etc/ folder. On installation the directories &amp; files contained in the repository's /etc/ folder should be copied to the absolute path <code>/etc/</code> on the user's computer.
 </p>
 <h4><span class="mw-headline" id="Systemd">Systemd</span></h4>
 <p>GVM/Mdev-GPU exposes several of it's functions as Systemd services.
@@ -103,7 +103,7 @@ Where possible, this documentation will clearly label dates and versions of obse
 </p>
 <ul><li><b>mdev-post.service</b></li></ul>
 <h5><span class="mw-headline" id="mdev-post.service">mdev-post.service</span></h5>
-<p>As the name would suggest <b><a rel="nofollow" class="external text" href="https://github.com//Mdev-GPU/blob/master/etc/systemd/system/mdev-post.service">mdev-post.service</a></b> posts the GPU(s) in a state where they are ready to be virtualized. When the service is invoked the mdev-cli util registers Mdev callbacks and supported mediated device (Mdev) types with the Mediated Core according to the user's specified configuration at <b><code>/etc/gvm/mdev-gpu/generate-vgpu-types.yaml</code></b>. If you'd like to place your configuration file elsewhere and still have your configuration invoked on boot you can edit the systemd service <a rel="nofollow" class="external text" href="https://github.com//Mdev-GPU/blob/9993fd0781ddddfcca2cb9bee6455ea2c024cc23/etc/systemd/system/mdev-post.service#L10">ExecStart= line</a> to specify an alternative path.
+<p>As the name would suggest <b>mdev-post.service</b> posts the GPU(s) in a state where they are ready to be virtualized. When the service is invoked the mdev-cli util registers Mdev callbacks and supported mediated device (Mdev) types with the Mediated Core according to the user's specified configuration at <b><code>/etc/gvm/mdev-gpu/generate-vgpu-types.yaml</code></b>. If you'd like to place your configuration file elsewhere and still have your configuration invoked on boot you can edit the systemd service ExecStart= line to specify an alternative path.
 </p>
 <h4><span class="mw-headline" id="Mdev-CLI">Mdev-CLI</span></h4>
 <p>Configuration for Mdev-GPU can be found in the path <b><code>/etc/gvm/mdev-gpu/</code></b>. This path will by default contain several vendor-specific folders which may include configuration examples for various devices/architectures as well as the file <code><b>generate-vgpu-types.yaml</b></code> which you can configure to specify your desired Virtual GPU (vGPU) / VFIO-Mdev topologies as they are presented in the sysfsdev mdev_bus path and as seen by tools such as <a rel="nofollow" class="external text" href="https://github.com/mdevctl/mdevctl">mdevctl</a>. Once you have configured the available types your liking you can refresh the supported types registered with the <a rel="nofollow" class="external text" href="https://open-iov.org/index.php/Virtual_IO_Internals#Mediated_Core">Mediated Core</a> by rebooting your machine or reloading the vendor driver kernel module then restarting <b>mdev-post.service</b> or by invoking <b>mdev-cli</b>.