00:35:21 EHLO 00:36:01 250-Welcome to #FreeBSD. 00:36:03 250 Continue 00:39:35 EHLO 00:41:23 * rwp laughs so hard I snort at the SMTP conversation not quite happening 00:42:35 EHLO there 00:42:52 Doesn't generally work any more, but it was the traditional. 00:43:30 My system would reject that EHLO because the "there" is not a FQDN and does not resolve. 00:43:59 rwp: Right. Today. Back in the day servers would shrug and say "sure". 01:36:29 Yes. It was the best of times, it was the worst of times, it was the age of wisdom, it was the age of foolishness, it was the epoch of belief, it was the epoch of incredulity, it was the season of light, it was the season of darkness, it was the spring of hope, it was the winter of despair. 03:24:48 remiliascarlet: if you haven't figured it out already, xorg.conf man page says BusID should be "PCI:::", and in your output "pci0:1:0:0" there are domain (0), bus (1), device (0), and function (0). 09:57:52 https://wiki.freebsd.org/DevSummit/202409#LiveStream 10:09:02 yuripv: Then why does the FreeBSD handbook tell me to do "pci0:1:0:0" instead of "PCI:1:0:0"? 10:10:53 https://docs.freebsd.org/en/books/handbook/x11/#x-config At 5.4.3 example 6. 10:11:31 Pretty anal that I need to figure out that the handbook is wrong... 10:22:53 patches welcome 10:40:34 Hmmmm https://freebsdfoundation.org/contributing-freebsd-documentation/ 10:42:19 I doubt they'd take too kindly to just copypasta this conversation referring to section and make it explicit from the outside, without a diff 11:37:39 Still, surprised to see that ChatGPT is more correct than official documentation. And ChatGPT is wrong about all sorts of stuff, but it is really good at translating languages or correcting grammar at least. 12:15:58 what software are people typically using for viewing/reading epubs? 12:17:04 The general population ? Probably amazon / kindle. IME they have a monopoly over book content 12:17:41 nah, FreeBSD users. 12:17:52 as in: "on a freebsd system" 12:18:39 Not sure. Maybe evince 12:33:29 jbo: i check epub content with mupdf - but i don't use it to actually read it 12:36:08 thanks ridcully - good enough for me. mupdf plugin for zathura seems to work for that 13:16:32 Greetings 13:20:41 once I chroot in mounted BE with /bin/sh as shell , and cat a file , I have the error 'cat: stdout: Function not implemented' , did you already ,get that error ? Maybe some config file are missing ? 13:21:21 (devfs is mounted) 14:14:14 sidh, so you have an interactive shell in chroot? One you can type and get results from? 14:14:39 yes 14:14:55 echo foo 14:14:57 That work? 14:15:09 most of command work, but cat throw that error 14:15:50 ldd `which cat` 14:16:10 echo foo work 14:16:26 And now I'm giving you a new command to run. 14:16:38 /bin/cat: libc.so.7 => /lib/libc.so.7 (0x801067000) 14:18:44 Just that one line? 14:22:39 sorry ( had a call ) 14:22:58 yes cat: stdout: Function not implemented 14:38:03 No, I meant the ldd output. 14:43:48 CrtxReavr: yes no additionnal info 14:43:59 i get the prompt back after 14:44:47 I dunno. . . definitely a weird issue. 14:44:58 Is your world in sync with your kernel? 14:45:01 I agree 14:45:39 it is a boot environment created from sets (base/kernel/lib32) 14:45:49 directly 14:47:01 but the host from which i run chroot, show different patch level between -k and -u (freebsd-version) 14:48:40 Does the file exist? ls -l /lib/libc.so.7 14:49:21 -r--r--r-- 1 root wheel 1957560 May 31 08:36 /lib/libc.so.7 14:49:43 If your your base system and kernel is out of whack, you may need to run a freebsd-update fetch and freebsd-update install - I would take relevant backups first. 14:53:21 ok will do that when the hypervisor will be less loaded 14:53:52 thank you Tabmow CrtxReavr 15:42:32 sidh: sounds like new binary on old kernel 15:43:34 cat(1) learned how to use copy_file_range(2) somewhere in the last couple of years, so you're probably hitting that. ktrace or truss could confirm 15:47:26 kevans: the context could match, I am testing a way to upgrade 12.3 systems directly to 14.1 with creating a BE directly from 14.1-R sets 16:02:38 kevans: once I boot on the new 14.1 BE, cat is running fine 16:10:28 sidh: right, that's not a supported configuration 16:10:49 new binaries will likely use new syscall, etc. that the old kernel cannot support 16:11:38 you can /usually/ get away with it if you're talking just two releases along the same branch, but shenanigans have happened there in the past, too, when it was really worth it 16:13:59 kevans: once booted on the 14.1 -release, I am using kernel and userland from 14.1 , right ? 16:15:11 I meant : once booted on the 14.1-R BE , sorry 16:15:52 assuming you created it correctly, yes 16:17:31 correct 16:17:32 I know now strange things can happen while chrooting a newer release from an older release 16:17:52 we don't have anything like... holy shit, the name's escaping me. 16:18:02 kexec. to try a new kernel live 16:18:07 i never has such isolated cat command problem 16:19:47 I'm supprised that 12.3 to 14.1 did work so well, but well, you only tested sh, ldd and cat? 18:36:14 remiliascarlet: so did changing BusID help?