Search results for query: create package

Thank you for clean instructions. I was able to create a jail template with FreeBSD-set-minimal-jail. The result is 210M template vs 374M from base.txz (the template name follows the archive or the package set): % zfs list -r zroot/jail/template | grep 15.0 zroot/jail/template/15.0-RELEASE...

It seems the create-packages-kernel target is doing the job, kernel-toolchain buildkernel required : /usr/src-15.0 # make create-packages-kernel KERNCONF=MYKERNEL ===> Creating FreeBSD-kernel-mykernel-15.0 /usr/src-15.0 % find /usr/obj -name 'FreeBSD-kernel-mykernel*'...

The easiest way to create a package repository for the offline machine is to install from the USB FreeBSD installer stick on the external media a full FreeBSD system, then connect that external device to a machine with internet connection. It's more complicated to make the installer USB a...

> Ha well, the dmesg I was referring to was wrt to loading the drivers, which was how all things started. Yes, exactly, loading the amdgpu driver at boot time. > I don't expect the built to fail because of missing files; though it is important to monitor a built. Be sure you've got the right...

After the second freebsd-update install you're supposed to update your installed ports/packages, that would certainly require network access. Neat little trick to remember; env ABI=FreeBSD:15:amd64 pkg fetch realtek-re-kmod198 would fetch the correct package for 15 regardless of the version...

This information in this wiki is incomplete. Please post the output of pkg -vv | sed -nE -e '/(OSVERSION|ABI|BACKUP)/ p' -e '/^Repositories:/,$ p'

Thanks again! How do I grab the 105 package from the ports main branch? Ahhhh.... please ignore the above. I now have found this at https://wiki.freebsd.org/Ports/QuarterlyBranch

I have the exact same problem after following the RELEASE 15 upgrade instruction here : https://www.freebsd.org/releases/15.0R/installation/#upgrade Here the log : xxx@xxx:~ $ sudo freebsd-update install Password: src component not installed, skipped Creating snapshot of existing boot...

Ok, I performed this upgrade tonight. At least for now it seems to work. The path I followed was: # cat /usr/local/etc/pkg/repos/FreeBSD-base.conf FreeBSD-base: { url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_0", mirror_type: "srv", signature_type: "fingerprints", fingerprints...

Thank you. Yes, I'm using ZFS. Re this method to update - you mean like detailed under "Example: Testing an OS Upgrade" shown here?: https://klarasystems.com/articles/managing-boot-environments/ When I attempted the update last night, like you said, the update created one or two 15.0 BE's but...

Is your system UFS or ZFS based? If ZFS: reboot into the 14.3 boot environment; if you've been following standard practice the BE named "default" is probably the 15.0 so you want the one "before that" (check timestamps). After booting into use the bectl command to create a new BE name it...

# pkg-static install -f FreeBSD-pkg-bootstrap pkg-static: Setting ABI requires setting OSVERSION, guessing the OSVERSION as: 1500000 pkg-static: Warning: Major OS version upgrade detected. Running "pkg bootstrap -f" recommended Updating FreeBSD-ports repository catalogue... pkg-static...

1. I decided to mess with the system. Here's what I did: # nano /usr/local/etc/pkg.conf PKG_DBDIR = "/var/db/pkg"; PKG_CACHEDIR = "/var/cache/pkg"; REPOS_DIR [ "/etc/pkg/", "/usr/local/etc/pkg/repos/", ] ABI = "FreeBSD:15:amd64"; 2. Something started to work: # pkg update pkg: Setting ABI...

Right, I had hoped that you were using ZFS, then it would likely be possible to go back to a Boot Environment (BE) before you pkgbasified your 14.3-RELEASE. As I see it, you may be currrently somewhere in between two OS-s: that seems a problem. Based on your pkg-static output OSVERSION =...

I just went through what has been by far the most difficult upgrade of FreeBSD since the beginning of time (circa 1999, version 3.4). I used to do it via buildworld and pre-mergemaster, so I'm used to a lot of effort to upgrade. My system runs 14.3 with pkgbase (converted from a regular install...

1. Everything is fine here: Convert 14.3 (pkgbasify.lua) - OK. # cat /usr/local/etc/pkg/repos/FreeBSD-base.conf FreeBSD-base: { url: "pkg+https://pkg.FreeBSD.org/${ABI}/base_release_0", mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled...

It's done with ports-mgmt/poudriere. Yes, within Poudriere you can create jails with different versions (and even different architectures). Each of them has a build run with at least a 'latest' ports tree, and for some also a quarterly ports tree. Those builds are spread over a multitude of...

Time to build, time to push, time to address any pkg fallout (failure to build package A may cascade to everything depending on A). So waiting a day or 5 may save you alot of pain. Oh and ZFS saves pain. You can do the upgrade "in place" (using the chroot option) so you can create a ZFS Boot...

Service deployment update: DNS and DHCP are up and running. BIND 9.20 installed from packages in a jail on the primary server, with another named instance installed in a jail on the backup machine. Authoritative zones configured on the primary named instance for my lone forward-lookup domain...

My method of doing so (manually installing) was to provide you a way to get to the rust version you may need on prod server. I'd personally avoid compiling anything on prod server, that's what you have dev/test systems for. With that you can bring tested packages to prod systems (if you can't...