| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2248.1 | | MIPSBX::thomas | The Code Warrior | Sun Feb 11 1990 17:11 | 3 |
| Just execute it.
# /usr/bin/Xqdsg
|
| 2248.2 | Restart after crashes | IOUONE::BRYSON | | Mon Feb 12 1990 17:48 | 8 |
|
Yes, but I would like it to restart when it crashes (of course, this will
never happen ;-)), but just in case... Execution by init from ttys is
what I am looking for.
Thanks,
David
|
| 2248.3 | Should be correct | SMURF::COUTU | He who will not risk, cannot win. | Tue Feb 13 1990 10:04 | 19 |
| Your first line:
:0 "/usr/bin/Xqdsg" none on secure
should work correctly. I use this constantly for running tests
against a 'bare' X server with no other X client applications
running. Be sure that you have the line in /etc/ttys for the
console device set to 'off' or else you'll have problems. Of
course this does assume that you're using a color VAX workstation.
If you have another type of workstation then you're using the
wrong X server.
Xqdsg = color VAX (except 3520/3540)
Xqdsm = mono VAX
Xcfb = color RISC
Xmfb = mono RISC
Xgb = 3520/3540 VAX
Dan
|
| 2248.4 | It works, but.... | IOUONE::BRYSON | | Wed Feb 14 1990 12:55 | 5 |
| Yes the line that I gave does work; however, I get a cycling init process
created when I use this line. I am trying to keep this cycling process from
being created.
David
|
| 2248.5 | | SMURF::COUTU | He who will not risk, cannot win. | Wed Feb 14 1990 17:33 | 8 |
| If your login screen is going away and coming back by itself then it is
a serious problem somewhere in your system. I'd suspsect that maybe
you have two init processes or else the line in /etc/ttys which starts
with 'console' is set to on as well as the line starting with ':0'.
This gives you dueling tty line processes. Check your setup, see if
you have more than one process named init.
Dan
|
| 2248.6 | Must know cpu type? | HPSRAD::KOMAR | You can't fool Nature | Wed Feb 14 1990 18:51 | 13 |
|
In an Ultrix environment, one needs to know what type of machine
(even what type of VAX, gasp) one is using before determining
what line to put in a file?
A bit more primative than I would have imagined.
Isn't there a better way?
(I don't manage any Ultrix systems, but I had that they would
be, uh, easier than these others...)
-pk.
|
| 2248.7 | | FLUME::dike | | Thu Feb 15 1990 07:45 | 3 |
| You need to know what kind of display hardware you have. That is the extent
of the dependency.
Jeff
|
| 2248.8 | | SMURF::COUTU | He who will not risk, cannot win. | Thu Feb 15 1990 11:20 | 16 |
| Re: .6
Well you pay your money and take your choice. ULTRIX doesn't have
shared libraries like VMS does so our executable images tend to be
larger. Large files on small workstations are not user friendly.
Therefore splitting one large X server into several smaller pieces
makes a lot of sense. You don't have to carry around the baggage of
things that you'll never use. Keep in mind that all of what we're
talking about doing in this note is non-standard use of DECwindows. The
installation process sets things up correctly for normal use and you
don't have to know about there being more than one X server unless
you're trying to do odd stuff like we're talking about.
Just because you don't agree with a design doesn't mean that it's wrong.
Dan
|
| 2248.9 | Field test software strikes again... | IOUONE::BRYSON | | Thu Feb 15 1990 12:58 | 8 |
| OK,
Apparently, my system was messed up for a while. After a reboot, the first
line from .0 worked fine (ah the life of field test).
Thanks,
David
|