Is CRT Burn-In Still a Problem?
coloth asks: "We've all been told for many years that monitor burn-in is a thing of the past, that CRTs use a different kind of phosphor now, and that screensavers are more toys than practical safeguards. After a few minutes with Google, nearly every PC advice site I found said as much. Well, I just realized tonight that I've got burn-in from the Seti@Home screensaver on my Dell P991. I took a picture with my digital camera. (disregard the bar of interference) I added the arrows with PhotoShop and enhanced the image a bit, but the burn in is clear. Here is the image of the "screensaver" to compare the pattern. Is my monitor sub-par? Is the conventional wisdom about burn-in untrue? Are most people doing anything specific to avoid burn-in?"
Even on old world machines (beige G3 etc) Mac OS X ignores the GUI code in the ROM as it is a completely different architecture (QuickDraw rather than Quartz) and it would be pretty impossible to use from a Unix environment anyway.
Logging in as >console drops you into a text console. No GUI. Is that so hard for you to believe? If you hold down command+v, Mac OS X will boot in verbose mode ie. it dumps pages of text to the console just like linux does. Command+s will boot you into single user mode, which is sh with nothing else running and / mounted as read only.
Here's a trick: install XFree86, login as >cosnole, run startx. No Apple GUI code in sight. Hell, if you had half a clue you'd know that Apple releases Darwin free without Quartz et al. The console is all you have unless you install XFree86.