05:42:58 is it possible to have the loader check for a keyfile, and only if it doesn't exist ask for a passphrase for a geli encrypted root? not seeing much in the docs on this. 05:43:49 I'm on 13.2-STABLE, and recently `uname -a` doesn't show the kernel build date anymore. Is there a way to get it without looking at filesystem timestamps? 05:57:34 fireglow: what does it show? 05:58:45 rtprio: right now it shows "FreeBSD localhost 13.2-STABLE FreeBSD 13.2-STABLE n255613-6322a6c9daaa TEST amd64" 05:59:40 iirc, that's a reproducible builds thing 06:00:22 WITHOUT_REPRODUCIBLE_BUILD=1 in src.conf might be what you want 06:01:40 RhodiumToad: indeed! Impressive! Thank you! 06:01:46 markmcb: where would the loader check for a keyfile? 06:03:19 i assume that'd have to be defined. ideally anywhere. a removable usb drive, a disk partition, etc. 06:05:29 for example, in linux with luks, i just say "look for UUID 1234". if it exists, try to load /path/key. if that fails, passphrase is the fallback. 06:06:27 judging by some posts i've read, i get the impression this isn't possible 06:13:12 /* XXX TODO: Support loading key files. */ 06:14:03 I think that answers it 06:15:10 indeed :) 06:53:16 reproducible -- that's a new one to me 07:55:38 Hello, since I made a pkg update and now zfs list shows "zroot" using 41.2GB but (same as zpool list) but ncdu or df show only 28.4GB. I really cant find where are the 12.4GB. (freebsd 13.2-p1). 08:03:09 do you have any snapshots? 08:03:22 the pool is a single partition of 48G 08:03:33 I deleted the remaining sanpshots 08:04:07 zfs list -o space 08:06:18 I delete all snapshots except the most recent, which size 18G 08:06:37 I may have misread that this one is needed for boot 08:06:56 Can i safely delete it ? 08:08:37 are you using boot environments? 08:09:40 I dont know, i discovered boot env today ! I deleted the other snapshots with bectl 08:09:56 (you don't need any snapshots in order to boot, but it's common when using boot environments to keep the previous one around as a snapshot in order to revert to it in the event of problems) 08:10:06 I mean, if the default install use boot environment then I use it 08:12:01 And I'm a bit confused about it. bectl list show 2 environement, one called "default" which I presume is actually running and another with a timestamp in its name. 08:12:46 default was creation date is 2223-12-05 ! 08:13:49 sorry for my bad english, I tried to sort this out all day 08:25:28 RhodiumToad: Thank you to point me out to boot environements. Reading the bectl man page wes enlightning. I deleted the remaining boot environements except the one noted "NR" and all is Ok now 08:26:39 except for the "default" creation date being in distant future :) 08:26:58 yes, this is very strange 08:27:09 what's a couple of hundred years between friends 08:27:25 possibly, when the install was done, the system clock was way wrong? 08:28:20 this a virtualbox VM, everything is possible 08:39:33 how do you merge conf files in /usr/local/etc/ if any? 08:41:43 merge them with what? 08:43:15 the general principle for conf files from packages is that things like startup/shutdown scripts are part of the package and those just get updated, 08:44:08 while config files have two versions: a .sample file which belongs to the package, and the actual conf file which belongs to the user, and is created by installing the package _only if it doesn't already exist_ 08:45:43 afaik (unlike /etc) there's no general assumption that package config files can be updated in any sane [semi-]automated way 08:46:35 looks like there aren't many important conf files in /usr/local/etc 08:46:59 well that depends on what packages you have installed :-) 08:50:09 so, when a pkg introduce a new conf file, the .sample is updated, the user conf file is untouched, there won't be stuff like /usr/local/etc/NAME/NAME.conf.new like most Linux distro does 08:58:03 let's say, the package sudo has a conf file in /usr/local/etc/sudoers . when sudo got upgraded AND it introduces new syntax or add/deperecates some options. 08:59:03 how does freebsd handle this by default? or the admin needs to read the changelog and do manual changes? 09:05:09 the admin needs to deal with it 09:07:58 i got it, thanks RhodiumToad 09:55:14 hello 09:56:20 good morning or other timezone-appropriate greeting 10:19:08 good morning RhodiumToad 11:17:22 good