Showing headlines posted by dba477

This option of Pycharm 2023.3 setup works for me with no issues so far. I am not quite sure that under any circumstances I am supposed to work via flatpak/flathub .

Pyenv is a tool for managing multiple Python versions. Once pyenv is installed you can easily switch between one project that uses Python 3.12 and a system-wide default Python 3.11. Same approach works fine on openSUSE Tumbleweed, SparkyLinux 7.2, SparkyLinux 2024.1

Pyenv is a tool for managing multiple Python versions. Once pyenv is installed you can easily switch between one project that uses Python 3.12 and a system-wide default Python 3.11, without any additional doubt. Same schema would work on SparkyLinux 2024.1

Following post is a compilation from several sources, which looked unexpectedly complicated due to I was unable to find out the way of installation like on the known Linux flavors (Fedora,Debian,Ubuntu). Actually "pyenv install 3.1X" appears to be the build via original python's tar ball. Before you can use a specific Python version, you need to install and configure pyenv.

On both Sparky releases (stable 7.2 and Seven-Sisters) kernel 6.7.2 may be installed via Synaptic Manager. Command "$ sudo apt install kde-standard" allows to switch from X11 to Wayland via relogin to Sparky instance. Just one more option comes up on SDDM login screen. Libvirt version 10.0 may be tested on SparkyLinux1024.1

Originally setup Cockpit Web Console and deploying KVM Guest were done under the most recent kernel 6.7.0 installed via Manjaro Settings Manager in VENV. Afterwards same schema was reproduced on bare metal with obvious changes related with manual creating EFI partion fat32 512 MB been mounted on folder /boot/efi and "btrfs" been used for "/" root partition

Deployments below have been performed to make sure that Calamares Installer has no any longer issues with KDE Plasma 6.0 RC1 on top of Fedora Rawhide Server. Debian Network Installer was verified with the same purpose

VM installed as KVM Guest via Fedora-Server-netinst-x86_64-Rawhide-20240103.n.0.iso ( 16 GB , 8 vcpu ) with KDE Plasma Workspaces 5.91.0 . Fedora Rawhide Server is running 6.7.0-rc8 kernel. Looks like Fedora Server Rawhide is ready for KDE Plasma 6.0 .

Look for YAST2 via Gnome 45.2 search capabilities and load it up, rather then run $ sudo yast2 via CLI. Goto Software=>View=>Pattern. At this point the sequence of steps maybe the same as described in http://lxer.com/module/newswire/view/336041/index.html either you may deploy KVM (Xen) Hypervisor and tools in graphical mode .

There are several desktop environments and window managers available for Manjaro, each with their own unique style, interface, and features. Furthermore, it is possible to install multiple environments if desired, which can be selected at the login screen at any time. Users are not restricted to whatever comes pre-installed with a particular flavour of Manjaro.

By default during install openSUSE Tumbleweed with KDE Desktop installer selects X11 as windowing system. After logging into KDE ( on openSUSE ) load Yast Control Center and proceed as shown on snapshots below

OpenSUSE Tumbleweed Installer in expert mode creates disk layout with volumes group VG_SUSE. At first glance, has practically the same possibilities as demonstrates Anaconda (Blivet-GUI) and more over creates subfolders under "/" root as BTRFS subvolumes

Original post has been written with intend to make gdm3 default display manager and it works with no issues at all. However, it appears that Lightdm could replace gdm3 as Default DM, following below is a brief description of sequence of steps to achieve this goal. First of all $ sudo dpkg-reconfigure gdm3 and choose default DM to be Lightdm . . .

Following below is an attempt to reproduce Fedora's style of installation Deepin Desktop on Server's instance. Due to known issues with DDE on F39's server, this procedure has been done on Ubuntu 22.04 (LTS) Server .

FreeBSD tar (also BSD tar) has become the default tar on most Berkeley Software Distribution-based operating systems including Mac OS X. The core functionality is available as libarchive for inclusion in other applications. This implementation automatically detects the format of the file and can extract from tar, pax, cpio, zip, rar, ar, xar, rpm and ISO 9660 cdrom images. It also comes with a functionally equivalent cpio command-line interface.

Please be advised, that in particular case install rpmextract results presence bsdtar on the system and extraction of rpms is supported via CLI $ bsdtar -xf *.rpm . The rest of deployment procedure keeps to be the same as on previous versions of Manjaro linux. So the commands which bring you to successful deployment of Windows 11 KVM Guest should be . .

Mentioned procedure on Fedora 39 Server requires only verification of presence packages edk2-ovmf swtpm swtpm-tools on the system. You are not supposed to experience any problems during deployment Win11 KVM in security mode (virt-manager's setup)

We start as usual ( no convertion is required on openSUSE ) $ sudo rpm -iv virtio-win-0.1.229-1.noarch.rpm . Second step looks a bit strange. I would expect this dependencies to be resolved automatically up on install of package swtpm

Setup Cockpit Web Console on openSUSE 15.5 Leap requires activation an additional repo mentioned first in the post, which by some reasons wasn't activated during standard installation procedure by default. Now proceed as follows . . .

Debian network installer appears to be extremely stable and flexible no matter of version Debian GNU/Linux to be deployed in particular case. I also have to admit that problem with LVM confiruration still persist for the most recent versions of Calamares Installer (3.2.6X), affecting ability for flexible LVM configurations of such distros as SparkyLinux 2023.10 and Manjaro Linux 23.0/5.