On Fri Dec 30, 2022 at 3:59 PM CET, vitmaubra@gmail.com wrote:
> Thank you guys for the tips. I think naddy is right, which means I was
> wrong in thinking that I finally had a doubt that couldn't be solved
> by OpenBSD's manuals. I'll do some tests and report back on this
> thread soon.
Don't forget to check firewall as NFSv4 from your Fedora 34 has
way less requirements then NFSv3 served by OpenBSD
You can compare 'rpcinfo -p localhost' on your OpenBSD server
vs same command remotely from client (with proper hostname/IP)
And NFSv3 is by default UDP while NFSv4 is TCP
>
> Best,
> Vitor
>
> Em qui., 29 de dez. de 2022 às 16:55, Christian Weisgerber
> <naddy@mips.inka.de> escreveu:
> >
> > "vitmaubra@gmail.com":
> >
> > > My /var/log/daemon regarding the issue:
> > > mountd[91001]: Refused mount RPC from host 192.168.1.4 port 57264
> >
> > The client's mount request didn't come from a reserved port, i.e. <1024.
> > OpenBSD's mountd(8) does not accept this.
> >
> > --
> > Christian "naddy" Weisgerber naddy@mips.inka.de
Friday, December 30, 2022
Re: go syscall/error/ioctl numbers etc.
On 22-12-19 00:49:53, Joel Sing wrote:
> On 22-12-15 13:15:58, Stuart Henderson wrote:
> > golang.org/x/sys/unix/zerrors_openbsd_* and friends are seriously out
> > of date on some archs; zerrors for 386 must have been generated on
> > openbsd 5.7 or earlier; arm and amd64 somewhere between 5.8 and 6.0.
> > (I bumped into this trying to build something which wants O_CLOEXEC
> > but fails on i386).
> >
> > How can we go about getting these updated upstream so that there's a
> > chance they'll eventually trickle down to projects using vendored copies?
>
> Thanks - I'll look at respinning and upstreaming them in the coming weeks.
This has been done:
https://go-review.googlesource.com/c/sys/+/459499
> > Here are diffs against the current files for i386 to give an example of
> > how far they've diverged.
> >
> > I have updated files for i386/amd64 and will soon have them for aarch64
> > if they're any use...
> On 22-12-15 13:15:58, Stuart Henderson wrote:
> > golang.org/x/sys/unix/zerrors_openbsd_* and friends are seriously out
> > of date on some archs; zerrors for 386 must have been generated on
> > openbsd 5.7 or earlier; arm and amd64 somewhere between 5.8 and 6.0.
> > (I bumped into this trying to build something which wants O_CLOEXEC
> > but fails on i386).
> >
> > How can we go about getting these updated upstream so that there's a
> > chance they'll eventually trickle down to projects using vendored copies?
>
> Thanks - I'll look at respinning and upstreaming them in the coming weeks.
This has been done:
https://go-review.googlesource.com/c/sys/+/459499
> > Here are diffs against the current files for i386 to give an example of
> > how far they've diverged.
> >
> > I have updated files for i386/amd64 and will soon have them for aarch64
> > if they're any use...
Subscribe to:
Posts (Atom)