[K12OSN] Custom XF86Config

Jim McQuillan jam at mcquil.com
Fri Feb 25 14:24:54 UTC 2005


Your custom config file goes in /opt/ltsp/i386/etc

When the client boots, it copies your custom file to /tmp on the client,
which is a ramdisk, so it's only visible to the client.

When the copy is made, it's clled 'XF86Config.1', because if you have
multiple SCREEN_xx lines setup, each one will have it's own config file.

You can make sure that /tmp/XF86Config.1 is the same as your custom
file, by setting:

    SCREEN_01 = startx
    SCREEN_02 = shell

Then, once X is up and running, hit Ctrl-Alt-F2, and switch to the text
screen, and take a look at /tmp/XF86Config.1 using 'more'.

Hope that helps,
Jim McQuillan
jam at Ltsp.org

On Fri, 25 Feb 2005, Jim Kronebusch wrote:

> > > Thanks, I did that.  Set XSERVER = ati, now it starts to
> > load x, says
> > > it is using /tmp/XF86Config.1, then fails.
> >
> > is the custom file named .1 or .indigo ??
> > try creating /opt/ltsp/i386/etc/X11 and put the file there??
> It is named .indigo which makes me question why I see stuff about
> /tmp/XF86Config.1, should my custom file be in the tmp?  If you know any
> way to verify from the client it grabbed the custom file let me know.
> Thanks,
> --
> This message has been scanned for viruses and
> dangerous content by the Cotter Technology
> Department, and is believed to be clean.
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>

More information about the K12OSN mailing list