OpenSUSE Leap 15.5 system release: supports KDE Plasma 5.27 LTS, Xfce 4.18 desktop environment-Nginx-php.cn

Home

Operation and Maintenance

Nginx

OpenSUSE Leap 15.5 system release: supports KDE Plasma 5.27 LTS, Xfce 4.18 desktop environment

王林

Jun 08, 2023 pm 06:21 PM

linuxoperating system

OpenSUSE Leap 15.5 系统发布：支持 KDE Plasma 5.27 LTS、Xfce 4.18 桌面环境

News on June 8th, the openSUSE project today released openSUSE Leap 15.5, which is the latest stable version of the openSUSE variant.

OpenSUSE Leap 15.5 is launched exactly one year after openSUSE Leap 15.4. It is built on the binary package of the SUSE Linux Enterprise 15 SP5 operating system, equipped with the same Linux 5.14 kernel as Leap 15.4, but with the addition of drivers. to provide better hardware support.

The openSUSE Project compared the Linux 5.14 kernel included in openSUSE Leap 15.5 with the upstream Linux 6.0 kernel series, saying that the biggest change is in the GPU driver, supporting AMD Radeon RX 7600, AMD Radeon RX 7900 XT /XTX, new graphics cards such as Intel ARC A380, Intel Arc A750 and Intel Arc A770.

Per NVMe-oF boot specification 1.0, openSUSE Leap 15.5 comes pre-installed with support for installing and booting distributions from NVM Express over Fabrics (NVMe-oF) over TCP transport.

"This allows for flexible creation and orchestration of diskless clients in SAN environments using the latest NVMe-oF technology. This feature requires system UEFI BIOS support with the network and NVMe-oF targets configured. Firmware usage This information is used to boot the kernel. The operating system obtains the configuration information from the firmware and uses it to mount the root file system via NVMe-oF," the openSUSE project said.

In terms of software, openSUSE Leap 15.5 comes with the latest KDE Plasma 5.27 LTS desktop environment series, and the latest Xfce 4.18 desktop environment series. For GNOME desktop fans, this version still uses the GNOME 41 series from openSUSE Leap 15.4.

This version does not feature some of the latest and greatest GNU/Linux technologies, such as openSUSE Tumbleweed. It comes with dnf 4.10.0 package manager, systemd 249.10 init system, Mesa 22.3.5 graphics stack, as well as sudo 1.9.9, AppArmor 3.0.4, Perl 5.26.1, Python 3.6.15 (also supports Python 3.9, 3.10 and 3.11), Ruby 2.5, Go 1.17, Podman 4.4.4, CRI-O 1.22.0 and containerd 1.6.19.

IT Home attaches openSUSE Leap 15.5 official website download (Click this link), which can be used as a live ISO image with pre-installed KDE Plasma, GNOME and Xfce desktop environments, as well as the Rescue version and Install the image offline.

Like previous releases, openSUSE Leap 15.5 supports 64-bit desktops, PowerPC (ppc64le) servers, UEFI ARM 64-bit (AArch64) desktops, laptops, SBCs and servers, and IBM System z and LinuxONE (s390x) servers. For users who want to virtualize openSUSE Leap, a virtual machine image can also be downloaded.

The openSUSE Project also announced this week plans to release another minor version of Leap 15, openSUSE Leap 15.6, which is expected to be available in early June 2024.

The above is the detailed content of OpenSUSE Leap 15.5 system release: supports KDE Plasma 5.27 LTS, Xfce 4.18 desktop environment. For more information, please follow other related articles on the PHP Chinese website!

Statement

This article is reproduced at:51CTO.COM. If there is any infringement, please contact admin@php.cn delete

How to start nginxApr 14, 2025 pm 01:06 PM

Question: How to start Nginx? Answer: Install Nginx Startup Nginx Verification Nginx Is Nginx Started Explore other startup options Automatically start Nginx

How to check whether nginx is startedApr 14, 2025 pm 01:03 PM

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

How to close nginxApr 14, 2025 pm 01:00 PM

To shut down the Nginx service, follow these steps: Determine the installation type: Red Hat/CentOS (systemctl status nginx) or Debian/Ubuntu (service nginx status) Stop the service: Red Hat/CentOS (systemctl stop nginx) or Debian/Ubuntu (service nginx stop) Disable automatic startup (optional): Red Hat/CentOS (systemctl disabled nginx) or Debian/Ubuntu (syst

How to configure nginx in WindowsApr 14, 2025 pm 12:57 PM

How to configure Nginx in Windows? Install Nginx and create a virtual host configuration. Modify the main configuration file and include the virtual host configuration. Start or reload Nginx. Test the configuration and view the website. Selectively enable SSL and configure SSL certificates. Selectively set the firewall to allow port 80 and 443 traffic.

How to solve nginx403 errorApr 14, 2025 pm 12:54 PM

The server does not have permission to access the requested resource, resulting in a nginx 403 error. Solutions include: Check file permissions. Check the .htaccess configuration. Check nginx configuration. Configure SELinux permissions. Check the firewall rules. Troubleshoot other causes such as browser problems, server failures, or other possible errors.

How to start nginx in LinuxApr 14, 2025 pm 12:51 PM

Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

How to check whether nginx is started?Apr 14, 2025 pm 12:48 PM

In Linux, use the following command to check whether Nginx is started: systemctl status nginx judges based on the command output: If "Active: active (running)" is displayed, Nginx is started. If "Active: inactive (dead)" is displayed, Nginx is stopped.

How to solve nginx304 errorApr 14, 2025 pm 12:45 PM

Answer to the question: 304 Not Modified error indicates that the browser has cached the latest resource version of the client request. Solution: 1. Clear the browser cache; 2. Disable the browser cache; 3. Configure Nginx to allow client cache; 4. Check file permissions; 5. Check file hash; 6. Disable CDN or reverse proxy cache; 7. Restart Nginx.

See all articles