dch: From the release build steps how would I specify to use any of the existing or new config in the /src/tree/release/tools directory? It looks like with release.sh I would run release.sh -c /src/tree/release/tools/desired.conf but how would I specify that I want memstick or cdrom target?

burie: have you read `man release` ?

rtprio: yes and the only command line option is to specify config file not specify target like cdrom or memstick

I don't see any environment variable to specify it

rtprio: I see the makefile targets but it seems like those would only be called by doing the cd /usr/src, run buildworld and buildkernel. then cd /usr/src/release, run make memstick steps, but if I did those steps I don't know how I would specify the config file like I could with release.sh

I mean my target right now is a cd so genisoimage would probably work if the generated image were files and not put in a filesystem yet, but I'm not sure what to do for the other formats. I guess I could look at the makefile source...

it's the makefile; `make cdrom`

what config file are you talking about

does the release.sh not write the files so the makefile then will build the correct thing

( i haven't done this in a while)

hi, can someone explain this, with df -h zroot/ROOT/default 193G 188G 4.2G 98% / I then removed a large folder of about 130 gb or so and then did df -h again, zroot/ROOT/default 58G 26G 32G 44% /

total size went down?

does zfs autoshrink?

sopparus: apparently "size" doesn't make much sense in zfs context and is just "used" + "avail", i'm wondering about the "avail" not going up though, do you have snapshots of that fs?

yuripv: I see, no i dont have a snapshot

or it could be files were still opened when you deleted the directory

it was a backup directory with just images and stuff, i doubt it

ill try a reboot later

good morning

after a reboot its still "just" 58gb

here is gpart output dumpinen.com/st--HFF-3md

nda0 is the device i use for /

sopparus: what does `zpool get freeing` say?

ok, and if you aren't using BEs (`bectl list`, using snapshots under the hood), i'm out of ideas :)

hm

seem like I am?

i can use delete those i assume?

I've got a weird one. I ran freebsd-update and upgraded to RELEASE-p8, but `uname -a` still reports running RELEASE-p6, even after reboots

might be related to KVM though

as usual, PEBKAC. got it.

rtprio: I'm talking about config that is custom made from existing config in /usr/src/release/tools/*.conf which seems like the files the example usage is using. Even if release.sh generated the files separately (which I don't know if it does), I don't know if output of a make <target> would reflect config file

How do I get the old motd behavior back?

update_motd="NO"

and symlink /var/run/motd -> /etc/motd

Is there a hard limit on how many IPs (v6) I can assign to a NIC?

CrtxReavr: Not that I've ever seen.

I currently have a script running assigning 65536 aliases.

for fun?

An experiment. . .

Hey. How can I make gdb pretty printers work on FreeBSD?

People worked for years to get Gnu out of the base OS and now you're trying to bring it back!

Do pretty printers work under lldb?

Ah, they do work under lldb.

Hi, How using Free BSD 13.3 on a virtual machine installed locally can I upgrade it using the console to the latest stable version?

Quick shout out to all the people making FreeBSD so amazing! Thank you!

nickgaw: that's covered in the handbook; docs.freebsd.org/en/books/handbook/book/#updating-upgrading

I want to upgrade on this virtual machine to version 15 or the current development version can I do this using binary packages as freebsd-update does not work as 15 is not a supported release?

nickgaw, I think that's one of those questions where if you have to ask, you shoudn't be using -CURRENT.

Understandable and from what it looks like you have to upgrade and build from source.

Is there a section in the manual about roling back from a zfs snapshot or creating one manually?

when building on Linux from source I get the error Could not infer value for $XCC. Either set $XCC or pass --cross-bindir=/cross/compiler/dir/bin

clang is installed as well as bz2-dev and libarchive-dev on debian 12

So what is the cross compiler in this setup?

i don't think I understand why it would decide to cross compile unless you explicity configured for that?

if you don't want cross compiling and you are on debian 12, maybe make sure you "apt install build-essential" and then rerun the configure or cmake step?

build-essential is installed.

it is with the make.py script.

ok. and i missed what you are building from source, could you repeat that?

I am trying to build Free BSD from source.

Using the directions from the manual on building from source.

ok. i won't tell you that it's impossible on linux, but it's probably easier to do this on a freebsd system.

True I was just wondering why the documentation does not tak about this extra step.

i can only speculate :)

but that is why it is looking for a cross toolchain. which architecture is debian system?

and which do you want to build for?

amd64 and I wish to also build for amd64

super. so you would need an x86_64-unknown-linux hosted toolchain that targets x86_64-unknown-freebsdX.Y

yes

based on what you said previosly, X is probably 15, although 14 would probably work. and Y probably can be any number that actually exists

Debian probably doesn't have that toolchain in the repos, so you have to find one that someone already built or build the necessary tools yourself?

q/54

:)

make.py requires a target host and a build host but not sure what I should sI was trying to use make.py to build the latest Free BSD sources on debian linux so what other tools and or targets do I need to set if they both are for amd64?

nickgaw: I usually recommend people use the github workflow stuff as a template to figure out what they need to do: cgit.freebsd.org/src/tree/.github/workflows/cross-bootstrap-tools.yml

so on ubuntu we're generally bringing in bmake, libarchive-dev, clang and lld; that seems about right, most things will get bootstrapped

Yes but what target and host do I pass to make.py?

it should be able to figure out the host itself and you just need to pass TARGET=amd64 TARGET_ARCH=amd64 (if it actually requires them / doesn't derive these from the host as well for cross-builds)

For -CURRENT, I'm sticking with beinstall.

[ 5] 0.00-10.06 sec 109 GBytes 92.7 Gbits/sec 0 sender

God I love Jails

pretty decent speed

92Gbits? what is that against the loopback device