The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: [TUHS] Re: Early GUI on Linux
Date: Sat, 25 Feb 2023 21:40:34 -0500	[thread overview]
Message-ID: <Y/rGop0y22X9Dcxd@mit.edu> (raw)
In-Reply-To: <58626A0B-EF9C-4920-8E20-CE0C4210BA6A@planet.nl>

I think it's fair to say that in the very early days of Linux, most of
the people who were using it were people who kernel hackers; and so we
didn't have all that many people who were interested in developing new
windowing systems.  We just wanted to be able to have multiple xterms
and Emacs windows.

In fact, support for X Windows predated the development of a
networking stack; we had Unix domain sockets, so that was enough for
X, but we didn't have a working networking stack at that point!  I
would be running X, and then running C-Kermit to download files from
MIT over a dialup modem.

At that point, X windows wasn't *flaky* per se, but remember that back
then monitors were very persnicky about exactly what resolutions and
frequences they would accept.  And this was before monitors supported
EDID (Extended Display Identification Data), which allowed the X
server to figure out what the parameters were of the monitor.  So that
meant that configuring the X server with the correct resolution,
frequencies, etc., was tricky.  There were long and complex documents
explaining how to do it, and it was a very manual process.  If you got
the calculations wrong, the image might not be stable, but that wasn't
a software bug so much as it was a configuration error.

There were programs (for example, the most famous was the graphical
game "Tuxracer") which wrote directly to the frame buffer, but there
wasn't anyone who was interested in developing their own compositor.
We just wanted xterms and (later) Firefox to work!

As far as discussion about what should and shouldn't go into the
kernel, most people agreed that as much as possible, especially in
graphics land, should be out of the kernel.  The fact that we didn't
have a lot of graphics specialists in the kernel development
community, and that in those early days the vast majority of Linux
boxen where single user machines just sealed the deal.

   	       	      	  	  	  - Ted

  parent reply	other threads:[~2023-02-26  2:40 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-25 21:31 [TUHS] " Paul Ruizendaal
2023-02-25 22:49 ` [TUHS] " Dan Cross
2023-02-26  1:27   ` Larry McVoy
2023-02-26  0:39 ` Warner Losh
2023-02-26  1:14   ` Steffen Nurpmeso
2023-02-26 15:50   ` Leah Neukirchen
2023-02-26 16:13     ` Larry McVoy
2023-02-26 16:23       ` Leah Neukirchen
2023-02-26 16:32         ` Warner Losh
2023-02-26 16:39         ` Will Senn
2023-02-26 19:58       ` Dave Horsfall
2023-02-27  0:16         ` Adam Thornton
2023-02-27 10:09       ` Ralph Corderoy
2023-02-26  2:21 ` Jonathan Gray
2023-02-27 17:22   ` Paul Ruizendaal
2023-02-27 18:32     ` Warner Losh
2023-02-26  2:27 ` Will Senn
2023-02-26  2:30 ` Will Senn
2023-02-26  2:40 ` Theodore Ts'o [this message]
2023-02-26  3:28   ` Dan Cross
2023-02-26  3:45     ` Warner Losh
2023-02-26  5:24   ` John Cowan
2023-02-26  5:36     ` Steve Nickolas
2023-02-28  3:35     ` Dave Horsfall
2023-02-27 17:22   ` Paul Ruizendaal via TUHS
2023-02-27 17:59     ` Arno Griffioen via TUHS
2023-02-27 18:07     ` Warner Losh
2023-02-27 20:04     ` [TUHS] Generational development [was Re: Re: Early GUI on Linux] arnold
2023-02-27 20:08       ` [TUHS] " Chet Ramey
2023-02-27 20:22         ` arnold
2023-02-27 20:46           ` segaloco via TUHS
2023-02-27 21:04             ` Dan Cross
2023-02-28  7:59             ` arnold
2023-02-28 15:28               ` Clem Cole
     [not found]                 ` <CAP2nic1STmWn5YTrnvFbexwwfYWT=pD28gXpVS1CVSfOOwxx7g@mail.gmail.com>
2023-02-28 15:50                   ` [TUHS] Fwd: " Adam Thornton
2023-02-27 20:50           ` [TUHS] " Chet Ramey
2023-02-27 20:55             ` Bakul Shah
2023-02-27 21:01               ` segaloco via TUHS
2023-02-27 21:15                 ` Chet Ramey
2023-02-27 21:22                   ` Dan Cross
2023-02-27 20:30     ` [TUHS] Re: Early GUI on Linux Dan Cross
2023-02-28  1:10       ` Alexis
2023-02-28  1:27         ` Dan Cross
2023-03-01 16:39       ` Paul Ruizendaal
2023-03-01 16:54         ` Larry McVoy
2023-03-01 17:22           ` Paul Ruizendaal
2023-03-01 17:52             ` Larry McVoy
2023-03-02  1:17               ` Jonathan Gray
2023-03-02  4:28               ` Larry McVoy
2023-03-02  6:46                 ` [TUHS] X timeline Lars Brinkhoff
2023-03-01 18:59         ` [TUHS] Re: Early GUI on Linux Theodore Ts'o
2023-03-02  7:27         ` arnold
2023-02-28  1:08     ` Jonathan Gray
2023-02-28  1:15       ` Clem Cole
2023-02-27 20:56 ` Will Senn
2023-02-27 22:14   ` Andru Luvisi
2023-02-27 22:31   ` David Arnold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Y/rGop0y22X9Dcxd@mit.edu \
    --to=tytso@mit.edu \
    --cc=pnr@planet.nl \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).