Re: XF86Config???
On Thu, 27 Aug 1998, Stephen J. Carpenter wrote:
> On Thu, Aug 27, 1998 at 01:07:56AM -0500, Michael Shuey wrote:
> > > Well my FULL debian sparc system has xbase and xsun installed and..works
> > > fine with NO XF86Config file...and if I try to make one with xf86config
> > > it fails :(
> >
> > This is because Xsun is not technically a part of XFree86. It's generated by
> > the X Consortium's release of X. XFree just happens to include that source,
> > or at least the source of the last publically released version, so it is
> > possible to patch the code to make Xsun work with Linux/Sparc. Because of
> > this programs like xf86config (and xvidtune, XF86Setup, etc.) do not apply.
> > They only apply to XFree86, not to Xsun (or Xsgi, or any other servers that
> > can be built with that source).
>
> AHHHH that explains it :)
>
> > > How can I tell it NOT to use the local fontpaths compiled in and
> > > to use "inet/10.0.0.42:7100"
> > > (then eventually ::fingers crossed:: 7101 if I can get xfstt hacked up to u=
> > > se
> > > the proper endianess)
> >
> > RTFM :-) The Xsun man page (or the X man page, one of the two) documents the
> > command line option. Yes, your font path will be a command line option to the
> > X server. -fp 'tcp/10.0.0.42:7100' should do it, I think.
> > The trick now becomes getting the X server to recognize these options. If
> > you're starting your X server with startx, that's easy; use
>
> Nope no startx...
> X -query <host>
> right from /etc/inittab
Well, in that case, change inittab to
X -query <host> -fp 'tcp/1.2.3.4:1234'
(Or whatever)
Jules
/----------------+-------------------------------+---------------------\
| Jelibean aka | jules@jellybean.co.uk | 6 Evelyn Rd |
| Jules aka | jules@debian.org | Richmond, Surrey |
| Julian Bean | jmlb2@hermes.cam.ac.uk | TW9 2TF *UK* |
+----------------+-------------------------------+---------------------+
| War doesn't demonstrate who's right... just who's left. |
| When privacy is outlawed... only the outlaws have privacy. |
\----------------------------------------------------------------------/
Reply to: