Messages in this thread | | | Date | Sat, 28 Mar 1998 23:39:47 -0500 | From | Vagn Scott <> | Subject | Re: GGI and cli/sti in X |
| |
Linus Torvalds wrote:
> The "kill -9" problem is so trivial to fix that it's scary: you make a > small setuid binary that runs as root (and makes sure to drop the > original user by doing a "setuid()" as the first thing). It saves the > old graphics mode information, switches into graphics mode, does a > "fork()" and starts up X as a normal user in the forked process. > > The small root-owned process then stays around, does a "wait()" on the > child (the X server) and when the X server exits it restores the screen > and everything is hunky dory.
This, of course, is the challenge. If it can be done then the problem is solved.
NAME
shazam -- magically rationalise graphics cards
SYNOPSIS
shazam cardname graphics-program-name [ graphics-program-options ]
DESCRIPTION
Can only be run by root. It saves the current graphics card state information and forks graphics-progam-name with graphics-program-options. When graphics-program-name terminates, for whatever reason, shazam restores the graphics card to the same state it was in before graphics-program-name started.
EXAMPLE
shazam GoodCard xserver-GOOD -bpp 16 &
BUGS
Works well for GoodCard and VeryGoodCard2000. Fails miserable on any card that can be set into a state such that to leave that state you must know what state it is in. For such cards the knowledge that it was once in a particular state is not useful.
The cards for which shazam is not useful include: S3-yada-yada ATI-blah-blah some others
SEE ALSO
lart(8).
AUTHOR
Somebody with the specs, and the skills, and some free time.
-- _~|__ >@ (vagn( / \`-ooooooooo-'/ ^^^^^^^^^^^^^^^^^^
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |