From 63c8e8e530ce26b1594b87368d5900215b30a844 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: 062445a49919eff117b5478c1fb18d125c1f895c) Signed-off-by: Ross Burton Reviewed-by: Quentin Schulz Signed-off-by: Antonin Godard Signed-off-by: Richard Purdie --- documentation/dev-manual/customizing-images.rst | 17 ++++++++--------- documentation/dev-manual/qemu.rst | 11 +++++------ 2 files changed, 13 insertions(+), 15 deletions(-) (limited to 'documentation/dev-manual') diff --git a/documentation/dev-manual/customizing-images.rst b/documentation/dev-manual/customizing-images.rst index 6348259446..6eed9ef56a 100644 --- a/documentation/dev-manual/customizing-images.rst +++ b/documentation/dev-manual/customizing-images.rst @@ -79,15 +79,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 -- cgit v1.2.3-54-g00ecf