Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Grant Taylor via COFF <coff@tuhs.org>
To: coff@tuhs.org
Subject: [COFF] Re: [TUHS] Re: the wheel of reincarnation goes sideways
Date: Wed, 5 Jul 2023 18:58:50 -0500	[thread overview]
Message-ID: <08ed6c3a-f2d3-590c-7de4-e01164271da1@tnetconsulting.net> (raw)
In-Reply-To: <CAEoi9W4ymJQ2EXxxM9vT9KjhW6i9z_rgYEFU9P0aC8-cru2iiw@mail.gmail.com>

On 7/5/23 4:48 PM, Dan Cross wrote:
> I thought some folks here might find this interesting.  Someone else
> today reminded me of tilde.town, which is a publicly accessible
> machine running Linux. They have a shocking amount of use:

O.o?

> tilde% hostname
> tilde.town
> tilde% uname -a
> Linux tilde.town 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13
> UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
> tilde% uptime
>   21:38:01 up 156 days, 17:15, 454 users,  load average: 3.82, 4.40, 4.19
> tilde%

Well I'll be.  Someone is running a multi-user Unix system.  That's 
something I've always wanted to do or find someone doing.

> Not quite a thousand users logged in simultaneously, but half that. If
> one counts the number of processes associated with pseudoterminals,
> it's more (I guess a lot of users are running tmux and/or screen).

:-)

> The system is also surprisingly modest: 6 cores, 16GiB of RAM and
> about 1TB of storage.

I can't yet tell if that's six logical CPUs or more.  x86_64 cores 
/could/ have hyper-threading et al. and more logical CPUs.

But still, six contemporary CPUs could be a lot of computing power.

16 GB of memory is nothing to sneeze at, especially for running commands 
in a CLI environment.  --  I'm assuming no daemons saying FEED ME RAM.

> It's surprisingly zippy.

I applied for membership.  I'll be interested to see if I'm granted 
logon permission.  :-)

Thank you for sharing Dan.



Grant. . . .

  reply	other threads:[~2023-07-05 23:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAP6exY+05fStBtpZGd2HeeNf21fNXeKUTwBV0h5-1YczwF+tew@mail.gmail.com>
2023-03-08 19:52 ` [COFF] Re: [TUHS] " Dan Cross
2023-03-08 20:18   ` [COFF] " Tom Ivar Helbekkmo via COFF
2023-03-09  1:22   ` [COFF] Re: [TUHS] " John Cowan
2023-03-09 19:55     ` Dan Cross
2023-03-09 20:09       ` Larry McVoy
2023-03-11 20:32         ` Dan Cross
2023-03-11 23:28       ` Bakul Shah
     [not found]   ` <ZA+gxAePDMWK6StD@straylight.ringlet.net>
2023-03-13 22:34     ` Dan Cross
2023-07-05 21:48       ` Dan Cross
2023-07-05 23:58         ` Grant Taylor via COFF [this message]
2023-07-06  1:02           ` Dave Horsfall
2023-07-06 16:47             ` Grant Taylor via COFF
2023-07-06  2:35           ` Dan Cross
2023-07-06  4:18           ` Robert Stanford via COFF
2023-07-06 16:53             ` Grant Taylor via COFF
2023-07-06 17:54               ` Adam Thornton
2023-07-09 14:55           ` Michael Parson
2023-08-01  9:52             ` Michael Cardell Widerkrantz
2023-08-01  9:49         ` Michael Cardell Widerkrantz
2023-08-01 15:55           ` Dan Cross
2023-08-01 16:27             ` Grant Taylor via COFF
2023-08-02 16:07               ` Dan Cross
2023-08-02 20:58                 ` Grant Taylor via COFF
2023-08-02 21:16                   ` Dan Cross

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=08ed6c3a-f2d3-590c-7de4-e01164271da1@tnetconsulting.net \
    --to=coff@tuhs.org \
    --cc=gtaylor@tnetconsulting.net \
    /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).