03:17:57 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? 03:22:25 burie: have you read `man release` ? 03:23:25 rtprio: yes and the only command line option is to specify config file not specify target like cdrom or memstick 03:25:30 I don't see any environment variable to specify it 03:26:58 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 03:40:29 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... 04:02:27 it's the makefile; `make cdrom` 04:03:02 what config file are you talking about 04:04:29 does the release.sh not write the files so the makefile then will build the correct thing 04:16:16 ( i haven't done this in a while) 06:29:38 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% / 06:29:43 total size went down? 06:29:50 does zfs autoshrink? 06:42:17 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? 06:43:48 yuripv: I see, no i dont have a snapshot 06:49:33 or it could be files were still opened when you deleted the directory 06:55:56 it was a backup directory with just images and stuff, i doubt it 06:56:05 ill try a reboot later 06:57:26 good morning 07:48:32 after a reboot its still "just" 58gb 07:51:56 here is gpart output https://dumpinen.com/st--HFF-3md 07:52:39 nda0 is the device i use for / 09:12:51 sopparus: what does `zpool get freeing` say? 09:16:09 https://dumpinen.com/HQHgMSVO-6R 09:19:53 ok, and if you aren't using BEs (`bectl list`, using snapshots under the hood), i'm out of ideas :) 09:24:01 https://dumpinen.com/pAQaihjNZ2n 09:24:01 hm 09:24:07 seem like I am? 09:24:39 i can use delete those i assume? 11:02:54 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 11:05:17 might be related to KVM though 11:10:01 as usual, PEBKAC. got it. 13:17:42 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 would reflect config file 14:14:38 How do I get the old motd behavior back? 14:24:24 update_motd="NO" 14:24:42 and symlink /var/run/motd -> /etc/motd 14:49:04 Is there a hard limit on how many IPs (v6) I can assign to a NIC? 14:58:42 CrtxReavr: Not that I've ever seen. 15:03:20 I currently have a script running assigning 65536 aliases. 15:04:35 for fun? 15:55:01 An experiment. . . 16:02:49 Hey. How can I make gdb pretty printers work on FreeBSD? 16:07:35 People worked for years to get Gnu out of the base OS and now you're trying to bring it back! 16:09:15 Do pretty printers work under lldb? 16:12:51 Ah, they do work under lldb. 16:21:01 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? 16:52:29 Quick shout out to all the people making FreeBSD so amazing! Thank you! 16:59:23 nickgaw: that's covered in the handbook; https://docs.freebsd.org/en/books/handbook/book/#updating-upgrading 17:03:25 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? 17:17:55 nickgaw, I think that's one of those questions where if you have to ask, you shoudn't be using -CURRENT. 17:28:48 Understandable and from what it looks like you have to upgrade and build from source. 17:33:04 Is there a section in the manual about roling back from a zfs snapshot or creating one manually? 18:08:38 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 18:08:58 clang is installed as well as bz2-dev and libarchive-dev on debian 12 18:09:24 So what is the cross compiler in this setup? 18:10:13 i don't think I understand why it would decide to cross compile unless you explicity configured for that? 18:11:37 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? 18:13:24 build-essential is installed. 18:13:44 it is with the make.py script. 18:14:06 ok. and i missed what you are building from source, could you repeat that? 18:14:24 I am trying to build Free BSD from source. 18:14:46 Using the directions from the manual on building from source. 18:15:31 ok. i won't tell you that it's impossible on linux, but it's probably easier to do this on a freebsd system. 18:15:58 True I was just wondering why the documentation does not tak about this extra step. 18:16:32 i can only speculate :) 18:17:13 but that is why it is looking for a cross toolchain. which architecture is debian system? 18:17:29 and which do you want to build for? 18:17:32 amd64 and I wish to also build for amd64 18:19:15 super. so you would need an x86_64-unknown-linux hosted toolchain that targets x86_64-unknown-freebsdX.Y 18:19:46 yes 18:19:49 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 18:20:15 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? 18:20:55 q/54 18:25:23 :) 18:31:59 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? 18:48:26 nickgaw: I usually recommend people use the github workflow stuff as a template to figure out what they need to do: https://cgit.freebsd.org/src/tree/.github/workflows/cross-bootstrap-tools.yml 18:48:45 so on ubuntu we're generally bringing in bmake, libarchive-dev, clang and lld; that seems about right, most things will get bootstrapped 18:50:39 Yes but what target and host do I pass to make.py? 18:52:11 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) 18:52:51 For -CURRENT, I'm sticking with beinstall. 20:48:40 [ 5] 0.00-10.06 sec 109 GBytes 92.7 Gbits/sec 0 sender 20:48:45 God I love Jails 21:07:02 pretty decent speed 22:03:31 92Gbits? what is that against the loopback device