From a3f59d7e23af71f57025075c4dd781b4d95ce8d6 Mon Sep 17 00:00:00 2001 From: Ross Burton Date: Mon, 3 Mar 2025 17:20:21 +0000 Subject: Remove all mention of core-image-lsb core-image-lsb was removed in 2019[1], so remove all of the incredibly obsolete references in the documentation. [1] oe-core fb064356af615d67d85b65942103bf943d84d290 (From yocto-docs rev: 9cc8bddc4d3ac0fd2c5dd4ecce582789bb5bd19c) Signed-off-by: Ross Burton Reviewed-by: Quentin Schulz Signed-off-by: Antonin Godard (cherry picked from commit 062445a49919eff117b5478c1fb18d125c1f895c) Signed-off-by: Antonin Godard Signed-off-by: Steve Sakoman --- documentation/dev-manual/customizing-images.rst | 17 ++++++++--------- documentation/dev-manual/qemu.rst | 11 +++++------ documentation/ref-manual/images.rst | 21 --------------------- 3 files changed, 13 insertions(+), 36 deletions(-) diff --git a/documentation/dev-manual/customizing-images.rst b/documentation/dev-manual/customizing-images.rst index 5b18958ade..53cad9c79c 100644 --- a/documentation/dev-manual/customizing-images.rst +++ b/documentation/dev-manual/customizing-images.rst @@ -80,15 +80,14 @@ recipe that are enabled with :term:`IMAGE_FEATURES`. The value of :term:`EXTRA_IMAGE_FEATURES` is added to :term:`IMAGE_FEATURES` within ``meta/conf/bitbake.conf``. -To illustrate how you can use these variables to modify your image, -consider an example that selects the SSH server. The Yocto Project ships -with two SSH servers you can use with your images: Dropbear and OpenSSH. -Dropbear is a minimal SSH server appropriate for resource-constrained -environments, while OpenSSH is a well-known standard SSH server -implementation. By default, the ``core-image-sato`` image is configured -to use Dropbear. The ``core-image-full-cmdline`` and ``core-image-lsb`` -images both include OpenSSH. The ``core-image-minimal`` image does not -contain an SSH server. +To illustrate how you can use these variables to modify your image, consider an +example that selects the SSH server. The Yocto Project ships with two SSH +servers you can use with your images: Dropbear and OpenSSH. Dropbear is a +minimal SSH server appropriate for resource-constrained environments, while +OpenSSH is a well-known standard SSH server implementation. By default, the +``core-image-sato`` image is configured to use Dropbear. The +``core-image-full-cmdline`` image includes OpenSSH. The ``core-image-minimal`` +image does not contain an SSH server. You can customize your image and change these defaults. Edit the :term:`IMAGE_FEATURES` variable in your recipe or use the diff --git a/documentation/dev-manual/qemu.rst b/documentation/dev-manual/qemu.rst index 19f3e40d63..9014d75f4d 100644 --- a/documentation/dev-manual/qemu.rst +++ b/documentation/dev-manual/qemu.rst @@ -280,12 +280,11 @@ present, the toolchain is also automatically used. networking. - SSH servers are available in some QEMU images. The ``core-image-sato`` - QEMU image has a Dropbear secure shell (SSH) server that runs with - the root password disabled. The ``core-image-full-cmdline`` and - ``core-image-lsb`` QEMU images have OpenSSH instead of Dropbear. - Including these SSH servers allow you to use standard ``ssh`` and - ``scp`` commands. The ``core-image-minimal`` QEMU image, however, - contains no SSH server. + QEMU image has a Dropbear secure shell (SSH) server that runs with the + root password disabled. The ``core-image-full-cmdline`` QEMU image has + OpenSSH instead of Dropbear. Including these SSH servers allow you to use + standard ``ssh`` and ``scp`` commands. The ``core-image-minimal`` QEMU + image, however, contains no SSH server. - You can use a provided, user-space NFS server to boot the QEMU session using a local copy of the root filesystem on the host. In diff --git a/documentation/ref-manual/images.rst b/documentation/ref-manual/images.rst index d6bdc92f07..c9d8989261 100644 --- a/documentation/ref-manual/images.rst +++ b/documentation/ref-manual/images.rst @@ -51,27 +51,6 @@ Here is a list of supported recipes: - ``core-image-full-cmdline``: A console-only image with more full-featured Linux system functionality installed. -- ``core-image-lsb``: An image that conforms to the Linux Standard Base - (LSB) specification. This image requires a distribution configuration - that enables LSB compliance (e.g. ``poky-lsb``). If you build - ``core-image-lsb`` without that configuration, the image will not be - LSB-compliant. - -- ``core-image-lsb-dev``: A ``core-image-lsb`` image that is suitable - for development work using the host. The image includes headers and - libraries you can use in a host development environment. This image - requires a distribution configuration that enables LSB compliance - (e.g. ``poky-lsb``). If you build ``core-image-lsb-dev`` without that - configuration, the image will not be LSB-compliant. - -- ``core-image-lsb-sdk``: A ``core-image-lsb`` that includes everything - in the cross-toolchain but also includes development headers and - libraries to form a complete standalone SDK. This image requires a - distribution configuration that enables LSB compliance (e.g. - ``poky-lsb``). If you build ``core-image-lsb-sdk`` without that - configuration, the image will not be LSB-compliant. This image is - suitable for development using the target. - - ``core-image-minimal``: A small image just capable of allowing a device to boot. -- cgit v1.2.3-54-g00ecf