I start with installing Kinoite from booting USB media.
I created /dev/bcache0, which is working with a ssd cache and hdd backing .
Then I rebased to Silverblue. After boot into Silverblue, I find that /dev/bcache0 is not defined.
Is this a normal behaviour? Can I make virtual devices created in one base (Kinoite) also accessible to other bases (Silverblue) ?
Will it be the same if rebased from F34 to Rawhide and vice versa?
ostree://fedora:fedora/rawhide/x86_64/silverblue
Version: Rawhide.20210525.n.0 (2021-05-25T06:08:29Z)
BaseCommit: d230b6a5d4f9d9e14517f78bb556aa0fd1fdc295383911d6dd6a7a60091cebbd
GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
LayeredPackages: gnome-tweaks guestfs-tools hdparm iotop libguestfs-tools
libvirt-client libvirt-daemon-config-network libvirt-daemon-kvm
libvirt-nss python3-libguestfs qemu-img qemu-kvm sg3_utils
smartmontools sway terminator virt-install virt-manager virt-top
virt-viewer
ostree://fedora:fedora/rawhide/x86_64/kinoite
Version: Rawhide.20210525.n.0 (2021-05-25T06:11:36Z)
BaseCommit: 69d4f9bc4bf246814bdb6f2c3a60d0b46db52bc8c8ec31aa8353681c81ee006f
GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
LayeredPackages: gnome-tweaks guestfs-tools hdparm iotop libguestfs-tools
libvirt-client libvirt-daemon-config-network libvirt-daemon-kvm
libvirt-nss python3-libguestfs qemu-img qemu-kvm sg3_utils
smartmontools sway terminator virt-install virt-manager virt-top
virt-viewer
Pinned: yes
ostree://fedora:fedora/rawhide/x86_64/kinoite
Version: Rawhide.20210522.n.1 (2021-05-22T18:26:11Z)
BaseCommit: 8a915542daaff13a2d1d6c328f261080de00a5445988157ad62b6e6f329c339e
GPGSignature: Valid signature by 787EA6AE1147EEE56C40B30CDB4639719867C58F
LayeredPackages: gnome-tweaks guestfs-tools hdparm iotop libguestfs-tools
libvirt-client libvirt-daemon-config-network libvirt-daemon-kvm
libvirt-nss python3-libguestfs qemu-img qemu-kvm sg3_utils
smartmontools sway terminator virt-install virt-manager virt-top
virt-viewer
Pinned: yes