The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Early GUI on Linux
Date: Sat, 25 Feb 2023 17:39:13 -0700	[thread overview]
Message-ID: <CANCZdfrmiq0qxKxrEWVAwTa5RjNG_Tq-9JATAA7qR2=cva_4+w@mail.gmail.com> (raw)
In-Reply-To: <58626A0B-EF9C-4920-8E20-CE0C4210BA6A@planet.nl>

[-- Attachment #1: Type: text/plain, Size: 2339 bytes --]

On Sat, Feb 25, 2023, 2:31 PM Paul Ruizendaal <pnr@planet.nl> wrote:

>
> I think discussion of early Linux is in scope for this list, after all
> that is 30 years ago. Warren, if that is a mis-assumption please slap my
> wrist.
>
> Following on from the recent discussion of early workstations and
> windowing systems, I’m wondering about early windowing on Linux. I only
> discovered Linux in the later nineties (Red Hat 4.x I think), and by that
> time Linux already seemed to have settled on Xfree86. At that time svgalib
> was still around but already abandoned.
>
> By 1993 even student class PC hardware already outperformed the
> workstations of the early/mid eighties, memory was much more abundant and
> pixels were no longer bits but bytes (making drawing easier). Also, early
> Linux was (I think) more local machine oriented, not LAN oriented. Maybe a
> different system than X would have made sense.
>
> In short, I could imagine a frame buffer device and a compositor for
> top-level windows (a trail that had been pioneered by Oriel half a decade
> before), a declarative widget set inspired by the contemporary early
> browsers and the earlier NeWS, etc. Yet nothing like that happened as far
> as I know. I vaguely recall an OS from the late 90’s that mixed Linux with
> a partly in-kernel GUI called “Berlin” or something like that, but I cannot
> find any trace of that today, so maybe I misremember.
>
> So here are a few things that I am interested in and folks on this list
> might remember:
>
> - were there any window systems popular on early Linux other than X?


No. Mgr was available but harder to setup than X. This is from like 0.98pl5
or so days, so very early on...

- was there any discussion of alternatives to X?
>

Discussions yes. But not much more than talk.

There were vgalib apps that ran graphics on the console, but I never used
them.

- was there any discussion of what kernel support for graphics was
> appropriate?
>

Some. But mostly it was to switch graphics modes between x11 and console
apps. Very little beyond that.

By the time Linux arrived, x11 had already won in the workstation space, so
the quick push was to get x11 going. It wasn't long before everything was
XFree86 (or XFree98 if you were in Japan).

Warner

>

[-- Attachment #2: Type: text/html, Size: 3395 bytes --]

  parent reply	other threads:[~2023-02-26  0:39 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 [this message]
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
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='CANCZdfrmiq0qxKxrEWVAwTa5RjNG_Tq-9JATAA7qR2=cva_4+w@mail.gmail.com' \
    --to=imp@bsdimp.com \
    --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).