Path: utzoo!attcan!uunet!samsung!umich!terminator!citi.umich.edu!dpg
From: dpg@citi.umich.edu (David Gorgen)
Newsgroups: comp.sys.apollo
Subject: Re: X Keybindings
Keywords: emacs keybindings
Message-ID: <1990Mar5.153742.11052@terminator.cc.umich.edu>
Date: 5 Mar 90 15:37:42 GMT
References: <612@software.software.org> <48f1134c.20b6d@apollo.HP.COM> <1606@cernvax.UUCP> <1990Mar4.200610.603@quintro.uucp>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: dpg@citi.umich.edu (David Gorgen)
Organization: Hewlett-Packard/Apollo
Lines: 34

In article <1990Mar4.200610.603@quintro.uucp> kts@quintro.UUCP (Kenneth T. Smelcer) writes:
> I've been running my dn3000 (10.2) using xdm in an X only environment
> for a couple weeks now, without any problems.  The X11R4 apollo documentation
> actually states that using xdm is the only way to run R4 on Apollo/HP 
> workstations, but it is an unsupported way to do things.

I wrote that man page, and that isn't what I meant to say.  Perhaps I wasn't
clear enough.  Here is the relevant excerpt:

    Xapollo now can operate in place of the Apollo Display Manager, as well
    as from within the DM (as in the past).  Standalone operation should be
    achieved via use of the xdm (1) client.  The xdm (1) program has many
    configuration options, and the defaults may not work for your
    environment; please read its man page before trying this.

    The following discussion explains how to set up a node for standalone X.
    Please note that Apollo does not officially support running systems
    without the Display Manager.  You may have difficulties in following
    these instructions; if so, you're on your own.

I didn't mean "Standalone operation should be achieved via use of xdm" to say
that only standalone operation is recommended.  What I could have added to
emphasize the fact that Xapollo will still run as before (from within the DM
environment) is that using the xinit (1) program is the best way to do that.

As Ollie has already said, the obstacles to official support of a no-DM
environment are more organizational (documentation, support staff training)
than technical.  (In my personal opinion, of course.)  I have been personally
running a no-DM SR10.2 node with pre-release and released X.V11R4 for three
months, with no problems.
--
Dave Gorgen / GTD-East (formerly Apollo Computer), Hewlett-Packard Company
located at:  University of Michigan, CITI          dpg@citi.umich.edu
(Center for Information Technology Integration)    313-998-7482 or -7479