From: Will Senn <will.senn@gmail.com>
To: Leah Neukirchen <leah@vuxu.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Early GUI on Linux
Date: Sun, 26 Feb 2023 10:39:04 -0600 [thread overview]
Message-ID: <78FBC005-1DA2-4D08-89A2-5E8DE30436C5@gmail.com> (raw)
In-Reply-To: <874jr8s8ee.fsf@vuxu.org>
Same here. The virtual terminals worked for me (and still do) until I start doing ssh, then screen and tmux are lifesavers.
Will
Sent from my iPhone
> On Feb 26, 2023, at 10:23 AM, Leah Neukirchen <leah@vuxu.org> wrote:
>
> Larry McVoy <lm@mcvoy.com> writes:
>
>>> On Sun, Feb 26, 2023 at 04:50:34PM +0100, Leah Neukirchen wrote:
>>> Warner Losh <imp@bsdimp.com> writes:
>>>
>>>> - 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.
>>>
>>> Back then I didn't have enough disk space to install X11 and TeX at
>>> the same time, so I mostly worked on the 80x25 console
>>
>> screen(1) was my go to back in the days of limited resources. Especially
>> screen -r so you could detach, come back the next day and have all your
>> setup right there.
>>
>> Wasn't that fancy but oh so useful. I'm with Ted in that we just wanted
>> a bunch of terminal windows.
>
> Curiously, I learned about screen only way later, when I used remote
> systems. But I made getty spawn on 12 ttys, so that worked as well to
> multitask.
>
> --
> Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org
next prev parent reply other threads:[~2023-02-26 16: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
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 [this message]
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=78FBC005-1DA2-4D08-89A2-5E8DE30436C5@gmail.com \
--to=will.senn@gmail.com \
--cc=leah@vuxu.org \
--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).