https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285394
--- Comment #32 from Andriy Gapon <a...@freebsd.org> ---
(In reply to Andriy Gapon from comment #30)
I've done some additional experimenting and I see why ttyv0 helped me, but was
problematic for other other people.
I have a small customization in /etc/ttys where I disabled getty on ttyv0.
Just in case, my rationale for that is that I keep the first virtual terminal
for kernel / console messages. It would be inconvenient to have a shell session
there as any console messages would interfere with normal output. So, I just
avoid having getting there.
But I see that having a getty on ttyv0 can cause the same issue as init(8)
caused for /dev/console. That is, revocation of the terminal device when the
session leader on that terminal / virtual console terminated.
E.g., if I log in on ttyv0 and the logout, I see this:
2025 Apr 29 20:32:16 vgone vnode fffff803fd074000, ttyv0 rdev by login (67940)
kernel`vgone+0x2f
kernel`devfs_revoke+0x41
kernel`VOP_REVOKE_APV+0x71
kernel`killjobc+0x15a
kernel`exit1+0x707
kernel`0xffffffff808bd00d
kernel`amd64_syscall+0x189
kernel`0xffffffff80c4fbfb
So, ideally we do need a dedicated character device that could be used for
issuing VT_ ioctls but which would/could not be used as a terminal for any
program.
Internally it could be aliased to ttyv0, all is needed is to have a separate
devfs entry / vnode.
--
You are receiving this mail because:
You are the assignee for the bug.
