Search results

Ok, that looks really helpful. I copied your FreeBSD-base.conf, and did your pkg add -f but still got the same error of pkg-static: Failed to fetch https://pkg.FreeBSD.org/FreeBSD:15:amd64/base_release_3/data.pkg: Not found As well as a bunch of other failed to find base_release_3. I think I'm...

Erichans yes, I have a 14.3 RELEASE-p7 on a vm that I want to upgrade, via pkgbase, to 15.0 I am doing it as suggested in the handbook, making a boot environment called 15.0-RELEASE, then mounting it on /mnt/upgrade. The results of env DEBUG requested env DEBUG_LEVEL=2 OSVERSION=1500068...

Even though it's dated, this is still useful. Michael Lucas who is great at explaining things so that even dummies like me can get it has some zfs books that are relatively inexpensive. https://www.tiltedwindmillpress.com/product/fmzfs/

env DEBUG_LEVEL=2 ABI=FreeBSD:15:amd64 pkg-static -c /mnt/upgrade upgrade -r FreeBSD-base pkg-static: Setting ABI requires setting OSVERSION, guessing the OSVERSION as: 1500000 DBG(1)[764]> (config) loading repositories in /etc/pkg/ DBG(1)[764]> (config) loading /etc/pkg//FreeBSD.conf...

Right, I think that what happens is that pkgbasify kept the 14.3 3, but then, when I try to modify FreeBSD-base.conf to release_0 I still get the error that it's looking for release_3 and I'm not sure what else to change if making FreeBSD-base.conf point to release_0 isn't having an effect.

I have a VM with 14.3-RELEASE-p7, and thought I'd try to use pkgbasify with it. I followed the handbook instructions of making a bectl image called 15.0, then mounting it at /mnt/upgrade. In the past I'd had problems with it being unable to find keys but had found the solution when SirDice...

Nor had I until recently. I used the quick start from churcher's page https://github.com/churchers/vm-bhyve which has always worked. However, if it gives me issues again, I'll copy your network config and once again thanks for sharing it.

Thanks. After another try, this time, reinstalling bhyve-firmware, it's been working again, this time with the switch, and sign of improvement, I'm able to destroy and recreate the switch. But I'm definitely keeping your config on file for future use, because at present, I feel like it could...

Ok, ignore the last post. It didn't survive a restart and I'm back to it not working.

Ok, I don't feel I can say solved because I'm not sure what happened. For what seemed the umpteenth time, I removed vm-bhyve and removed /vm/.config/system.conf (which had the switch information. I then reinstalled, ran vm init and tried to start a machine. It started and had its IP. Only then...

On both. The dwm tiling window manager, or openbox. If I have to use Wayland, the equivalents, dwl, and labwc. bda65 I used to use spectrwm, and have an ancient page on it, probably 10 years old https://srobb.net/spectrwm.html and I liked it, but wound up with dwm.

hpnothp, No, I didn't get that error when creating a bridge. As I think I mentioned, I've never had to create a bridge for it to work.

Eric A. Borisch, it should be the latest, 1.7..0_1. https://freshports.org shows it as the latest. rootbert ifconfig_re0="inet 192.168.1.145 netmask 255.255.255.0" defaultrouter="192.168.1.1" ifconfig_re0_ipv6="inet6 accept_rtadv" is the relevant network information. I don't have what...

I've been using vm-bhyve for awhile with Linux, Windows, and FreeBSD guests. Probably around a month ago, but I'm not exactly sure, the guest will seem to start, but then if I try to connect, I can't. If I then do vm list, it shows that it has stopped. The log will say (failed to find virtual...

Thanks very much. I'm going to mark this thread as solved, since even though I couldn't test on 14.3, it seems from the comments on github and this thread that it's been fixed.

I can understand the aggravation, but recompiling takes about 30 seconds. To nxjoseph, I should try that patch, but my config.h, along with the move-resize patch, has worked for me for so long, that it's not worth the effort (for me). For what it's worth CyberReaper00, there's also spectrwm...

Hopefully yes. The one that was first out with pkgbasify had the wrong path to keys, so it wouldn't update without the path being fixed. I put up a little page about it, mostly to remind myself, at https://srobb.net/fbsd14_15.html. (The page is pretty use case specific, only covering ZFS...

My Thinkpad, T495, has an Intel card that doesn't get the newer speeds. It has an AC9x6x card. But I also have a Beelink SER5, with an AX200 Intel card, and that one has wireless speeds equal to the speed in Linux.

Yes, that fix seems to work, as I said I already used freebsd-update to update, and just ran pkgbasify.lua, downloading the very latest, and I no longer get that error about non standard pkg REPOS_DIR.

Just a note. The issue is supposedly fixed, I say supposedly because as I said, I wound up using freebsd-update so I can't test. But if you view the link a few posts above they say it's fixed.