Showing headlines posted by dba477
( 1 2 3 4 5 6 ... 31 ) Next »Running Archinstall and Post installation LVs reconfiguration step via remote SSH connection
Remote connection via ssh is significantly more convenient for cut and paste all set of LVs resizing, creating, removing commands along with fstab's updates then typing all of them manually during local Arch Linux Instance setup with more or less complicated LVs updated layout .
Another LVs reconfiguration on ArchLinux as of 03/07/2026
Create root and home LVs as suggested by system during "archinstall" run-time . In general, we follow approach proposed in https://www.dwarmstrong.org/install-lmde-with-custom-lvm-luk... a while ago for LMDE 6. Upon completition drop to root's shell and update default LV's layout as shown below ( just for instance ) .
A FRIGHTENING Episode: systemd, Rust, and KDE Plasma Abandoned | Source Code #7
Too many interesting and relevant issues are touched upon in one short video and in particular the issue related with KaOS decision to transition away from systemd to regain independence and control over the core of its operating system.
Switching location of default libvirt's pool on Debian forky
Google's AI Assistant brief report some times shows up the command following below : If you need to redefine, use virsh pool-define-as --name default --type dir --target /new/path/libvirt/images, some time skips it. However, "Dive deeper in AI mode" always point to this command. Same procedure may be also performed via Virt-manager GUI with option "preferences" => XML editing enabled and manually editing path to default pool and restarting daemon libvirtd.
Setup CachyOS Kernel 6.19.3 on MX25.1 KDE Edition (VENV)
MX Linux consistently tops DistroWatch because it is a highly capable, lightweight, and user-friendly Debian-based system that appeals to a wide range of users.
Build CachyOS Kernel 6.19.2 on Debian forky (VENV)
Start with Pre-installation step $ sudo apt install build-essential bpftool and include /usr/sbin in system $PATH variable.
On Debian forky installation of libdw-dev and build dependencies for libdw-dev steps are required to succeed with build CachyOS 6.19.2 Kernel on top of Debian Testing ( forky native kernel 6.18.9 )
Stress test Deepin 25.010 via build CachyOS Kernel 6.18.7 (VENV)
Because Deepin is Debian-based, we would use the linux-cachyos-deb tool provided by the community to generate compatible .deb files. See for instance https://itsfoss.com/news/cachyos-kernel-builder/ . Notice also that current Deepin's modules names and dependencies appear to be the same as on Debian 13.3 at least during attempt to setup KVM Hypervisor, Libvirtd service and related tools as virt-manager.
Setup Arch Linux KVM Guest via archinstall 3.0.15-2
Following below is an attempt to deploy Arch Linux KVM Guest via archinstall 3.0.15-2. Load Guest via virt-manager into spice console. Pre-install archinstall 3.0.15-2 seems to be needless. However, straight forward run `python -m archinstall` having git clone done and skipping first upgrade didn't work for me .
Bring CachyOS Cosmic DE along with kernel 6.18.2 to Arch Linux Bare Metal Instance
Following below is procedure which allows to install on Arch Linux CachyOS v3 repositories along with pacman fork belongs to CachyOS. Re-sync of v3 repos and core and extra works pretty stable ( u; sudo pacman -Syyu ) - the same commands as described in post after first reboot Arch Instance into CachyOS kernel. I also have to confirm that Re-sync might be randomly required. The hack step below is scp cachyos-rate-mirrors script from remote native CachyOS Instance to the target one.
Bring CachyOS's KDE Plasma 6.5.4 along with kernel 6.18.1 to Arch Linux Bare Metal Instance
Several times schema proposed in https://lxer.com/module/newswire/view/358937/index.html has been run with no issues on bare metal . Re-sync provided by function u() embedded in /.bashrc was tested successfully on bare metal multiple times
Bring CachyOS KVM Hypervisor along with KDE Plasma 6.5.2 and Kernel 6.17.7 to Arch Linux VM
This post is an immediate follow up for Fedora 43 KVM Hypervisor && bring CachyOS KDE Plasma 6.5.1 along with kernel to Arch Linux VM ( https://lxer.com/module/newswire/view/358937/index.html ) It is quite clear that there is a way to automatically start services virtstoraged, virtnetworkd, virtqemud, virtnodedevd on Arch Linux VM , however I was not lucky enough to automate this procedure.
Fedora 43 KVM Hypervisor && bring CachyOS KDE Plasma 6.5.1 along with kernel to Arch Linux VM
Following below is procedure which allows to install on Arch Linux CachyOS v3 repositories along with pacman fork belongs to CachyOS. Proceed as advised in post on Arch Linux KVM Guest deployed via F43/42 KVM Hypervisor . Upgraded Arch Instances have successfully passed via `sudo pacman -Syyu` multiple times during several recent days.
Attempt Arch Linux LVs reconfiguration in Post-installation phase
Following below is an attempt Arch Linux LVs reconfiguration in Post-installation phase. Original LVs layout configuration cannot be changed during archinstall active state. After archinstall finishes up we are going to switch to terminal session via "exit" option rather then reboot .
LMDE 7 LV Setup per Daniel Wayne Armstrong (VENV)
Setup below in general follows guide lines proposed in https://www.dwarmstrong.org/install-lmde-with-custom-lvm-luk... However, we intend to remove swap LV and increase sizes of root and home LVs . Then reboot system and activate zram instead of keeping unreasonably large LV swap on /dev/vda .
Deployment Fedora 43 Cosmic Spin as KVM Guest per Google's Dive deeper in AI Mode guide lines
Tuning Virt-manager you are supposed enable 3D-acceleration and OpenGL to avoid crashing instance setup and successfully install Fedora 43 Cosmic Spin in VENV. The interesting thing is that F43 Cosmic Spin behaves the same way on bare metal and as KVM Guest. No issues for switching between different folders contain wallpapers for Cosmic DE happens in VENV.
Bring Hypland with ML4W Dotfiles functionality to Cosmic Beta DE via setup Dual DE environment on top of CachyOS 082425
We start with deployment of Cosmic Beta DE via CachyOS 082425 Calamares installer. Next step would be deployment Hyprland with ML4W Dotfiles RC 2.9.9.3 as second DE for Cosmic Beta. Notice that Launcher of Cosmic DE provide an option to start ML4W Sidebar App inside Cosmic DE instance . . .
Cosmic Beta DE setup performed via native CashyOS 082825 Calamares installer
Just select Cosmic during initial run of CashyOS 082825 Calamares installer and proceed with installation of Cosmic Beta DE utilizing native CachyOS repositories . Finally make sure that Cosmic Beta has been installed in the same way how we may install KDE Plasma 6.4.5 via original Cachyos ISO as of 08282025 . I have to notice that the only CachyOS provides a straightforward setup of Cosmic Beta DE vs an others clones of Arch Linux, say Garuda Mokka or Manjaro Linux for instance .
Setup Cosmic Beta as dual DE for openSUSE Krypton ( KDE Plasma 6.5 Beta2)
Once again install Hyprland with ML4W Dotfiles DEV 2.9.9.3 along with Cosmic Beta DE. Apparently pre-loading Hyprland virtual instance and performing actions causing trouble for Cosmic creates some shared objects in virtual machine RAM serving in particular the target of normal switching between folders contain desktop wallpapers and afterwards we may work for a while in Cosmice DE instance preserving ability manage Cosmic Desktop with no issues visible at first glance .
Setup dual DE Cosmic Beta and Hyprland with ML4W Dotfiles 2.9.9.3 on top of fedora 43 server ( build as of 09/30/25)
First we setup F43 Server KVM Guest and issue `sudo dnf5 update` then reboot instance and run $ sudo dnf install @cosmic-desktop-environment . Then disable cosmic-greeter.service and enable sddm :- $ sudo systemctl disable cosmic-greeter.service ; $ sudo systemctl enable sddm. Reboot and log into Cosmic Beta DE on top of Fedora 43 Server . . . .
CachyOS: A Derivative Different from the Others
An analysis of CachyOS, the performance-focused Arch derivative that delivers real optimizations through x86-64-v3/v4 packages, the BORE scheduler, and specialized kernels. With 5-20% performance gains and strong gaming support, it proves derivatives can offer genuine innovation beyond simple installers.
