Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!lll-winken!quintro!kts From: kts@quintro.uucp (Kenneth T. Smelcer) Newsgroups: comp.sys.apollo Subject: Re: X Keybindings Keywords: emacs keybindings Message-ID: <1990Mar4.200610.603@quintro.uucp> Date: 4 Mar 90 20:06:10 GMT References: <612@software.software.org> <48f1134c.20b6d@apollo.HP.COM> <1606@cernvax.UUCP> Reply-To: kts@quintro.UUCP (Kenneth T. Smelcer) Organization: none Lines: 34 In article <1606@cernvax.UUCP> achille@cernvax.UUCP (achille petrilli) writes: >In article <48f1134c.20b6d@apollo.HP.COM> oj@apollo.hp.com writes: >>to /etc/daemons/xdm . Please don't be tempted to try xdm on sr10.2...... >>unless you like debugging your node what we call the Phase II shell. >>As Mr. Wizard sometimes says on TV, "Don't Try This At Home, Kids!" >> >>/Ollie Jones (speaking for myself, not necessarily for HP) > >Could you tell me why I shouldn't try to use xdm under >sr10.2 ? > [ Achille ran xdm on a dn2500 without problems ] >Achille Petrilli 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. What I think Ollie is talking about is that if you have a problem with the node's software, you have two choices. You either have to fix it across the network, or bring the node up in service mode and use the Phase II shell to figure out what's wrong. I don't consider this a serious problem, because if the DM setup was messed up, you'd still only have two choices. You just have to be careful. One question: is there any way to start up DM without it creating the standard login pads? I'd like it to work like the X server does now, just running as a standard background task. Any ideas? -- --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- Ken Smelcer Glenayre Corp. quintro!kts@lll-winken Quincy, IL tiamat!quintro!kts@uunet