This is an FYI about 8 GiByte RPI4B coverage by 13.2-RELEASE.
(The existing snapshots and such show the issue now --but I'm
noting the 13.2-RELEASE consequences for as things are.)
When sysutils/u-boot-rpi-arm64 and sysutils/u-boot-rpi4 recently
changed to be based on U-Boot 2023.01, the U-Boot pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The second BETA build of the 13.2-RELEASE release cycle is now available.
Installation images are available for:
o 13.2-BETA2 amd64 GENERIC
o 13.2-BETA2 i386 GENERIC
o 13.2-BETA2 powerpc GENERIC
o 13.2-BETA2 powerpc64 GENERIC64
o 13.2-BETA2 powerpc64
Am 15.02.23 um 20:26 schrieb Miroslav Lachman:
On 10/02/2023 22:22, Stefan Esser wrote:
Am 09.02.23 um 20:04 schrieb Miroslav Lachman:
I have FreeBSD 12.4 virtual machine installed inside KVM. This machine has 2
disks. One is 30GB connected as VirtIO vtbd0. There is installed system. The
secon
Paul
This can be fixed with one to two changes . One check the group who owns the
device for the cr/dvd drive . Look at ‘ less /var/run/dmesg.boot ‘ and search
for the entry about the cd / dvd or run ‘camcontrol devlist’ and see what shows
for the cd device . Next run ls -al /dev/the cd drive