Path: utzoo!attcan!uunet!wuarchive!mailrus!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: Configuring X on an Apollo
Message-ID: <1990Aug7.191049.15920@terminator.cc.umich.edu>
Date: 7 Aug 90 19:10:49 GMT
References: <1990Aug6.223445.32172@eagle.wesleyan.edu> <1990Aug7.142135.19679@ncsuvx.ncsu.edu>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 24

In article <1990Aug7.142135.19679@ncsuvx.ncsu.edu>, jwb@cepmax.ncsu.EDU
(John W. Baugh Jr.) writes:
  It appears that to run both X and DM software we have to use
  Xapollo.  If this is indeed the case, is it possible to make
  X the default environment instead of DM?

I'm not sure what you mean by "default environment."  Here's what I do.

I run Xapollo and the DM both, with X owning the root (Xapollo s+r+).  The
DM handles logging in, which shouldn't be too big a burden on your X users.
The dm login startup file (/sys/dm/startup_login*) does not start a shell of
any kind, it just cmdfs user_data/startup_dm*.

DM users can put a 'cp /bin/csh' in their startup_dm file if they want. My
startup_dm contains this line:

    cpo /bsd4.3/bin/csh '.xsession';wdf

You can change the 'csh' to 'sh' if you want.  Then .xsession contains all
the normal stuff like xterm & twm.

You still have to logout the DM way.  Again, I don't think this is a
terribly big burden.  You could even fix this with a strategically places
"xdmc LO", but note that xdmc needs to run in a pad (what a lose).