From: Tim Chase <blinux.list@thechases.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: Running X w/o X (Oracle client install)
Date: Thu, 09 Sep 2004 07:55:16 -0500 [thread overview]
Message-ID: <414052B4.7050406@thechases.com> (raw)
In-Reply-To: <6.0.1.1.2.20040908164302.01b02d28@wiscmail.wisc.edu>
If you have a couple options for satisfying a need for X.
1) If you want to send things remotely to the machine from which
you're SSH'ing, you need an X server running on your local
machine. There have been steps taken by the Cygwin folks to get
this working in Windows, but I've not tried it. Last time I
tried this, I used a non-free package by the name of Reflection
to provide an X server under Windows.
2) If you really need to connect to an X server, but don't have a
"real" X server, you can configure X to use the "Xvfb" driver
which creates a virtual frame-buffer. This would be, as your
"subject" line suggests "X without X." From the man page:
"Xvfb is an X server that can run on machines with no display
hardware and no physical input devices. It emulates a dumb
framebuffer using virtual memory."
I recommend against simply finding some random machine proving an
X server over which you have no control and just setting your
DISPLAY variable to point at it, as things may get displayed to
that machine without notifying you. Or there may be security
concerns if it provides some sort of administrative dialog that
comes to the person sitting in front of the X display rather than
coming to you.
3) You might be able to get away without X at all, if the Oracle
program/install in question has some obscure option (like Vim
does) to forego detection of X. You'd have to check out their
documentation on this to see if they provide such an option.
4) Lastly, if getting "Xvfb" set up is a problem, but your
install automatically can configure a regular X setup, just let
it start, and then use ctrl+alt+F1 to get back to your first
virtual console. X will run in the background, making Oracle
happy, (and slupring down a few system resources, but it
shouldn't be too bad) yet you have your regular console interface
at VC 1 through whatever.
Hope this helps,
-tim
prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Perfectly accessible Audio production solution for Linux Mario Lang
` Running X w/o X (Oracle client install) John Heim
` hank smith
` John Heim
` Willem van der Walt<willem@top.health.gov.za>
` Tim Chase [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=414052B4.7050406@thechases.com \
--to=blinux.list@thechases.com \
--cc=blinux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).