🚀 go-pugleaf

Dan Pop (Dan.Pop@mail.cern.ch) wrote:
: In <adtDCACx8.CvJ@netcom.com> adt@netcom.com (Anthony D. Tribelli) writes:
: The X stuff comes directly from the XFree86 people...
: Once again for the boneheads: this is not a Linux issue...
: It's not Slackware, it's a contributed script which builds the configuration
: file for you...

Who cares who wrote a piece of code or script. This is just finger
pointing to avoid the blame. The complete product, in this case: linux,
Slackware 2.3 (July 95) distribution, has a crude installation and does
not always work.

Once again, try to recognize that I am talking about a product called
linux, not the kernel programming project called linux. 

: ... And the refresh rates are required by the X server (which
: is _not_ Linux specific) in order to protect you from frying your monitor.
: Both Windows and the Mac will happily fry your monitor if it doesn't
: support the refresh rates used by the graphics card.  Guess who got it
: right?

Windows and Mac. They quite successfully configure hardware without 
frying monitors and without requiring users to dig through technical 
documentation.

: The X server simply couldn't care less about your monitor's specs, if
: it weren't for your own protection.  There is no way for the server to
: query the monitor about its specs, so you have to supply this data 
: yourself.

Actually the X development team doesn't have the resources or talent to 
provide a more reasonable installation like Windows or Mac. Their 
solution is to pass the hard stuff off to the user.

Tony
-- 
------------------
Tony Tribelli
adtribelli@acm.org