dagorn@cicb.fr (Francois Dagorn) (11/08/90)
Problem with NCD X terminals and fonts : I have an NCD X terminal and fonts need to charged using tftp. My local installation of X reside in /usr/local/X11R4 (lib,bin,include,man). NCD indicates to make link to lead to /usr/lib/X11/ncd so i tried : ln -s /usr/local/X11R4/lib /usr/lib/X11/ncd /usr/lib/X11 is yet a link to /usr/local/X11R4/lib tftp cannot find any fonts ! So i moved the fonts in /usr/spool/tftp/fonts and now the xset command runs well but it's not convenient because i have a duplicated fonts hierarchie. ( and when booting the fonts are not found). Does any NCD customer have fixed this problem ? Thank's.
klein@ncd.COM (11/11/90)
(Forgive the wasted bandwidth of this response if you're not interested in how an NCD X terminal reads fonts. It's just that this seems to be a FAQ in the last few weeks, so I'm cc'ing xpert. If you don't care, press delete now.) >I have an NCD X terminal and fonts need to charged using tftp. My local >installation of X reside in /usr/local/X11R4 (lib,bin,include,man). NCD >indicates to make link to lead to /usr/lib/X11/ncd so i tried : >ln -s /usr/local/X11R4/lib /usr/lib/X11/ncd >/usr/lib/X11 is yet a link to /usr/local/X11R4/lib >tftp cannot find any fonts ! An NCD can read fonts either via TFTP, NFS, or DAP (for DECnet worlds). By default it will use TFTP, and the default path will be built-ins,/usr/lib/X11/ncd/fonts/{misc,100dpi,75dpi} Assuming you stay with TFTP the most common problems you will run into are a) TFTP is not enabled on the host, b) TFTP is enabled but set in either 'secure' or 'restricted' mode, (SunOS vs. Ultrix), or c) you will have so much TFTP traffic that inetd goes casters to the sky. To solve (a), check in /etc/inetd.conf, (the most common place), and verify that the line for TFTP is not commented out, i.e., does not begin with a '#'. If it does, delete the character. If the problem is (b), then the TFTP line in inetd.conf will end with something like '-s /tftpboot', or '-r /tftpboot'. To solve this problem either remove this string entirely, or place the font files under this heirarchy. Note! Secure/restricted TFTP *does not* follow symbolic links! (Actually someone posted this somewhat convoluted scheme that does allow this about a year ago, but I forget the exact trick, and besides it just seemed rather weird to me.) In either (a) or (b), don't forget to let the inetd know that you've been adjusting his configuration file. A 'kill -1 <pid_of_inetd>' should suffice. To solve the busy inetd problem I have seen people resort to a stand-alone TFTP daemon. If you would like more information on this, contact 'support@ncd.com'. If you wish to use NFS for fonts, you will need a remote configuration file for your NCD. This file can be loaded either via TFTP or NFS, and (in addition to numerous other configuration values) contains the 'mount' command for the font file structure. (Note that since this file does the NFS mounting, using NFS to read it requires that it really exist in /usr/lib/X11/ncd/configs on the host, since that is what the terminal will auto-mount at boot time. Have to start somewhere, after all :-). In your case, for example, the config file could contain a line like: nfs-file-systems = <host_name_or_IP>:/usr/local/X11R4/lib /usr/lib/X11/ncd to get fonts in the right logical place. Hope this helps. For more information you can always contact us directly at 'suport@ncd.com'. Doug klein@ncd.com