Date: Wed, 20 Oct 2021 15:47:29 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 259319] openpty(3) and forkpty(3) don't work under Linux compat Message-ID: <bug-259319-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259319 Bug ID: 259319 Summary: openpty(3) and forkpty(3) don't work under Linux compat Product: Base System Version: 13.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: jmmv@FreeBSD.org Created attachment 228888 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D228888&action= =3Dedit Small repro program that uses openpty Linux binaries that call into openpty(3) or forkpty(3) get "No such file or directory" as a result of these calls. This is in combination with linux_base-c7-7.9.2009. I've found this issue while trying to run the VSCode remote server under Li= nux compat, but I have attached a trivial repro program that shows the issue. I have loaded the pty kernel module. One thing I've found is that these calls are trying to open /dev/ptmx, wher= eas this device is under /dev/pts/ptmx on Linux. However, by looking at the gli= bc sources, it seems as if the lack of ptmx is a non-fatal error, as the code = then falls back to opening /dev/ptyp0. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259319-227>