Search results

It is another machine, then both are i386, one the one on VMware is 13-RELEASE, the one on VirtualBox is 13.1-RELEASE.

Very quick test with a i386 Virtualbox Virtual Machine! Exactly the same problem, the system stops when booting kernel exacting at the same point. Now, this loader.efi got problems with i386 like you _martin said.

Thank you martin for your reply. If you say so, a problem in loader.efi, I will maybe try another, older loader.efi. The very old boot1.efi doesn't even boot the machine and the other loader_*.efi same. If I do have a moment to spend, I will also try if this happen also under Virtualbox. BTW...

I can say I never had problems in managing FreeBSD UEFI boot. I converted a lot of machines from old standard BIOS legacy boot to UEFI boot without any glitch and/or problem but this 13.1-RELEASE (i386) virtual install. Google was my friend discovering someone had the same problem long ago...

You are right, it wasn't a problem with ZFS. It was a problem with a proprietary driver not working at all in 13-RELEASE. So I learned how to mount the Zpool in a rescue environment, I used fhe install usb, and mounted the pool and removed the offending driver. Then I learned how to handle...

Absolutely yes, as I said I've been asked to take care of this machine, someone other installed this mess. So, to explain better, I can boot one of that "snapshot", I can't boot the actual 13-release. Do that command you suggested can be run on one of that working "snapshot" with 12-release to...

Thank you Sir, I'm not an expert of ZFS, to me it add a layer of confusion to the system management, and this is the deminstration. I will learn from the document suggested, for now there is some quick command I can run to have back the corrupted (i suppose) "actual" snapshot (if the name is...

I do have to rebuild a machine not originally handled by me. It has a brand new 13-release installed. Tweaking the software for the owner, I saw it has ZFS with a unique Zpool then something happened and now the machine is not bootable anymore. It fails when it need to import the Zpool...

FreeBS 12.1-RELEASE-p9 FreeBSD 12.1-RELEASE-p9 GENERIC i386 After like 24H, the servers started to fetch metadata, maybe it was a server problem that day? % sudo freebsd-update -r 12.2-RELEASE upgrade src component not installed, skipped Looking up update.FreeBSD.org mirrors... 3 mirrors...

% sudo freebsd-update -r RELEASE-12.2 upgrade Password: Looking up update.FreeBSD.org mirrors... 3 mirrors found. Fetching metadata signature for 12.1-RELEASE from update4.freebsd.org... done. Fetching metadata index... done. Inspecting system... done. The following components of FreeBSD seem...

From that very old doc: " -CURRENT should be considered the playground for FreeBSD developers, and for 'adventurous users' who don't mind that their system breaks. These users typically do not require any help to get their systems back into a working state." Not exatly so in this days. -CURRENT...

My question is in the subject. Before going in the long procedure of updating, I will need if really an upgrade compared to installed version exist. How to determine if it exist?

Probably my fault, I maybe wasn't clear enough, then the example in the code window I was wondering it was clear enough. Your command show ALL the outdated packages from updated ports tree, I just need a list of outdated packages in the sense of ports not maintained anymore with relative...

Example: ===>>> Returning to update check of installed ports ===>>> The x11/xsetmode port has been deleted: Deprecatd upstream ===>>> Aborting update How can I find all this outdated packages installed in a system from outdated packages with a simple command? Thank you.

FreeBSD 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC i386 Strange problem configuring ftp/curl fail in config stage and the problem seems related with Clang. Here what happen: ===> curl-7.68.0 depends on executable: gmake - found ===> curl-7.68.0 depends on file...

Thank you to both T-Daemon and Sir Dice. I didn't noticed they were there, my bad! Maybe becouse that files is cluttered with any type of infos and network logs too, so network logs are always very dense considering all those machines are in a domain. Then, like you said, with a simple filter...

Not in my experience: latest Virtualbox (I'm on 6.1.4) works perfectly fine for me with many flavours of BSD clients and emulators/virtualbox-ose-additions install and run just fine.

Thank you. Nothing to do for the past? Pkg do not let traces of installed packages lists?

How can I obtain, if it is possible to obtain it somewhere in some log file, such a list? I explan, I do build and maintain my systems with Portmaster, then it creates packages, so maybe there is a way to obtain such a list? Thank you for any help.

Some programs have routines to discover system binary are modified and they tell the user to restart the program. In my experience it happened many times with Firefox browser, then I do not remember if it was under FreeBSD or some Linux (Ubuntu that's for sure).