00:05:41 <_xor> checking whether mktime, gmtime, localtime work correctly in 2020... no 00:05:41 <_xor> configure: error: date-time conversions do not work in 2020 -- is tzdata installed? 00:06:19 <_xor> Umm, poudriere is complaining about that for math/R. Is that likely me or a port issue? 00:07:35 hm, are you building WITHOUT_ZONEINFO ? 00:07:57 * RhodiumToad does, but I haven't tried math/R 00:08:10 <_xor> Is that an option for make.conf or src.conf? 00:08:25 src.conf 00:08:43 <_xor> Nope, don't have WITHOUT_ZONEINFO=yes 00:09:00 is TZ set to anything weird? 00:09:25 <_xor> Shouldn't be, where am I checking for that? On the host? In the builder jail? Poudriere config? 00:09:56 in the builder jail, I don't know whether poudriere inherits it 00:10:13 <_xor> Hmm, I wonder 00:10:52 * _xor just checked if the master jail had /etc/localtime already in it 00:11:12 <_xor> Nope. I'm also assuming that poudriere copies that into the jail after it clones it or whatnot. 00:12:46 do you have WITH_ZONEINFO_LEAPSECONDS_SUPPORT set in src.conf? (never do that) 00:13:03 <_xor> Nope. 00:13:21 * RhodiumToad fires up poudriere to see what happens 00:13:35 if it's "never do that", why it's even an option? 00:13:53 <_xor> Oh yeah tz in builder jail is fine. Just looked at the logs and the timestamps match the host. 00:14:00 dunno. I think I put up a doc patch to document the dangers of it 00:15:19 I never spent much effort pushing for it or finding reviewers: https://reviews.freebsd.org/D25902 00:15:20 Title: ⚙ D25902 Add warning against leapseconds to src.conf manpage. 00:16:18 [00:02:43] Failed ports: math/R:configure 00:16:40 so it's not just you 00:16:46 <_xor> ah, that's good to know. 00:17:11 have you checked on the package builders? 00:17:43 <_xor> I should get into the habit of checking bugzilla for existing issues first. Unlikely, but only takes a few seconds to check. Isn't there a CLI tool in ports to help with the search? 00:17:46 there don't seem to have been recent changes to the port 00:18:05 <_xor> I just started poudriere porttest on it and dropping into a shell to take a lookg at config.log. 00:19:33 what OS version? 00:20:00 <_xor> 1302505 for both kernel on host and userland on host and in jail. 00:20:43 does /usr/share/zoneinfo/Europe/London exist in the builder jail? 00:21:13 <_xor> Apparently not. 00:21:40 that's odd. it doesn't exist in mine, but that's because I build with WITHOUT_ZONEINFO=yes 00:23:08 <_xor> https://termbin.com/u7t6 00:23:32 here's a workaround: 00:23:33 <_xor> There's the relevant snippet of the config.log that was dumped by configure. 00:25:59 in make.conf, math_R_VARS+=CONFIGURE_ENV+=r_cv_working_mktime=y (just testing it myself now) 00:27:10 <_xor> ah 00:28:04 bah, didn't work 00:28:14 <_xor> I assume that's an R-specific idiom since it's prefixed with r_? (was going to ask if that's a common idiom to force configure check statuses) 00:28:21 <_xor> oh nevermind then heh 00:28:24 <_xor> What's exit status 4? 00:28:38 it means something did exit(4) 00:28:48 <_xor> I meant 4 specifically :P 00:29:20 <_xor> Was just looking for that but having trouble finding it. Guess maybe it's not standard, even though I just happen to read in the man page that "it's not good practice to call exit with arbitrary codes" 00:29:42 from the chunk of code, it's in the part testing Europe/London for DST 00:29:55 if(res != 1593601200L) exit(4); 00:30:03 <_xor> oh 00:31:32 hm, try =yes rather than =y 00:32:47 <_xor> k running now 00:32:58 adding that kind of stuff to CONFIGURE_ENV is indeed a way to force the result of configure tests, but the name of the test varies and you usually have to look them up in ./configure 00:33:41 <_xor> =yes might have worked, seems to be getting further this time around. 00:33:54 <_xor> [00:01:05] checking whether mktime, gmtime, localtime work correctly in 2020... (cached) yes 00:34:20 yeah, the (cached) means it's believing the value from the environment var rather than actually doing the test 00:34:25 <_xor> yup 00:35:00 <_xor> Should Europe/London exist or is more a case of the configure checking logic being incorrect? 00:35:09 I'm not sure why you don't have the zoneinfo files though. what parameters did you use creating the jail? 00:35:38 Europe/London should exist if the zoneinfo files exist at all, which should be the case unless you built WITHOUT_ZONEINFO=yes 00:35:54 <_xor> It's from a slightly customized build of stable/13. 00:36:20 (there's a zoneinfo package you can install if the base system is built without zoneinfo, but poudriere can't cope with installing that package, though it can build it) 00:36:45 (since it doesn't like things writing to /usr/share) 00:36:45 <_xor> I checked src.conf and WITHOUT_ZONEINFO isn't in there, but who knows, maybe the build that I have on my server was built with WITHOUT_ZONEINFO=yes and the line in src.conf was removed after the fact. 00:37:05 <_xor> I have FreeBSD-zoneinfo since I'm using pkgbase. 00:37:13 <_xor> I wonder if that's the issue. 00:39:06 what options did you use to poudriere jail -c ? 00:39:17 <_xor> Hmm, just checked revision history for src.conf in my repo and don't see any sign of WITHOUT_ZONEINFO having been there at any point (which would be odd too because I doubt I would have disabled it). 00:39:36 anyway, the workaround seems to work fine 00:40:33 <_xor> Don't remember now, but checking /usr/local/etc/poudriere.d/jails/1302505-amd64/* to see if that gives me any hints. 00:40:58 poudriere jail -l should show relevant info 00:41:18 <_xor> METHOD=tar 00:41:27 * _xor sighs 00:41:50 <_xor> Don't tell me the set of tars that I built a long while back is missing those files. 00:42:17 shrug 00:42:34 <_xor> Feels kind of strange though that an error like this hasn't popped up before if that's the case. I run a bunch of poudriere builds all the time and the jail was built 6+ months ago. 00:45:31 shrug 00:45:56 all I can say is that the R port as it currently stands won't build without zoneinfo files 00:46:37 <_xor> Yeah, this is going to nag me as it's a bigger problem to me if the dist archives are missing files that should be present :P 00:46:44 <_xor> Oh well, another item on my TODO list. 01:22:19 <_xor> meena: Does update-packages require buildkernel+buildworld first or does it include that as part of its target? 01:22:45 you're fun :) 01:24:26 * _xor is guessing not as all he sees flying by his screen is a bunch of directory recursing + install commands 01:24:37 yuripv: changing the on-disk format for PR 265950? 01:24:38 265950 – POSIX 2008 locale failures when global locale not C https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265950 01:37:13 nope, adding yet more stupid public symbols to libc :( 01:38:50 ahh 01:39:34 phew :-) I've been working on this kind of stuff for a downstream, and it would've been a weird time in that to drop another format revision :-p 01:40:18 kevans: like this: https://reviews.freebsd.org/D41927 01:40:20 Title: ⚙ D41927 pr265950 draft 01:40:20 265950 – POSIX 2008 locale failures when global locale not C https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265950 01:46:41 yuripv: ah, ok, yeah, that's about what I had pictured... it does suck that we have to export this just to do it right 01:55:27 odd question, is there any easy way to download a file from git hub, without using git? maybe using wget or curl? 01:55:41 sure 01:55:44 or an equivalent tool in base? 01:56:07 https://raw.githubusercontent.com/thedaemon/dotfiles/master/.Xdefaults 01:56:10 something like this 01:56:22 so use the raw.git etch url and use fetch 01:56:48 so fetch https://raw.githubusercontent.com/someuser/somerepo/master/fileyouwant 01:57:46 yeah, there's generally a 'raw' button for most things, then you can just feed that to fetch(1) whose default behavior is like `curl -O` 01:58:07 (/ `wget`) 02:00:49 awesome, thank you 02:03:56 brilliant, thank you! 06:02:09 _xor: it includes that as part of its target 06:32:04 how can I change vxlan udp/port number on ifconfig commands ? 06:34:41 thanks 06:34:53 https://man.freebsd.org/cgi/man.cgi?ifconfig(8) vxlanlocalport etc. 06:34:54 Title: ifconfig(8) 06:37:32 <[HOT]> Hi Guys 06:37:32 <[HOT]> plz, where can I buy valid US CC?? 07:57:27 AllanJude, you willing to take the ownership of #eurobsdcon 07:58:01 I have a gentleman trying to prove it should be his, it certainly should not be mine - I took it over during the server move as a defensive move 07:58:14 his emails are not reaching me and he has mentioned you 07:58:22 I trust you so ... yeah 08:10:12 Hi. Looking for a freebsd git merge conflict resolution tool. I see there is linux-bcompare but it requires the compatibility enabled in the kernel. Do i miss another tool? 08:11:25 What makes me look is this git output: 'Hit return to start merge resolution tool (bc): The merge tool bc is not available as 'bcompare'' 08:15:19 RhodiumToad: jails could help if you nullfs mount 08:15:53 ooups looks list I was too far in my scroll history 09:47:30 broke something, now su returns su: Sorry 09:48:37 removed user from group wheel? 09:49:01 Add user to dialer group for access to serial port (as root): 09:49:04 09:49:07 pw usermod myuser -G dialer 09:49:10 that's what i did 09:49:14 # pw usermod me -G dialer 09:49:18 that's it, yes 09:49:35 but groups return: me wheel operator video vboxusers ? 09:49:39 what would that? 09:49:56 V-T60: did you re-login? 09:50:02 and # groups me gives me dialer 09:50:13 "me dialer" 09:50:21 was that command bad? 09:50:35 presumably i had "me wheel operator video vboxusers" 09:50:38 it overrides the groups for user instead of adding user to group 09:50:45 and now have "me dialer" 09:50:55 i want it to be " me wheel operator video vboxusers dialer" 09:51:16 pw groupmod dialer -m me 09:51:25 how do i reach that result when got into superuser account? 09:51:26 pw groupmod wheel -m me 09:51:29 and so on 09:51:30 okay 10:08:14 -G overrides, i think -m adds 10:10:21 Is there a way to tell which particular driver was used for a device? I read the manual of pcm (snd) and learned a bit about it. I checked and figured out the snd drivers are compiled into my (default) kernel. I checked dmsg and see pcm lines picking up the audio devices. But i dont see which driver was used or do i? 10:13:52 KingShark: try pciconf -l (may be with -v for more information) 10:14:50 also devinfo -v 10:24:57 does it even make sense to use pulseaudio on top of oss? wouldnt oss be enough? 11:17:21 panic: page fault. Is my ram/disk failing? :) 11:18:47 i installed a kernel debugger now in case it happens again 12:19:36 nice 12:22:19 page fault panics aren't usually hardware problems, though they can be (typically RAM rather than disk) 12:22:25 more often they are driver bugs 12:30:32 interesting. did not tinker around much with drivers, just the freebsd 13.2-release base system with the i915kms drivers for intel/nvidia gpus. it happened while using blender so maybe the rendering sent some unusual calls 12:34:56 KingShark: you don't have to change anything in the drivers (or more generally, the kernel) to experience page fault panics. they are usually caused by dereferencing invalid memory (not always, but usually) 12:35:12 it's likely that this is a bug somewhere and if you can get a core dump, you could report it 12:37:15 Installed and configured nginx under FreeBSD. The log files are in /var/log/nginx. Do they automatically get rotated? 12:40:28 dstolfa, it did write something in /var/crash/core.txt.0 but i lacked a kernel debugger at that time so thats the only information in the file (i installed gdb meanwhile) 12:40:36 tercaL: No. I had to add a script and crontab entry to do that 15:31:12 does anyone know why my dns doh nginx gateway is not working? I want to create a DNS server with bind9. `nginx.conf`=https://pastebin.com/5jCu21CX `named.conf`=https://pastebin.com/fy0FG1ST 15:31:13 Title: #user nobody;worker_processes 1;events { worker_connections 1024; - Pastebin.com 15:32:48 Schamschula: why crontab though when there's newsyslog(8) and newsyslog.conf(5)? 15:44:17 al1r4d: not working? any error message? 15:44:44 i can't find on /var/log/message.. but i realized i did wrong.. let me fix it 15:45:05 al1r4d: nginx doesn't log to there, usually 15:46:32 since when is the -g option for geli (encrypted /boot, or so it sounds) around? and is there any documentation on how to actually use it? because man geli is pretty tight-lipped about that… 15:48:26 the geli boot options are weird because it's not exactly clear which ones are for gptboot and which for loader 15:49:04 (and which for kernel) 15:49:26 oh, there's a distinction? that's even more confusing because i still configure uefi booted stuff with loader.conf… 15:50:44 and god damn, i downloaded the tiny memstick image to fix up a new system quickly and have to see that the new installer is extremely janky. i think i'll just do it completely manually because figuring out why the damn thing keeps breaking is probably more work :F 15:53:16 like setting up an interface that's already set up, skipping the dhcp step even tho i said yes but then ignoring the existing dns config. failing to download files and then just wanting to completely restart instead of just offering me to choose another mirror. then failing even after restarting the setup because somewhere some partially fetched file is laying around and (surprise!) not 15:53:17 extractable or some other dumb stuff like that… 15:54:34 I slightly revise my previous statement 15:55:01 having picked through various bits of code, the -g flag is used by both gptboot and loader, 15:55:07 while -b is used only by the kernel 15:55:32 gptboot and loader will only try and decrypt partitions where -g was specified 15:55:46 kernel will try and decrypt partitions with either -g or -b 15:56:32 bottom line is that you need -g for partitions containing /boot, and -b for partitions that don't have -g but which contain the root filesystem 15:57:03 for the longest time the GELIBOOT flag didn't imply BOOT, so you could easily create a GELI partition that we'd deceptively use in loader but fail to mount root from it 15:57:22 hm, I didn't check before 13.2 15:57:36 i think i fixed that in 12.0 15:57:52 so use -g for partitions containing /boot and -b for partitions containing / even if they also contain /boot 15:58:03 i just couldn't think of a reason where we would want that 15:58:16 specifying -b on a partition that also has -g does not seem to be harmful 15:59:26 okay, one thing i don't understand tho – where does a -g partition get its keyfile from? 15:59:40 or does that work exclusively for when the passphrase represents the entire key? 16:00:20 the installer was never fixed to use just -b instead of -bg, fwiw 16:00:35 so -bg is actually incredibly well-tested still 16:00:52 gptboot has nowhere to read keyfiles. I don't think that loader has anywhere either, though there is a comment about that feature being missing 16:01:07 grmbl, tiny memstick doesn't have the archives and fetching via ftp.freebsd.org fails… 16:01:57 RhodiumToad: well, i can put a keyfile on /boot and note it down in loader.conf – but that only works *after* you actually got into /boot – hence my confusion. 16:01:58 loader has a load_geli command 16:02:07 (one could in theory have loader.efi get keyfiles from the ESP, but it seems questionable how much security that adds) 16:02:22 what's the ESP? 16:02:34 the efi partition? 16:02:37 ESP = EFI system partition 16:02:48 I think the more common scenario is to load_geli a key from removable media 16:03:41 kevans: how? i currently have a setup where i just have the entire /boot on a usb key and just yank it out after the machine is started.^^ 16:04:04 load_geli loads a key, not a keyfile, no? 16:05:03 should be a keyfile according to the manpage 16:05:17 ah, and it sets the module type to geli_keyfile: 267 sprintf(typestr, "%s:geli_keyfile%d", argv[1], num); 16:06:33 right, but presumably loader itself isn't using that, it's for kernel to use? 16:06:52 correct 16:07:17 so you can use that for example to have a keyfile for /, but not for /boot 16:07:36 right, it's for a case like phryk's where they don't care about encrypted kernel 16:09:33 well it's not that i don't care. i just came up with this pattern as the most reasonable compromise back when i did my first freebsd laptop. back then, either -g didn't exist or i overread it in the manuals. 16:10:55 honestly i still want to have a proper secure boot. /boot *could* be unencrypted for all i care as long as it'd be signed and the signature checked on startup so people can't just add a rootkit. 16:11:37 but i think geli with -g might be the next best thing currently available. 16:13:11 I believe you can sign loader.eli, though I haven't looked into whether you can then have that validate /boot files 16:14:38 but if loader.efi is signed and /boot is encrypted, that should be enough for most cases 16:14:50 i currently only have like decade old hardware. i don't think you can load custom keys/sigs into their tpms. 16:15:20 have a new 7950x lying around and gonna get board/mem next month so might be worth a shot with the new equipment. 16:16:50 i also recently stumbled onto something called mfs in the docs and think that could be used to really improve my remote-bootable crypto setup on the live machine. 16:18:25 … what was the command to make the built-in vi not be a complete flustercluck again? i thought ":set nocompatible", but apparently that's an error… :F 16:42:51 mhh, i created an efi partition as second partition on a disk and it doesn't seem to be recognized… 16:45:51 you want vi to be nocompatible with vi? :D 16:45:56 i only created an msdosfs with -F 32 -c 1 and copied loader.efi to EFI/BOOT/BOOTX64.EFI, pretty sure this is enough on my laptop enough… 16:46:22 yuripv: i think the compatibility in that refers to ancient hardware nobody outside a museum still has 16:49:32 it recognizes my laptops bootsticks, too… so i guess this bios just doesn't recognize efi partitions that aren't the first partition on the disk… 16:51:56 phryk: did you set the partition type correctly? 16:52:11 RhodiumToad: pretty sure something-efi 16:52:21 what does gpart show say about it 16:52:45 give me a minute, currently booting into the livestick to set up a custom bootstick^^ 16:53:54 RhodiumToad: "efi (40M)" 16:54:05 that should work 16:54:16 though 40M is too small 16:54:28 works flawlessly on my laptop so far. 16:54:33 (bios should still recognize it) 16:54:43 I mean, the recommended size is much larger 16:55:32 why tho? i mean i'm putting one file on it that's… 928K?^^ 16:59:11 it's just the standard advice 17:07:12 okay, going the usb stick route seems to work. getting a couple "Can't read linker hints file." but it's running. 17:10:37 weird, freebsd-version seems to look to /boot to figure out the running kernel? instead of just… asking the kernel? that seems a bit backwards 17:25:56 It's using sysctl(8). 17:27:13 debdrup: are you sure? it told me it couldn't determine the running kernel version when i didn't have /boot mounted… 17:30:36 If you look at the shell script in /usr/src/bin/freebsd-version/freebsd-version.sh.in, you'll see that the running-version function uses `sysctl -n kern.osrlease`. 17:34:18 debdrup: mhh, sysctl doesn't fail when /boot is missing, tho. but freebsd-version -k does. 17:35:55 okay, 13.2-p3 working, now updating the fresh system to 14.0-BETA2. here's hoping it doesn't kill another disk the second time around ^^; 19:16:41 finally got a working 14.0 with working drivers for my new gpu. 19:17:05 now working data recovery. wish me luck. :P 19:18:25 Good luck, phryk! 19:19:00 break a leg phryk ! 19:19:20 phryk: which GPU? I am running drm-515-kmod for my AMD 6750XT in 14.0 19:41:43 thedaemon: rx6600xt 19:42:36 and thanks, nothing exploded yet, currently backing up all development data ^-^ 19:44:38 yay 20:23:40 Freaky: any idea how to integrate this, https://freshbsd.org/freebsd/src/commit/da51e0f586389de0063650343e264ae58116e3c0 so that commits like https://freshbsd.org/freebsd/src/commit/948e11aaf420cd7d493cc2e118cacc06d18653fe and https://freshbsd.org/freebsd/src/commit/1c1ff7979571bf07c05a48e857b7b285b037410f show up when searching for me 20:23:41 Title: FreeBSD / src / da51e0f / Add .mailmap to normalize some author data - FreshBSD 20:24:39 what tool is that .mailmap for? 20:25:12 yuripv: i think it's for git 20:25:36 ah right, thanks 20:31:19 looks like cgit doesn't care either https://cgit.freebsd.org/src/commit/?id=948e11aaf420cd7d493cc2e118cacc06d18653fe (yet) 20:31:20 Title: src - FreeBSD source tree 20:43:39 looks correct to me? 20:47:40 or if you mean 'c' in your name, looks like it's missing the "Mina Galić " entry 20:55:51 yuripv: wanna comment on the review? 20:56:03 I didn't know that's necessary 20:56:10 i was just happy is possible 21:15:25 yep, done 21:15:32 yuripv: oh, for entries that already have the correct email address 21:15:59 correct 21:16:06 yuripv: you want to do the honours? 21:16:20 i can do it, yes :D 21:36:19 meena: that didn't help cgit, but it works in git log now 21:49:57 yuripv: cool 21:50:01 thank you! 21:55:25 meena: hmm, I'm not sure, I'll add it to the TODO 21:58:13 hi. how can I know what installed /usr/bin/tar on FreeBSD? I would like to get the source code of tar. "pkg which /usr/bin/tar" tells me that it's not pkg. i installed ports, but "find /usr/ports -type d -name tar" doesn't find anything 21:58:46 /usr/bin is FreeBSD 21:58:55 i searched for "tar" in https://github.com/freebsd/freebsd-src/ but hum, they are many words which contain "tar", and so it's a pain to navigate the results :-) 21:58:57 Title: GitHub - freebsd/freebsd-src: The FreeBSD src tree publish-only repository. Experimenting with 'simple' pull requests.... 22:00:15 https://gist.github.com/igalic/795aa561909981892526bb50ae8a96f8 22:00:16 Title: wtf · GitHub 22:00:17 no. 22:00:28 VimDiesel: if you look at usr.bin/tar you'll see the Makefile refers to contrib/libarchive 22:00:29 it's usr.bin/tar, but that's only Makefiles, the real source is in contrib/libarchive 22:00:34 thedaemon: is it https://github.com/freebsd/freebsd-src/tree/main/usr.bin/tar ? this directory doesn't contain C files 22:00:35 Title: freebsd-src/usr.bin/tar at main · freebsd/freebsd-src · GitHub 22:00:36 er, vstinner: 22:02:06 yuripv: latest tig uses it correctly. So next up, bug report for cgit 22:02:17 /usr/src/contrib/libarchive/tar 22:02:20 It's here ^ 22:02:26 if you have source downloaded 22:03:45 https://docs.freebsd.org/en/books/handbook/cutting-edge/ 22:03:46 Title: Chapter 26. Updating and Upgrading FreeBSD | FreeBSD Documentation Portal 22:03:49 meena: latest what? 22:04:03 https://github.com/jonas/tig 22:04:04 Title: GitHub - jonas/tig: Text-mode interface for git 22:04:10 oh 22:04:40 it's my preferred way of reading commits when I'm on my computer. (when I'm on my phone it's freshbsd ;) 22:04:41 'git pull /usr/src' this should get you going 22:05:28 oh neat meena 22:05:36 im running retroarch on the console with the i915 drm driver and i cant figure out how to give a user input permissions 22:05:43 I can't believe I've only been contributing since 2021. it feels like an eternity. 22:05:46 theres no input group 22:06:20 so input only works if i run it as root, but not as a regular user 22:06:39 what groups is your root in that user isn't? 22:07:04 groups rarely matter for root 22:07:06 thedaemon: on standard Unix, root doesn't really have to be in any special groups 22:07:12 oh my bad 22:07:20 but for drm stuff, the user should be in the video group 22:07:28 root has to be in video group for x11 22:07:30 in FreeBSD at least 22:07:32 * thedaemon shrugs 22:07:52 :D 22:08:08 i have the user in the video group and retroarch runs and video works 22:08:18 but i cant figure out how to make the keyboard work 22:08:20 thedaemon, yuripv : ok thanks, i found what i needed :-) i'm fixing test_tarfile of Python on FreeBSD: https://github.com/python/cpython/pull/108950#issuecomment-1730361505 -- in short, FreeBSD clears the sticky bit, unless -p option is used 22:08:24 Title: gh-108948: tarfile should handle sticky bit in FreeBSD by sorcio · Pull Request #108950 · python/cpython · GitHub 22:08:26 on linux you just add the user to the input group but on freebsd there is no input group 22:08:40 is there a man page? 22:08:44 I don't have it installed 22:09:00 or check the port doc, did it have anything when you installed? 22:09:17 bjornn: what kind of input are we talking about here? joysticks? 22:09:17 no 22:09:19 what isn't working? keyboard input? 22:09:24 yeah the keyboard doesnt work 22:09:28 ok 22:09:32 just making sure lol 22:09:50 it uses libudev-devd i think 22:09:57 https://www.freshports.org/games/retroarch/ 22:09:58 Title: FreshPorts -- games/retroarch: Cross-platform entertainment system based on libretro API 22:10:01 which like makes freebsd's devd work with apps that use linux udev 22:10:07 you can also use webcamd 22:10:18 you have to grant access permissions on the appropriate 22:10:19 /dev/input/eventN device to your user account 22:10:39 ^ found this as the pkg-message 22:11:44 and this is how the pkg was built 'UDEV=on: udev device hotplug support' 22:11:59 may be we could have input group as well and make those root:input 660 22:12:13 i suppose i could just use the operator group 22:12:42 and make /dev/input like the other dev folders that use operator 22:13:41 or just create an input group 22:14:01 but i assumed devd would already have some functionality for doing this 22:18:56 ok i think i figured it out 22:19:04 you dont manually mess with the permissions of anything in dev 22:19:09 you use devfs.rules 22:19:21 this really ought to be documented 22:19:39 but i suppose its not an issue for anyone uses xorg 22:20:39 good to know 22:20:46 you running in FB or something? 22:20:51 or wayland? 22:21:15 fb 22:31:41 ok yeah heres the way to do it 22:32:09 [localrules=10] 22:32:10 add path 'input/*' mode 0660 group input 22:32:17 this has to go in /etc/devfs.rules 22:32:35 and then you add devfs_system_ruleset="localrules" to /etc/rc.conf 22:33:19 and then create the input group and add your user to it 22:34:23 WARNING: Kernel has no file descriptor comparison support: No such file or directory 22:34:28 im also getting this warning when i start retroarch 22:34:30 not sure what that is about 22:35:56 im starting to think it might be easier to just use xorg for this 22:36:19 the drm stuff is all so linux specific 22:37:04 i miss when free software was actually written to be crossplatform and linux wasn't the sole OS that anyone cared about supporting 22:41:14 that was when? :) 22:46:07 like 20 years ago 22:48:52 we already had drm ported from linux back then 23:12:56 https://bugs.php.net/bug.php?id=77284 oh 23:12:58 Title: PHP :: Bug #77284 :: base64 broken on FreeBSD 23:12:58 77284 – Update port: databases/py-MySQLdb new default options https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=77284 23:13:54 https://github.com/php/php-src/commit/291589114aa9be899cf7d5d874c3b5bbdb35f336 23:13:56 Title: Disable ifuncs on FreeBSD · php/php-src@2915891 · GitHub 23:16:26 I'm currently playing with ifuncs and trying to see how to integrate it with Ruby, encountered that - PHP has them disabled for FreeBSD 23:18:05 why? 23:19:07 https://github.com/php/php-src/blob/master/configure.ac#L568-L573 23:19:08 Title: php-src/configure.ac at master · php/php-src · GitHub 23:19:40 meena: why to which bit of that 23:19:49 i really hope whoever is maintaing the port has a patch to enable it for recent versions of FreeBSD 23:20:19 doesn't seem to 23:20:26 we are making use of ifuncs in base / kernel? csu? etc… so i bet we'd notice if it didn't work. 23:21:18 https://github.com/php/php-src/commit/5a361c3a54c055cdf7088e76aa8efa159334e096it seems the underlying problem was their end 23:21:28 FUZxxl: ^ your code uses ifuncs, right? wanna chime in on that php issue 23:22:26 Freaky: i don't wanna look at php code ever again 23:24:34 anyway, it's bed time, i just don't wanna get up. otoh, sleeping in this chair will not be comfy 23:24:51 this chair bi-phobic! 23:30:37 meena: libc certainly appears to use them 23:30:53 I should dig out of old SSE2 memchr port 23:31:12 s/of/my/ 23:31:45 I'm doing byte counts at the moment, I don't think there's a libc function for that though 23:32:12 be good for wc -l 23:33:40 cool 23:34:18 yuripv: https://git.zx2c4.com/cgit/about/ there's no issues. just mailing lists. do these people not know that I hate mailing lists? 23:34:19 Title: cgit - A hyperfast web frontend for git repositories written in C. 23:45:53 "hyperfast" wonder if there's marks of benches 23:46:24 meena: one day I want to make my own issue tracker, for a laugh 23:53:50 LxGHTNxNG: can't be worse than no issue tracker 23:55:17 LxGHTNxNG: feature request: i would like to be able to search existing issues, and quickly figure out if they are already fixed 23:55:44 I should easily be able to bolt this on the side of a mailing list