00:03:05 Yay, 13.4! \o/ 01:25:35 interesting, doas mount directory_which_is_in_fstab fails 02:00:26 Are you looking for sympathy or debugging? If sympathy then, "Well that's just terrible! I feel your pain." If debugging then, "What error message was emitted when it failed?" 02:32:13 sympathy because IDK if I should submit a bug report 02:34:56 oh, interesting, the bug stems from doas mount not taking $PWD into account, so { cd /mnt; doas mount fs/ } fails, but { doas mount /mnt/fs } succeeds 02:35:37 but umount works 02:36:00 oh nevermind, it didn't work either way 03:45:48 Mounts should always be absolute paths. 03:46:14 At least mounts using /etc/fstab should always be absolute paths. So that the string matches what is in the file. 03:48:40 except ZFs mounts which are relative paths 03:53:14 (not that you would usually mount zfs in fstab) 04:09:41 True that zfs is its own special case. 04:27:15 a bit off-topic, but there's a bug inside my 4K monitor and I no longer have warranty. Will it disintegrate/disappear slowly, or should I buy a new 4K, 5K, 6K, or 8K or is there something newer (10K) as long as they don't have *BSD driver issues? 04:27:45 darwin: what do you mean by "a bug"? like literally an insect lives inside your monitor? 04:34:10 yes: two actually. The first one did disintegrate/disappear 04:35:02 fortunately they so far go all the way down to the bottom left where it's not a big issue unless I'm fullscreen graphics-editing at those pixels (not many) 04:50:27 i'd give it a go with compressed air 04:52:00 well if you want to buy a new monitor, i'd say 4k is fine for most desktops, if you have a Mac consider 5k because of the strange way display scaling works on that OS, definitely don't bother with anything higher 05:08:14 On OpenBSD and Linux, installing the "zimg" package includes the libraries (.so and .a), but on FreeBSD it doesn't apparently. Why is that? 05:09:57 Ah, nevermind, I see I had to install "zbar" as well in order to get the libraries. 05:22:27 [00:00:10] [01] [00:00:00] Inspecting devel/popt | popt-1.19_1: determining shlib requirements 05:22:37 this is new, what does 'determining shlib requirements' mean? 06:10:27 kevans: sorry for the delay, (CEST tz here, I was sleeping) , yes I performed 3 freebsd-update install 08:25:24 oh no 08:25:26 Error: (2474) _mktemp:_mktemp:260: mkstemp failed on /poudriere/data/logs/bulk/main-lf/2024-09-17_07h54m48s/.write_atomic-.poudriere.snap_loadavg.HQa1OkM8: No space left on device 08:25:34 never saw this before, i wonder what changed 08:31:36 lw: that error makes me recall a rust build problem I had 08:32:31 there was an adjustment in poudriere.conf for tmp space for the build process to set 08:33:07 i already have USE_TMPFS=no 08:33:14 (in poudriere.conf) 08:34:05 oh wait i found the problem 08:34:08 [8!] daphne /usr/local/etc# df -h / 08:34:08 Filesystem Size Used Avail Capacity Mounted on 08:34:09 zroot/ROOT/default 5.5G 5.5G 0B 100% / 08:34:12 (as I had several problem in building rust on my poudriere vm, i decided to use poudriere-devel and fetch as many pkg as I can in dependancies, (with rust being one of this dependancy) 08:34:49 somehow /src/obj is 221GB 10:00:31 reset 10:00:46 i refuse 10:04:59 does anyone know which pkg is the 'dns' package for python 311 ? 10:05:11 I try import dns and it says the module can't be found 10:09:49 last1: py311-dnspython 11:04:01 holy shit my ports build actually finished 11:04:37 let's see if upgrading works 13:25:26 sidh: how much RAM on this guy? 13:52:50 kevans: 1GB RAM for the first, and 2 GB RAM for the second (proxmox VM , few services) 13:55:23 sidh: ZFS or UFS? 13:56:17 an associate noted they've seen similar failures in low RAM environments where the update ends up only sporadically deployed 13:56:30 dch: oh, hey 13:56:48 kevans: sup 13:57:29 dch: sidh just above is the one with that very partially updated system I mentioned 13:57:48 sidh: heya 13:58:14 yes, so I have seen this a couple of times on my mini-VMs (they act as ssh jump hosts, and run a lightweight auth services) 13:58:33 typically 1G RAM, and sometimes swap gets a little high 13:59:30 sidh: my speculation is that theres not enough ram during unpack or fetch, so box just runs out of memory and stuff randomly gets OOM killed 13:59:57 I don't see this every time, but I've seen it enough to know to run `freebsd-update IDS` *before* the reboot. 14:05:35 dch: thanks for the tips, will add that IDS to the routine 14:06:43 but here the question remains if the problem is not due to the freebsd-update -b -d procedure (as usually, we create a bootenv, and upgrade it once mounted) 14:07:51 in the first context of the bug, it is from a jail context, so with my BE, I'm in the same context 14:11:21 oh, someone marked it closed 14:14:25 kevans: really am sorry for my weird inconsistent system 14:16:27 sidh: we all have our snowflakes 14:16:47 I don't think the memory constraint would be any different if you do freebsd-update into a jail 14:17:00 btw I tried https://rustdate.over-yonder.net/download.html last week 14:17:05 its very nice, very fast. 14:17:15 also very new and you may find different/new/other bugs 14:17:27 freebsd-update written in rust, so no shell forking. 14:22:10 I read about the brainstorming in including rust in the basesystem, I have to admit that my first reaction was FEAR (several poudriere bulks that failed during rust after 12 hours+ building time) , but rust apps are known for their efficiancy, so I am quite wondering about it 18:51:54 https://dpaste.org/64zNQ 18:52:00 ^ weird right ? 18:54:16 jb1277976: Not really. afaik, pkg info shows info of *installed* packages. 18:54:32 aw 18:54:39 you can tell i'm still a noob 18:56:01 Everyone was, once. Contrary to belief, even the hardest bofh wasn't born with the knowledge. :) 19:27:54 yep, every bofh was once a pfy :P 20:34:31 Did you find out the differences between pkg-search(8) and pkg-info(8), then? ;) 20:42:22 I have an internal process use for symmetric encryption. 20:42:24 Previously I have used GnuPG v1 but GnuPG v2 makes non-interactive use if not impossible then so difficult that I haven't been able to accomplish it safely and securely yet. 20:42:28 I am contemplating using openssl encryption. Is there wisdom from the community that they might want to hint to me? 20:45:59 too many variables / what are you encrypting? 20:47:12 In this particular case it is part of server provisioning and I am encrypting a secrets.tar.gz of information targeted to a server. ssh host keys. https certs. 20:48:16 The entire process is rather involved but this is information which shouldn't be publicly available but I must transport from the secrets vault to the server getting provisioned. 20:49:15 you don't generate ssh host keys on the host itself? 20:49:25 anyway openssl could probably be fine for this 20:49:42 Can't. Let's take Github as an example. Let's say that every time you did a clone or push that it informed you that the host keys had changed? 20:50:42 When a new system is spun up to perform a role it must use the same role keys that have already been distributed by TOFU. 20:54:01 sure, ok 20:56:08 Handling secrets vault information in a secure way is one of those tedious details that makes provisioning, well, tedious! 20:56:12 Non-secrets details have a dozen competing infrastructures for provisioning. Such as puppet, chef, salt, ansible, and so on. 20:56:18 I wrote my own so of course I use my own. But they all fill the same conceptual block in the block diagram. 20:59:39 In GnuPG v2 it appears they decided to embrace interactive use only. gpg starts up a persistent gpg-agent to handle the passphrase interaction. Which if interactive would open a GUI dialog and interact with the user. I don't want that in batch mode operation acting automatically in a root privilege process. Avoiding that seems impossible. Working securely with that behavior will be tricky. 21:00:33 Seems the only answer is to abandon that tool. Therefore I must use another. 21:02:44 Humor found in gpg(1) man page "--no-use-agent This is dummy option. gpg2 always requires the agent." 21:26:35 in my case i use puppet with hiera, and with hiera i can use eyaml 21:27:09 root::salt: ENC[PKCS7,MIIBmQYJKoZIhvcNAQc...]