> Date: Fri, 3 Jan 2020 20:18:46 +0100 > From: Klemens Nanni <k...@openbsd.org> > > On Fri, Jan 03, 2020 at 08:04:10PM +0100, Mark Kettenis wrote: > > No. If you messed this up in a previous commit, please fix it some > > other way. > The purpose of this diff is not to fix previously messed up spacing but > to omit information that I consider redundant by now since the `console' > available. > > At e2k19 I added printing the vcctty first, then the console command > followed. In hindsight, printing it could have been skipped right away, > but well... didn't occur to me earlier. > > vmctl does not print the device either, I just don't see a reason to do > it in ldomctl anymore.
The way I see it, "ldomctl console" is just there for compatibility with vmctl. We don't really need it for sparc64 as the random allocation of ttys that vmm(4) suffers from doesn't happen (and there are interesting user permission issues that we discussed a few weeks ago). I continue to use "cu -l ttyV2" as I'm used to it (and it takes less typing). But occasionally I need to refresh my memory about the tty assigned to my domains.