02:15:56 i ran through bsdinstall and it put aesni_load="YES" in /boot/loader.conf but it's not listed when i run kldstat why not? 03:31:27 demido, If it is built into the kernel then it is not needed as a module. 03:40:19 ahh rwp there any way to check at runtime if OS has aesni? kldstat obviously isn't a solution since it could be bilt into kernel 03:50:57 demido you would see it in dmesg, so `dmesg | grep aesni` would show what as detected 04:40:50 I'm on my 3rd attempt at trying to use the ports tree in any capacity at all, and I keep getting the same exact error. I've tried the installer-provided ports tree and tried the git method of obtaining an up-to-date tree. "Brotli" keeps having an error "fetch: ... size mismatch: expected 1022. actual 1024." It does this on the very first package I 04:40:51 try to install, no matter which one it is. Only the smallest things like nano are able to install successfully, and even then it took multiple tries and I'm not sure what I did right... 04:51:25 I also notice a bit of an oddity in the error text: "port manually into /usr/ports/distfiles// and try again"... it has two forward slashes... looks weird to me 07:36:53 jtdowney ok so i saw the installer adds aesni_load and cryptodev_load into /boot/loader.conf like i said, and i just checked dmesg and you're right aesni is in there. kldstat shows cryptodev. all god. but then on another identical box, i DON'T put aesni/cryptodev lines in /boot/loader.conf and it has aesni in dmesg, and cryptodev in kldstat. so it 07:36:53 seems they're loaded automatically if supported. hence, why does bsdinstall bother putting them in files explicitly? 09:03:24 Is there perhaps a recommended order to build ports? Or some other trick I'm missing to reduce build errors? 09:04:00 On new installations, I mean 09:23:06 MountainMan1312: poudriere is remommended to build ports en masse 09:23:12 https://github.com/freebsd/poudriere/wiki 09:27:44 mzar: I'm not deploying to a bunch of machines, just one workstation 09:49:38 Hi, I recently updated my FreeBSD VM to 14.2 and now that portsnap doesn't work anymore I installed gitup, but my first run of it gave me this: http://pastie.org/p/6x8EOf9EAUbk7XINWqTcQg 09:49:52 Do I need to do more prep work before running gitup ports? 10:13:15 Feigr: is there any real reason you didn't install git instead and just done git clone https://git.freebsd.org/ports.git /usr/ports ? network seems there for both gitup and repo fetch, maybe disk space, memory or cpu that would justice extra effort? 10:14:08 or maybe network is byte capped 10:33:59 maybe it was simpler too 12:32:55 ketas: short answer is I want my pkg info output to be a short as possible 12:33:36 only that? :p 12:34:02 I have 10GB free on the VM, which I assume would be enough 12:35:27 git indeed did pull (what a pun) lot of deps in 12:35:43 it does indeed 12:36:12 but when did gitup ever work... 12:36:16 trying to keep it minimalist on a VM that is just used for irc and maybe some Inform7 programming 12:36:55 I started reading up after updating on what people use instead of portsnap and gitup was recommended as a minimal alternative 12:37:25 unsure about that error 12:37:45 i mean it should work 12:38:02 this is ports from installer, isn't it? 12:38:18 or no maybe 12:39:17 https://forums.freebsd.org/threads/whats-the-new-alternative-to-portsnap.80489/ 12:39:23 that's what pointed me to gitup 12:41:40 even that mentions errors eg 12:41:46 eh 12:42:27 maybe gitup needs fix 12:46:56 another thread mentioned in passing that gitup is a memory hog, and seeing as this VM currently only has ~100MB free 12:46:59 might be that 13:01:31 for christmas I got a thiknpad t480, which I intended to use to experiment and test things I wouldn't on my main computer 13:01:51 like testing operating systems 13:02:23 so I decided to install freebsd on it, which I at first used only in the console 13:02:59 fast-forward to now where I got x11 to work, audio to work correctly with my headphones, installed i3 and actually made an effort to make it look decent unlike my main computer 13:03:26 and now I feel too invested in it to actually replace it and try another os on it (I intended to tinker with nixos), oops 13:04:15 <|cos|> becrel: you could run nixos in a bhyve, where linux belongs... 13:04:49 <|cos|> becrel: sounds like a success story to me though. the x-mas until now journey. 13:05:10 it's definitely been quite fun :D 13:05:29 I liked building things from the ground up and I like the way freebsd is organised 13:06:06 well not "building" as in using make, building as in installing and setting up every piece I need after starting with only the base os 13:06:31 I don't know what a bhyve is so I'll start reading on that, thanks 13:11:52 since I found bhyve in the handbook, I'll add the docs to the list of things I like about freebsd 13:12:42 I tried running gitup again while looking at top, and it does indeed chew up all available memory and then fails, so it looks like I need more RAM on this VM 13:13:54 although there is maybe one thing that could be more convenient on the doc 13:14:31 since it's distributed in html and pdf format, you need to install a reader before you can read the docs 13:25:25 still the same error in gitup with 1024MB on the VM rather than 512 20:41:21 I upgrade my system to 14.2, I upgrade zpool and I run "sysctl vfs.zfs.bclone_enabled=1". But when I cp a file I see the user quota grows. Any idea why the block cloning doesn't work? 20:47:46 hey there! now that Sendmail has been deprecated in favor of DMA in FreeBSD, is it safe to remove all sendmail_* lines in /etc/rc.conf? 20:58:49 veg: Yes 21:12:07 thanks for the confirmation, vkarlsen 23:22:57 holy hanna, almost an hour to build ports-mgmt/pkg to get version 2.0.5, I hate this craptop 23:23:24 what laptop? 23:23:54 a 2010 Asus 23:34:01 https://bsd-hardware.info/?probe=d5d32f1334 this is old