00:19:21 i'm getting errors about zfs when i boot up. its before the acer screen comes on something about the zpool. yet when i boot into freebsd everything is fine. zpool list and zpool status show everything like it should 00:19:44 jb1277976: if you don't have time to read the error, trying taking a video on a mobile phone (if you have one) 00:20:06 ok let me do it now.. where do i upload it ? 00:20:18 well, i thought you could just watch it on your phone and type the message out :-) 00:20:32 oh yea that makes sense. i will brb 00:20:40 although in general, the first thing i'd do with loader/zfs issues is to update to the latest loader, if you didn't already (assuming you're on EFI) 00:25:21 Hey, anyone using freebsd collectd logparser plugin? 00:25:30 I need help understanding the pattern regex for collectd logparser plugin. Does anyone can point me to a config sample that reads journalctl messages (or any kind of unit / log) 00:25:46 I have found this example in the man page, using var/log/syslog, but cannot make it work. Any clue/doc indication? 00:26:24 i don't know about collectd specifically, but freebsd doesn't have journald (or systemd) so you won't get anywhere with that. /var/log/syslog doesn't exist by default, but you could create it in /etc/syslog.conf 00:27:09 (look at the commented example for 'all.log' - that's basically what /var/log/syslog.log usually is) 00:27:40 unixwitch: BTW, I dont care about what log file it will read. I am trying to make it work - even if it is a ascii file to parse. 00:27:53 well, try /var/log/messages to start since that exists by default 00:28:04 it is in the usual syslog format which should be supported by any log collector 00:29:19 unixwitch: I did. It captures the portions of the logs I want and form a collectd UDP packet and send to influx-db server. I capture the packet using wireshark and the collectd-message is somehow 'malformed' 00:30:57 zfs: i/o error - all blocks cpioes unavaialble 00:30:57 zfs: can't read MOS of pool zroot 00:30:57 BIOS 634kB/185143kb avaiable memory 00:30:59 unixwitch: saddly, the collectd documentation about log_parser_function is very limited. And I dont know where else to look/search. 00:31:16 ah, i have no idea about that part of it then, sorry 00:31:36 copies* 00:31:46 jb1277976: that's weird. have you run a scrub on the pool just in case? it's weird it produced that error but still booted fine though 00:31:56 let me do it right now 00:32:30 unixwitch its scrubbing right now 00:40:40 00:40:58 oops 00:43:04 so i am having a problem upgrading a jail from 13.2-RELEASE to 13.2-RELEASE-p9. When I run the upgrade from the jailhost (running -p9) it runs and then the jail craters. 00:44:23 ld-elf.so.1: /lib/libc.so.7: Unsupported relocation type 37 in non-PLT relocations 00:45:27 if i run the fetch install from within the jail it fails with 00:45:28 Installing updates...chflags: ///lib/libc.so.7: Operation not permitted 00:45:29 chflags: ///sbin/init: Operation not permitted 00:46:07 and 3 other chflags errors 00:46:54 any thoughts as to what is going on? 00:50:45 there's a sysctl controlling chflags in jail 00:51:23 man jail, /allow.chflags 01:04:07 hmm, sctp_recvmsg(3) says the 'from' argument is restrict, but it's not in the actual prototype. i wonder if that's a bug in the manpage or the header 01:10:34 yuripv: set allow.chflags=1 in /etc/jail.conf and restarted the jail. Do I need to reboot the host? 01:11:10 also thanks. 01:13:19 I will put my head in the man page next year. for now I am gonna leave it at 13.2. 01:14:25 happy new year all. 01:19:43 kevans: so it is possible i am downloading images from the current directory on freebsd.org that are NOT aligned to checksums? 01:20:45 are the checksums not the same as the files you downloaded 01:21:08 ? 01:21:33 i was NOT checking before i did the install 01:21:46 but now the installs of CURRENT are blowing up 01:21:52 i am trying ta virtualbox image now.. 01:22:04 i can't say i've checked maybe but once or twice in the 20 years i've been using freebsd 01:22:28 it's possible it could be broken; verify the checksum. or download the previous week's image 01:22:46 did that.. i did 23DEC2023 and 16DEC2023 same result :)O 01:23:05 blow up how? 01:24:27 i install the whole thing, says checksum are not correct.. restarts install 01:24:46 is that from the image or from the network 01:25:02 both install local to my machine and over the network.. same result 01:25:18 but looks like the virtualbox image works.. i am logged in 01:25:30 but i am now going to be stubborn and try to do an install WITHOUT hte virtualbox image 01:25:39 well, which exact image did you download; i can try it now 01:26:23 FreeBSD-15.0-CURRENT-amd64-20231216-ca39f23347e1-266973-bootonly.iso 01:26:33 FreeBSD-15.0-CURRENT-amd64-20231223-dac33a65b965-267058-bootonly.iso 01:26:40 FreeBSD-15.0-CURRENT-amd64-20231228-fb03f7f8e30d-267242-disc1.iso 01:27:11 https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/ 01:27:13 Title: Index of /snapshots/amd64/amd64/ISO-IMAGES/15.0/ 01:27:19 that is where i got them from 01:29:42 hrm, hard to install with this broken down arrow key 01:30:52 https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/FreeBSD-15.0-CURRENT-amd64-20231216-ca39f23347e1-266973-bootonly.iso 01:31:03 i got it 01:31:06 okay 01:32:01 Did anyone see my error? It’s an error before FreeBSD ever loads 01:32:47 Aw unixwitch I forgot you told me to scrub. Let me check on it 01:33:03 voy4g3r2: ok, ufs auto, main server, ... 01:33:13 fetching distribution 01:33:13 ufs auto and zfs 01:33:15 tried both 01:33:28 voy4g3r2: could you just install 14.0 and upgrade to 15.0 from source? that might be easier 01:33:46 easier, but might take longer 01:33:55 depends how long it takes to fix this :-) 01:33:55 voy4g3r2: does it die on base.txz or what 01:34:28 after a full install, yes it dies on base.txz 01:34:34 just says.. checksum bad.. wanna restart? 01:34:34 16% ... 50% 01:34:46 i get through the WHOLE install of all packages, ports, src, base 01:34:57 it does the checksum check thingie and that is when it dies 01:35:11 and even when you install from th cdrom using disc1 iso 01:35:19 it still chceksum errors 01:35:20 unixwitch: that is possible.. but never did that before 01:35:21 right? 01:35:25 yes it does 01:36:05 another question for the 13.2 to 14.0 upgrade - in the process of upgrading my jails I was no longer able to get a console on the jails after upgrading to 14.0. This tells why, and also how I fixed it https://pastebin.ubuntu.com/p/5dhDcfFXrj/ 01:36:06 Title: Ubuntu Pastebin 01:36:15 i just picked the default sets base, kern, kern-dbg, lib32 01:36:26 and it probably worked.. 01:36:30 because that is just my luck 01:36:45 has something changed in the way login is done? I am thinking maybe some config was made to the host os, that was not done in the jail configuration 01:36:58 BarnabasDK: yes, opie was removed from freebsd, so you'd need to update pam configs to match 01:36:58 voy4g3r2: 60% overall progress 01:37:21 yup par the course for me also 01:37:30 BarnabasDK: that is, remove opie* lines 01:38:05 77% 01:39:37 BarnabasDK: how did you upgrade the jails? either freebsd-update or etcupdate should prompt you to update /etc/pam.d/* which contain pam_opie.so (which was removed) 01:39:56 voy4g3r2: The checksum for base.txz does not match. 01:40:31 someone might have broken something-- anything on the -current mailing list? 01:40:32 bingo 01:40:41 i did not get that far 01:40:52 i was hosting some people, the wife preferred i speak with guest 01:41:02 that was the last thing i did but now i am being asked to help clean up.. ill bbl 01:41:16 rtprio: i take it the mailing list reference is osmewher eon freebsd.org? i can look 01:41:33 https://lists.freebsd.org/archives/freebsd-current/ 01:41:35 Title: freebsd-current⊙Fo 01:42:05 thank you, i will dive in a little later, at least i am not crazy 01:42:16 i was getting my b*** busted for using netatalk but it was not that.. 01:42:17 :) 01:43:37 unixwitch, "sudo ezjail-admin update -U -s 13.2-RELEASE" 01:43:46 ah, no idea about ezjail 01:44:24 seems to use the freebsd-update utility - at least thats how the output looks 01:45:30 anyways - copied in the needed libs in order to be able to get a console and update the packagtes in the jails - but I would like to configure the PAM modules to behave in the jails like the host OS 01:45:47 i wonder if freebsd-update doesn't catch that one for some reason... although i'd expect more complaints if so since it breaks login for everyone 01:47:14 so - I guess there must be a set of config files in the host os - that can be copied to the jail config ditto? 01:47:28 BarnabasDK: were you using opie, by chance? (it was removed) 01:47:30 just edit /etc/pam.d/* and remove any reference to pam_opie.so 01:47:38 heh 01:47:49 or, if you really want to use opie, install it from ports (but you might need to remove it first so you can log in to do that...) 01:48:20 i suppose you could copy /etc/pam.d/* from the host, but that would overwrite any local modifications in the jail 01:48:54 check - I will look over the config files - thx for the help 01:51:08 and no - I would rather see the jails behave in the same manner as the host os 01:54:34 the most optimistic thing i've done in years: + 2 Dec 28 Qualcomm Support ( 25K) Thank you for contacting us 02:03:35 rtprio: i am not seeing anything on mailing list 02:03:49 i do notice that MOST people are just upgrading from 14.0 -> 15.0 CURRENT and rarely run the installers... 02:04:12 there's no real point using the installer since you'll be compiling from source to update current anyway 02:04:32 although, there *is* a point in reporting bugs in the installer, since that's partly why the snapshots exist, so i would drop a mail to -current about this 02:04:46 unixwitch: true and that is exactly right 02:05:19 lets see how i can subscribe to this without having to download all the dang emails :) 02:05:38 if you don't want to subscribe to the list you could file a PR at https://bugs.freebsd.org instead 02:05:39 Title: FreeBSD Bugzilla Main Page 02:05:57 "bad checksum" is usually a bad download/image transfer 02:06:19 yuripv: but two different people reproduced it in this case, so probably not 02:06:23 yuripv: i thought that, downlaoded to a file server, locally and rtprio confirmed same issue 02:06:24 unless it's exceptionally bad luck 02:06:32 any links? 02:06:43 to the isos used? 02:06:49 no, to reports 02:06:58 scroll up to rtprio's comment 02:07:20 no reports from installer.. not sure how to get them.. this is all new teroritory for me 02:07:25 i could rerun it and try to pull 02:08:12 same iso? 02:08:31 yup 02:08:57 i mean you and rtprio, same issue using same iso (which one?)? 02:09:23 rtprio: could you confirm which one you used? i shared 3 :) 02:09:30 i am retrying with this one: https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/FreeBSD-15.0-CURRENT-amd64-20231216-ca39f23347e1-266973-bootonly.iso 02:09:54 bootonly doesn't have any installation distributions 02:10:35 okay.. i can try with disc1 then: https://download.freebsd.org/snapshots/amd64/amd64/ISO-IMAGES/15.0/FreeBSD-15.0-CURRENT-amd64-20231216-ca39f23347e1-266973-disc1.iso 02:10:47 what is meant by installation distributions? 02:10:56 i figure.. if result is same for 3 different iso images.. does it matter? 02:10:58 meaning it doesn't include base.txz, it has to download it 02:11:12 ah okay.. let me try with disc1 then which DOES have it, thanks for clarification 02:12:24 voy4g3r2: fwiw, if you plan to run current, it's a good idea to be subscribed to the list, even if it means getting so many mails :-) 02:12:51 unixwitch: i know.. i am just being stubborn :) 02:13:44 and likely to commits-main to know what broke your setup :D 02:13:55 i just want ot fix manual pages :) 02:14:07 which i got a categorized list about 2 hours ago, so new post while this install happens 02:14:20 you don't need to run current to do that, just use the main checkout 02:14:25 the disc1 install is verifying checksums of selected distributions (base, kernel, kernel-dbg, lbi32, ports, src) 02:15:26 checksum fail on base, dang nab it 02:16:11 does it succeed on the image? compare with provided hashes 02:16:12 yuripv: true, it would be interesting to try installing freebsd, as i only installed it a handful of times and mainly raspberry pi images.. which does NOT do an install 02:19:27 checking now.. 02:20:16 https://bsd.to/j41D 02:20:18 Title: dpaste/j41D (Plain Text) 02:20:22 looks like we have a mismatch :) 02:20:31 I could see no changes to the PAM in the jails - so I simply copied in the new set of config files from the host - and removed all opie libs from the basejail - seems to work 02:21:33 BarnabasDK: hmm, you shouldn't need to remove the opie libs since the upgrade should take care of that. seems like something went wrong somewhere 02:21:41 (no idea what, though) 02:22:32 ezjail is not really supported well any longer, I should find an alternative 02:44:49 if i'm not a committer, is it okay to open a PR and assign it to myself? (it's for the alc(4) msi-x fix which is stalled, but i want something on the bug list so i don't forget it... plus it is an actual bug) 02:53:20 Not sure you can self-assign if not a committer. I'd ask in #freebsd-bugs. 02:58:04 you don't need to assign it to yourself, you'll be mailed on any changes on that PR 02:58:14 (as submitter) 02:59:58 unixwitch: also, if you have the patch, opening a PR on github or better yet review on reviews.freebsd.org would help 03:00:57 i don't have a patch yet, i'm trying to find some documentation on the card 04:12:28 ohhh there is a way to subscribe to freebsd-current without getting emails.. not sure how this will work but it will allow me to send an emaiL :) 04:42:53 well here goes my first CURRENT mailing list entry 04:42:59 time to see if it is clear enough.. 04:50:30 well i guess we can give a 14.0 install a try and upgrade to 15.0... 05:00:33 well egg on face.. there are multiple checksum lines in the checksum256 files that do appear to match.. but why would the installer say they do not .. 05:00:36 errr 05:04:34 voy4g3r2: which images specifically have you tried? 05:04:42 (not just the name, the hash/date as well) 05:06:24 ((that is, not just bootonly, the full filename of the iso is sufficient) 05:06:25 ) 05:07:25 * FreeBSD-15.0-CURRENT-amd64-20231216-ca39f23347e1-266973-bootonly.iso 05:07:25 * FreeBSD-15.0-CURRENT-amd64-20231228-fb03f7f8e30d-267242-disc1.iso 05:07:26 * FreeBSD-15.0-CURRENT-amd64-20231223-dac33a65b965-267058-bootonly.iso 05:08:19 and now that first current mailing list entry is just garbage.. i am annoyed.. i figured a sha256 would do the magic 05:08:35 https://lists.freebsd.org/archives/freebsd-current/2023-December/005207.html 05:08:37 Title: Checksum Error on installer (3 iso images in CURRENT) 05:08:42 this has more details, if required 05:14:37 i am now trying the install one more time with teh bootonly 20231223 one and going to see if i can get more than just the dialog 05:14:41 like a message giving more context.. 05:18:41 voy4g3r2: if you roll bootonly, go with 20231228 05:19:24 bootonly is going to download whichever sets you select from here: https://download.freebsd.org/snapshots/amd64/15.0-CURRENT/ 05:19:25 Title: Index of /snapshots/amd64/15.0-CURRENT/ 05:19:41 iirc it doesn't trust the MANIFEST there, it has its own 05:19:53 actually, that can't be right 05:20:06 hello 05:20:27 either way, with bootonly go with the absolute latest to be safe 05:20:35 i found this chatroom from the freebsd.org website pleased to meet you :D 05:21:01 I have no idea how the mirror syncing works, if there's a chance that you were just getting really lucky and hitting it in some discrepancy between MANIFEST and the dist files 05:21:08 aeronot: o/ 05:21:11 if I want to run a GNU/Linux virtual machine (VM) guest also to get some drivers *BSD doesn't have, should I run Xen or is BHyVe good enough or better? 05:25:09 kevans: i will give the latest version a try.. 05:25:28 for some reason.. the installer does not generate logs of steps anywhere in /var/log 05:37:48 still downloading.. 05:50:55 woohoo, a different error this time 05:51:25 Error while extracting base.txz: Lzma library error: Corrupt input data 06:15:00 and run it a second time, back to the checksum thing.. what a visicous cycle, that can wait till tomorrow 06:22:39 darwin: bhyve works pretty well. what driver do you need that freebsd doesn't have? 06:23:51 Alcor Micro Corp.: USB hub & AU9540 smartcard reader & multi flash reader 06:24:01 they're in a 5.25" 'multi-function hub' I got 06:24:35 unless it's a pci device i don't think you'll be able to passthru it to the guest 06:24:55 it's just plugged into USB & SATA headers 06:25:04 headers/sockets/whatever 06:26:02 again, unless it's pci, you won't be pass it to the guest 06:28:18 and freebsd can't be a dom0 06:29:18 alright. Is it possible any this might change in future? 06:31:16 i would be surprised 06:37:51 voy4g3r2: first error is incredibly concerning 06:38:50 when did we stop being able to run freebsd dom0? 06:48:51 thanks 06:50:52 er, domu. "the host" 06:51:00 it's been a while since i've used xen 06:55:47 rtprio: dom0 is the host, and we reportedly run as both for years now 06:56:16 (on x86) 06:56:41 aarch64 work was in progress, not sure if that was domU or dom0 07:02:40 kevans: that's not whan `man xen` says 07:02:51 BUGS FreeBSD is only able to run as a Xen guest (DomU) and not as a Xen host (Dom0). 07:03:48 sounds like it needs an update then 07:08:30 alright, fired off an e-mail to roger about updating that 07:08:39 i bet there's other missing bits 07:12:06 i'd like to know how to domu freebsd 07:12:14 i just assumed it wasn't a thing 07:17:02 the first couple of results in google for "freebsd xen" are pretty useful there; https://wiki.freebsd.org/Xen is maybe the authority here 07:17:03 Title: Xen - FreeBSD Wiki 07:20:19 rtprio: Bhyve might well be more flexible. Type 1 hypervisors are a little less flexible than Type 2. 07:29:12 i'm getting along fine with bhyve now, sure 07:35:26 I ran Xen for years, and then moved over to KVM and it was good. Now everything's in a container, more or less. 07:37:08 yep 07:37:25 often they're in a container even when they don't need to be 07:44:21 Not here generally, no. 08:01:02 I'm having a problem with my freebsd 14.0 installation 08:04:18 no services are running, pkg is not able to run the error message is as follows : ld-elf.so.1: Shared object "libcrypto.so.111" not found, required by "pkg" 08:35:20 sixpiece, was just though the same - try using pkg-static 08:35:32 and start with a pkg-static bootstrap -f 08:35:56 will install a new pkg built with a new version of libcrypto / libssl 08:36:54 ld-elf.so.1: Shared object "libcrypto.so.111" not found, required by "pkg" 08:37:19 yes use pkg-static 08:37:27 to fix this particular problem 08:37:27 I did 08:37:54 obviously not :-) 08:38:15 I did though 08:38:47 https://bsd.to/tu6P 08:38:48 Title: dpaste/tu6P (Plain Text) 08:39:08 try a pkg-static update first then 08:39:38 everything is up to date 08:41:58 Anyone here switched from isc dhcpd to isc kea? Saw this morning that isc dhcpd was EOL end of 2022. I must be living under a rock. 08:44:46 sixpiece, what is the output of $> ldd /usr/local/sbin/pkg-static 08:45:15 ldd: /usr/local/sbin/pkg-static: not a dynamic ELF executable 08:45:26 as it should be 08:45:36 what if you run that with a full path 08:46:31 "/usr/local/sbin/pkg-static bootstrap -f" 08:46:57 what the linker is telling you is, this is a statically linked executable - not using libraries (shared objects) 08:47:29 same thing 08:47:44 have no explanation for that 08:48:01 root@videotron:/var/run # /usr/local/sbin/pkg-static bootstrap -f 08:48:01 pkg(8) is already installed. Forcing reinstallation through pkg(7). 08:48:01 ld-elf.so.1: Shared object "libcrypto.so.111" not found, required by "pkg" 08:49:31 is it possible to make it work? 08:50:55 I have never seen a statically linked executable (non ELF) bork about a shared object before 08:51:53 So - I really don't know 08:53:39 ok thank you going to go to bed and try tomorrow 09:44:25 pkg(7) would be /usr/sbin/pkg ? 09:44:32 Hi all. Has anyone ever discussed a freeBSD GUI installer like you have in linux? 09:44:50 Rather than an ncurses one? 10:29:58 For those you wondering, we did a Discord Hackathon yesterday, working on superv, a supervised bhyve manager. The meeting was recorded and uploaded to YouTube: https://www.youtube.com/watch?v=Dmap39245b0 10:30:00 Title: 2023-12-28 bhyve Discord Hackathon - YouTube 10:46:20 as root, why do i get the error "sudo: you are not permitted to use the -D option with /usr/local/bin/npm" from command 'sudo -u polyex -D /home/polyex/foo'? 10:49:02 thorre: I use Kea 10:49:34 since 2019 I think because ISC dhcpd is not very good at DHCP6 10:49:50 Remilia: Any pitfalls? 10:50:26 thorre: if I recall right, if you configure it to use a database backend it will terminate if it cannot reach the database server 10:50:39 otherwise dunno 10:50:50 Remilia: Mine will be serving a home environment :-) 10:51:06 it is perfectly fine otherwise 10:51:21 i installed konsole on a laptop, but the configuration windows are longer than 1080 pixels and not resizeable :( 10:51:25 Ok, thank you. I will give it a spin 10:51:37 thorre: also it works just fine with powerdns for ad-hoc 10:52:12 (or I think it does? I forgot if I actually tested that thoroughly enough) 10:58:54 does 'su' have any way to chdir? 11:00:12 polyex: What do you mean? 11:00:55 when you do `su -`, it will do a login, changing ot the user's home directory 11:01:37 su seems great why even use sudo? 11:02:31 because all it does is giving full permissions of one user to another which has the permissions to run su. No more fine grains 11:24:31 also thorre indeed I run it in a home environment; was experimenting with using postgresql as the backend for static leases 11:27:13 gnrp so when use sudo and when su? 11:29:55 su requires the knowledge of the superuser password 11:30:25 sudo and doas do not 11:31:28 su also does not limit its invoker in any way, much unlike sudo and doas 11:32:53 nice 11:36:46 what's a good way to make one FreeBSD PC a duplicate of another, like get a list of all user-installed packages and maybe in future run pkg in parallel over ssh? 11:37:15 NFS 11:38:19 maybe I'd better not make them exact duplicates because the hardware differs slightly 11:38:53 mount /usr on both from the same NFS source 12:20:22 when i run pkg upgrade it says updating freebsd repository catalogue... then a few lines of pkg: an error occured while fetching packages. then repository freebsd has no meta file, using default settings. and eventually error updating repositories 12:20:34 but i can ping pkg.freebsd.org so i know network is good. pf is off 12:21:39 same when i run pkg-static bootstrap -f, fails with error fetching, host doesn't resolve, address resolution failed for pkg.freebsd.org... but i can immediately ping pkg.freebsd.org 12:47:54 nvm got it 12:58:18 is it possible to get "global" EQing in FreeBSD that is more granular than just the bass/treble knobs hint.pcm.*.eq enables? 13:00:50 maybe by piping global audio unmodified into a sound fx daemon before output? 13:02:04 polyex: so… jack probably? i have no idea how i would plug that together, tho… 13:02:19 well i could be wrong too. haven't done audio yet 13:02:22 also no idea if jack itself is enough, or if i need something else to act as an lv2 host or somesuch thing. 13:02:44 when you figure it all out pls add to freebsd wiki or write blogs or smth 13:03:35 will do, but i might actually get to doing custom DSPs before, which would remove my need to have this in the OS.^^ 13:03:50 ya sounds awesome 13:04:21 earliest i might manage to mess around with that will probably be summer, tho. 13:04:48 and till actual hardware exists, even longer. so an intermediate solution would be nice^^ 13:05:40 maybe email the mailing list? like freebsd-audio or smth 13:07:33 unixwitch does this look like a good way to setup ldap server on frebsd? https://wiki.freebsd.org/LDAP/Setup 13:07:34 Title: LDAP/Setup - FreeBSD Wiki 13:07:46 actually, this might be a good place for me to start doing dsp… no need to build hardware and C + math is the same as on a uC… 13:15:20 mane: i haven't used ldapscripts before (i use ldapvi mostly) but that seems basically fine... i do strongly suggest reading the openldap manual though, it covers some important things not mentioned there like ACLs 13:15:40 thanks 13:32:06 antranigv: where's the source for superv? 13:41:10 thorre: i've been using Kea for a few months, it seems fine. configuration is annoying (JSON) but it works well enough. this is only for a home/soho network, nothing fancy (except dhcp relay maybe). 13:41:49 unixwitch: Thank you for the feedback 13:42:26 I am really glad that I spent to much time on my Neovim setup so json and other things are "taken care of" by LSP, formatter and linters. 13:44:08 But yeas, the configuration for a home environment becomes very big. But I see clera benefits for real world production configuration. 13:44:34 Nice that kea seems to be API dirven so that it can be configured without re-start. 13:46:02 in rc.conf are these two lines sufficient? 13:46:06 kea_enable="YES" 13:46:08 kea_config="/usr/local/etc/kea/kea-dhcp4.conf" 13:49:00 thorre: kea_config shouldn't be needed; it autostarts the appropriate daemons based on whether the file exists, so just don't create the configs you don't want 13:49:17 JSON: slightly better than YAML… 13:49:27 unixwitch: Thank you. 13:58:54 oh no, devel/nspr broken on current 14:15:03 https://dpaste.com/2BXGKFMKY obvious patch for anyone else who hits this (i assume it'll be fixed soon anyway) 14:15:04 Title: dpaste: 2BXGKFMKY 14:18:51 unixwitch, you're not the first one to mention this. there's currently no PR open for that. Maybe because everybody thinks the same way - this is your chance ;) 14:19:06 jbo: it seems like -current is already on top of it, so i just fixed it locally 14:20:06 although maybe i'll check if there's an existing PR already and open one just in case... need more coffee first 14:53:48 polyex: "why use sudo" - the original purpose of sudo was to give users restricted access to root or other accounts; you can permit them to only execute certain commands, for example to restart a service, but without giving them full root access. Linux (i think Ubuntu specifically) decided to use sudo instead of su for all root access, and other people followed that trend. 14:54:24 polyex: i think the main advantage of this is you can give multiple people root access without needing a shared root password. also, many end users are used to having a single password, not a separate user and admin password, because e.g. Windows desktop works like this. 14:59:46 makes sense ty! 15:00:14 i'll try doas next 15:00:24 same advantages of sudo but way less code and openbsd ppl are good 15:00:28 ever try it? 15:00:38 i have not 15:03:14 just a little nitpick sudo is also from a openbsd guy 15:03:28 oh ty 15:04:31 https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=sudo https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=doas 15:04:34 Title: CVE - Search Results 15:06:01 polyex: many of those CVEs aren't in sudo itself, if you read the description. 15:06:25 oh shit 15:11:11 hrm.. so got my first email response for the iso issues in installer, for 15.0, a propogation issue.. 15:12:58 what iso issues ? 15:13:42 polyex: install of 15.0, based off amd64 iso images, if you download the iso the checksums are not aligned.. which causes the installer to NOT allow you to install the system 15:15:12 ah ya 15:15:18 how's 15 otherwise? 15:16:09 i would not know, i am trying to do a 14.0 -> 15.0 upgrade right now 15:16:15 i updated to current yesterday and it hasn't crashed yet, so take that for whatever it's worth :-) 15:20:37 that is a good sign, at least this 50 millionth install may go right.. for once (joking) 15:23:38 i need to some help with nfs on freebsd 15:23:47 clnt_create: RPC: Program not registered is what i get when i try to mount 15:24:09 mane: are you using NFSv3 or NFSv4? 15:24:24 nfsv4_server_enable="YES" is what i got enabled 15:24:41 did you specify the 'nfsv4' mount option on the client (or vers=4, which is the same thing)? 15:24:47 no 15:25:02 try that, and if it works, you might consider disabling NFSv3 entirely unless you have a reason to use it 15:25:17 v4 is much easier to mount because all the RPCs are inline, it doesn't need rpcbind 15:30:08 ohhh i should disable nfs_server_enable myself then 15:30:14 i went through that hell a few days ago.. 15:30:19 the rpcbind stuff 15:30:32 voy4g3r2: you want nfs_server_enable=YES, nfsv4_server_enable=YES, nfsv4_server_only=YES 15:30:49 hello I upgraded to freebsd 14 and having trouble to get it work. Can someone please help me here? 15:30:56 and probably nfsuserd_enable=YES, nfsuserd_flags="-domain my.domain.com" (not strictly required as it will pick up the default from the hostname, but i prefer to be explicit) 15:32:59 is there someone awake that can help me? 15:33:12 ld-elf.so.1: Shared object "libcrypto.so.111" not found, required by "pkg" 15:33:34 like what do I do about this for example someone tried last night I stayed up until 4am est I am now 15:34:31 there is no documented solutions that I can find with google I tried 2 or 3 one giving sim links another installing openssl via the ports both did not work 15:34:58 the ports created another issue I also tried pkg-static -f stuff and that also did not work but maybe there is another variation that I am not aware of 15:35:14 sixpiece: i would try fetching the current pkg package from pkg.freebsd.org for 14, and then install it with pkg-static 15:35:32 can you explain how to do that first part? 15:35:48 or both parts 15:36:20 I'll try to search that 15:37:10 to fetch the package (assuming quarterly on amd64): "fetch http://pkg.freebsd.org/FreeBSD:14:amd64/quarterly/All/pkg-1.20.9.pkg", then "pkg-static add pkg-1.20.9.pkg" 15:37:12 there's also an issue that uname -v is not the same as /etc/OS-release one is 14.0 release p3 the other is p4 15:37:22 (i haven't actually tried this though...) 15:38:45 I get Not Found 15:39:29 hm, out of date mirror? try this url instead, that definitely works http://pkg0.sjb.freebsd.org/FreeBSD:14:amd64/quarterly/All/pkg-1.20.9.pkg 15:40:07 any way to make my little bash code better? https://pastebin.com/VFxsff02 15:40:09 Title: #!/bin/bashd () { s=($EPOCHSECONDS) mkdir ~/.trash/"$s"; - Pastebin.com 15:41:13