EHLO

250-Welcome to #FreeBSD.

250 Continue

EHLO

EHLO there

Doesn't generally work any more, but it was the traditional.

My system would reject that EHLO because the "there" is not a FQDN and does not resolve.

rwp: Right. Today. Back in the day servers would shrug and say "sure".

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.

remiliascarlet: if you haven't figured it out already, xorg.conf man page says BusID should be "PCI:<bus>:<device>:<function>", and in your output "pci0:1:0:0" there are domain (0), bus (1), device (0), and function (0).

yuripv: Then why does the FreeBSD handbook tell me to do "pci0:1:0:0" instead of "PCI:1:0:0"?

docs.freebsd.org/en/books/handbook/x11/#x-config At 5.4.3 example 6.

Pretty anal that I need to figure out that the handbook is wrong...

patches welcome

Hmmmm freebsdfoundation.org/contributing-freebsd-documentation

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

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.

what software are people typically using for viewing/reading epubs?

The general population ? Probably amazon / kindle. IME they have a monopoly over book content

nah, FreeBSD users.

as in: "on a freebsd system"

Not sure. Maybe evince

jbo: i check epub content with mupdf - but i don't use it to actually read it

thanks ridcully - good enough for me. mupdf plugin for zathura seems to work for that

Greetings

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 ?

(devfs is mounted)

sidh, so you have an interactive shell in chroot? One you can type and get results from?

yes

echo foo

That work?

most of command work, but cat throw that error

ldd `which cat`

echo foo work

And now I'm giving you a new command to run.

/bin/cat: libc.so.7 => /lib/libc.so.7 (0x801067000)

Just that one line?

sorry ( had a call )

yes cat: stdout: Function not implemented

No, I meant the ldd output.

CrtxReavr: yes no additionnal info

i get the prompt back after

I dunno. . . definitely a weird issue.

Is your world in sync with your kernel?

I agree

it is a boot environment created from sets (base/kernel/lib32)

directly

but the host from which i run chroot, show different patch level between -k and -u (freebsd-version)

Does the file exist? ls -l /lib/libc.so.7

-r--r--r-- 1 root wheel 1957560 May 31 08:36 /lib/libc.so.7

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.

ok will do that when the hypervisor will be less loaded

thank you Tabmow CrtxReavr

sidh: sounds like new binary on old kernel

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

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

kevans: once I boot on the new 14.1 BE, cat is running fine

sidh: right, that's not a supported configuration

new binaries will likely use new syscall, etc. that the old kernel cannot support

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

kevans: once booted on the 14.1 -release, I am using kernel and userland from 14.1 , right ?

I meant : once booted on the 14.1-R BE , sorry

assuming you created it correctly, yes

correct

I know now strange things can happen while chrooting a newer release from an older release

we don't have anything like... holy shit, the name's escaping me.

kexec. to try a new kernel live

i never has such isolated cat command problem

I'm supprised that 12.3 to 14.1 did work so well, but well, you only tested sh, ldd and cat?

remiliascarlet: so did changing BusID help?