Date: Mon, 30 Sep 2024 13:14:05 +0000 From: bugzilla-noreply@freebsd.org To: jail@FreeBSD.org Subject: [Bug 281751] Unable to start jail from vty1... virtual terminal Message-ID: <bug-281751-29815-XJSqoFa9MI@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-281751-29815@https.bugs.freebsd.org/bugzilla/> References: <bug-281751-29815@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D281751 Olivier Certner <olce@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Assignee|jail@FreeBSD.org |olce@FreeBSD.org Status|New |Closed --- Comment #39 from Olivier Certner <olce@FreeBSD.org> --- (In reply to Alex Tutubalin from comment #36) Ok, so all is well and good... You can't reproduce the problem on 13.3, but= on 14.1 and 14.1-p5. I was just wondering how you could reproduce on a recent 15-CURRENT (main-n272495-6a4f0c063718), which has the pam_xdg(8) fix, but from comment= #28 and comment #29 I infer that you only installed the new kernel but not the associated world, which indeed explains. So, this problem is already fixed on -CURRENT and 14-STABLE, and the fix wi= ll appear in 14.2-RELEASE. That said, I will think about some followup commits (such as having jexec(8) automatically close all FDs being directories, or print something) because = it is hard for users to diagnose such problems on their own. --=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-281751-29815-XJSqoFa9MI>