I tend to do my graphical administration remotely.
# First make sure your workstation allows X connections
# from your server
bob@workstation $ xhost <server's ip address or name>
# Then connect to your server
bob@workstation $ ssh <server>
# Tell the server where to send your X gui widgets
bob@server $ export DISPLAY="<workstation's IP or name>:0.0"
# become root
bob@server $ su
# run your gui tool
root@server # red-carpet
The red-carpet gui then displays on my workstation.
In this example, the X server daemon only needs to
be installed on the workstation, not on the server.
On Wed, 23 Oct 2002, William Lindley wrote:
> On Wed, 23 Oct 2002, Mike Starke wrote:
> > If it is a server, why have X installed?
>
> in general, is it still considered a Bad Idea to run X on a server,
> despite all the easy graphical administration tools, Kups for printers
> just to name one?
>
> "Don't run X on a server" seems a kinda mid-'90s attitude, or am I wrong?
>
> \\/
>
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> To subscribe, unsubscribe, or to change you mail settings:
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
----------------------------------------------------------------------
"Any data that's public, and that Google can see, is hardly worth
storing and organizing. We simply search for what we need, when we
need it: just-in-time information management." - Jon Udell
----------------------------------------------------------------------
(text/plain)