In article <20250722163315.ec599b2f...@viking.prd.co.uk>,
Steve Blinkhorn <st...@prd.co.uk> wrote:
>For over 10 years I have run our office network with a clutch of
>'nettop'-style machines with specific roles but overlapping
>capabilities, so that any one machine can die without affecting
>overall functionality.  One of these, running NetBSD 7.0, repeatedly
>fails to boot multi-user: it's main role was to run Xvnc to provide
>access to the network of NetBSD machines to PC workstations.  This
>arrangement has worked very well, so well I had not looked at how it
>was set up for years.
>
>So I switched the service over to an identical machine whose
>principal role was to provide outward-facing services: mail, named
>etc.  It appeared at first to be a seamless transition, until I saw
>that characters typed into an xterm were echoed horizontally offset to
>the right, so were largely unreadable.  Characters programatically
>output to the screen are rendered correctly.  I use lucidatypewriter
>as my STD_FONT, 18 point in deference to my presbyopia.  A fix for
>this would be really helpful.
>
>So I turned to a NetBSD 9.2 box, and here I hit a different problem.
>Using Xvnc as started by the same vncserver script as before, I get
>the right screen dimensions (1920x1080) but not the font I want or the
>size I want.  It looks like there was a major reorganisation of fonts
>some time between 7.0 and 9.2, with more layers of configuration.  How
>do I specify th lucidatypewriter font I want (it's there, I can see it
>through xlsfontas, but I don't get told where it is in the
>filesystem).
>
>Finally, with native X on 9.2, despite specifying a geometry of
>1920x1080 in my startx script, I get a 1024x768 display.  Why?
>
>I'm about to replace all my old machines but need to feel properly in
>controld when I do.
>
>BTW, all machines amd64.

use 'xset q' to query your font path and then see if the bitmap fonts
(75dpi/100dpi) are before or after the Type1 fonts.
Why font are you trying to use?

christos

Reply via email to