Re: vax wscons setting questions

[Hans Rosenfeld <hans%netbsd.org@localhost>]

On Sun, Feb 04, 2024 at 11:13:45PM +0900, Izumi Tsutsui wrote:
> > I have never given a thought to the fact that I need to add new entries 
> > in /dev for new devices, it has always been a natural thing to do, 
> > wscons or not, but it might be that people expect a devfs to be present 
> > these days.
> 
> Note vax still use ttyw0 (at least in src/etc/etc.vax/ttys) for
> wscons ttys, but it looks other ports have switched to using
> ttyE[0-7] rather than ttyw[0-7] for wscons (actually wsdisplay) ttys:
> 
>  http://cvsweb.netbsd.org/bsdweb.cgi/src/etc/etc.i386/Attic/MAKEDEV.diff?r1=1.64&r2=1.65
> >> change wscons tty names to ttyE* to avoid clashes with the pty namespace
> 
> I think we no longer use pty in /dev (using ptyfs instead)
> so there is no conflict, but I wonder if it's worth for vax
> to use ttyE[0-7] for wscons in ttys(5) and remove "vt0" target
> for ttyw[0-7] from MAKEDEV.

I don't know what VAX model you're using, but my 4k90 uses ttyE[0-7] for
wscons. All ttyw[0-7] are commented out in /etc/ttys, but then there's a
comment above those indicating they are for VAXstation 3100
framebuffers?

Hans


-- 
%SYSTEM-F-ANARCHISM, The operating system has been overthrown