Showing headlines posted by dba477

Deepin Desktop Environment (DDE) is a stylish and user-friendly desktop environment originally developed for Deepin Linux, a distribution based on Debian. This environment is known for its sleek and modern design, which focuses on providing a clean and intuitive user experience. DDE is recognized for its polished and visually appealing interface. It incorporates a blur and transparency effect, giving it a distinct look compared to other desktop environments.

Deepin Desktop allows straightforward installation on Arch Linux. Just don't forget to configure network interface during archinstall run. It might be easily installed alongside with Gnome 46 on the same KVM Guest. You may select any available virtual disk layout in meantime. Say allocate "home" lvm for Pycharm projects.

Following below is an attempt to reproduce sample described in https://www.phoronix.com/news/Archinstall-2.8.1-Released in virtual environment . To perform the testing first of all . . . .

In particular case the original set of packages differs from Debian 12.5 and Sparky Linux 2024.05 ones : $ sudo apt install qemu-system libvirt-daemon-system libvirt-clients bridge-utils virt-manager

Procedure which brought me to success looks a bit unusual in comparison with Virt-Manager configuration for any popular Linux Flavor like Manjaro 24.1, SparkyLinux 2024.05, Suse Tumbleweed and etc. Distro KaOS 2024.05 forced me to select emulation of i440FX Chipset, otherwise it hanged right away (case PQ35). During Calamares setup folder /boot/efi was not present among classic options of well known drop down menu. See snapshots bellow

Since we released Vulcan in December 2023 we worked hard to get the next release of Manjaro out there. We call it Wynsdey. This is also our first release which comes with Plasma 6.With Plasma 6, KDE’s technology stack has undergone major upgrades: a transition to the latest version of application framework, Qt, and an improved graphics platform when Wayland is used. These changes are as smooth and unnoticeable to the users as possible.

Virt-manager still appears to be the most powerful tool in regards of deployment and managment of KVM guests. Current version in Debian SID is 1:4.1.0-4. The presence of Web Cockpit Console is also a nice way to manage KVM guest's

Original Virt-manager UEFI option setup should be configured as follows /usr/share/edk2/ovmf/OVMF_CODE_4M.qcow2 . Next step is supposed to be creating /boot/efi fat32 EFI partition during Calamares Installer virtual disk layout configuration.

dnf-plugin-system-upgrade is a plugin for the DNF package manager and is used to upgrade your system to the current release of Fedora Linux. For Fedora Silverblue and Fedora CoreOS, which use rpm-ostree, you may refer to rpm-ostree documentation for details.

Joshua Strobl known for his work on the Budgie desktop and Solus Linux along with Fedora developers Alessandro Astone, Marc Deop i Argemí,Steve Cossette, and Red Hat's Troy Dawson have submitted this change proposal on making Fedora Plasma Workstation the default for next year's Fedora 42 release.

Per https://forum.manjaro.org/t/xz-package-contains-a-vulnerabil... Arch does not directly link openssh to liblzma, and thus this attack vector is not possible. You can confirm this by issuing the following command: $ ldd "$(command -v sshd)" . However, out of an abundance of caution, we advise users to remove the malicious code from their system by upgrading either way. This is because other yet-to-be discovered methods to exploit the backdoor could exist. – Arch Linux - News: The xz package has been backdoored

The main purpose of this post is to demonstrate that the cockpit.service is not required for deploying KVM guests in UEFI mode on AlmaLinux 9.3, which has binary-compatibility with RHEL. Linux bridge for VMs has been installed via nmcli to avoid any involvement of cockpit.service. See for detailis http://lxer.com/module/newswire/view/338368/index.html Everything works on AlmaLinux 9.3 as on openSUSE Tumbleweed. KVM Setup on AlmaLinux 9.(X) follows standard guide lines.

First of all I state, that I am not promoting Kingston's NVME SSD and SATA SSD . Personally, I've been using for a while 2x(WD Blue 500 NVMe SSD) . I've also been testing KDE Plasma 6.0 and Gnome 46 on several boxes equiped with NVMe drives and 32 GB RAM :- When it comes to superior storage technology, NVMe is in a league of its own. Even at a glance, the differences between NVMe and SATA in performance are impressive. The communication drivers and interface between NVMe and SATA are completely different. SATA uses AHCI drivers that are designed for hard disk drives (HDD) with spinning technology while the NVMe driver is specifically designed for SSDs with flash technology. In addition, NVMe is able to take advantage of the PCIe sockets to communicate between the storage interface and system’s CPU for even greater leverage.

Cockpit Client provides a graphical interface to your servers, containers, and virtual machines. Connections are made over SSH, using the SSH configuration of the local user (including aliases, known hosts, key files, hardware tokens, etc).

Porting KDE Plasma 6.0.2 to Manjaro 23.1 was performed by commands $ sudo pacman-mirrors --api --set-branch testing ; $ sudo pacman -Scc ; $ sudo pacman-mirrors --fasttrack 5 ; $ sudo pacman -Syyu . I may confirm the issue mentioned in https://forum.manjaro.org/t/i-tested-kde-6-oh-my-oh-my-you-w... . I've also tested with no problems opening *.webp files via Dolphin on the most recent fedora 40 KDE nightly build. See snapshot . . .

Deployment KVM Guest of openSUSE Tumbleweed was performed via the most recent ISO image dated 03/13/2024. Default disk layout was also updated with LVM Group. Following below are just several reports obtained by different GUI Tools

KDE Plasma 6.0.1 seems to work with no obvious issues on Fedora 40 WKS ( nightly build as of 03/06/24 ) . Looks like requirements for beta staging for Fedora 40 and openSUSE 15.6 are a bit different. Anaconda Blivet GUI on Fedora 40 WKS allows to create any desired disk layout even during deployment WorkStation. Spice console works just fine for L1 and L2 KVM Guests .

This post gives a detailed description of procedure creating network bridge via nmcli commands and virsh CLI. Same procedure was also tested with no issues on openSUSE Leap 15.5. Both tests have been performed in VENV and allow to avoid setup of Cockpit Web Console

A showstopping issue has come to light that has now led to this feature being diverted to Fedora 41 instead. The matter was raised over an important difference in behavior during the storage/disk setup between the existing installer and the new web UI solution.

Actually, what happens right now during deploying KVM Guest via Fedora-Workstation-Live-osb-40-20240301.n.0.x86_64.iso . At the time of writing I clearly saw Anconda Web UI behavior during installation via ISO image pointed above. Awareness of article https://www.phoronix.com/news/Fedora-Web-Installer-F41-Delay explains the reason why Anaconda Web UI was postponed until Fedora 41 and provide some light on why OSB image behaves the way described here in details .