On Dec 25, 2022, at 15:55, Warner Losh wrote:
> Most likely MK_HYPERV is defaulting to no for aarch64? Or there is a bogus if
> MACHINE_ARCH == "amd64" somewhere.
Well, seems more is missing for aarch64 if devd hyperv is to be enabled:
# grep -r MK_HYPERV /usr/main-src/ | more
Most likely MK_HYPERV is defaulting to no for aarch64? Or there is a bogus
if MACHINE_ARCH == "amd64" somewhere.
Warner
On Sun, Dec 25, 2022, 4:28 PM Mark Millard wrote:
> From the Dec 24 main [so: 14] snaphot for an aarch64 RPi*
> system:
>
> . . .
> Starting devd.
> genet0: link state
From the Dec 24 main [so: 14] snaphot for an aarch64 RPi*
system:
. . .
Starting devd.
genet0: link state changed to UP
sh: /usr/libexec/hyperv/hyperv_vfattach: not found
Starting dhclient.
. . .
This seems to be from /etc/devd/hyperv.conf :
notify 10 {
match "system"
On Sun, Dec 25, 2022, 1:02 AM Alexey Dokuchaev wrote:
> Hi there,
>
> I'm in the process of moving my data from a dying HDD, and just noticed
> something weird. It's an MBR partitioned drive, and there is a FreeBSD
> slice and Fedora LVM in EBR, accessible as
>
Hi there,
I'm in the process of moving my data from a dying HDD, and just noticed
something weird. It's an MBR partitioned drive, and there is a FreeBSD
slice and Fedora LVM in EBR, accessible as
/dev/linux_lvm/fedora-{swap,home,root}.
The problem is that once I mount my old FreeBSD partition,
