From: Dave Horsfall <dave@horsfall.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] SCO marketing FreeBSD (was: Micnet, Was: Surprised about Unix System V in the 80's - so sparse!)
Date: Sun, 21 Mar 2021 17:53:12 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2103211744570.73872@aneurin.horsfall.org> (raw)
In-Reply-To: <20210321030425.GD60525@eureka.lemis.com>
On Sun, 21 Mar 2021, Greg 'groggy' Lehey wrote:
>> I'd love to hear more recent news...
>
> So would I. I wonder if they're still basing on FreeBSD 10.
Well, I'm still on 10:
FreeBSD aneurin.horsfall.org 10.4-RELEASE-p13 FreeBSD 10.4-RELEASE-p13 #0: Thu Sep 27 09:21:23 UTC 2018 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386
Just not enough hours in the day when one is retired... I have a spare
(and faster) box waiting for RELEASE once I get a round tuit, based upon
my experiences with partition sizes[*] with the old box (I refuse to sling
everything under "/").
[*]
Dreadful things happen if /tmp is "tmpfs", /tmp fills up with a massive
compilation, and swap was too small...
-- Dave
next prev parent reply other threads:[~2021-03-21 6:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 9:44 [TUHS] Micnet Was: Re: Surprised about Unix System V in the 80's - so sparse! Paul Ruizendaal via TUHS
2021-03-18 11:27 ` Mike Knell via TUHS
2021-03-18 12:04 ` Jim Capp
2021-03-20 11:50 ` Josh Good
2021-03-20 15:16 ` Larry McVoy
2021-03-21 0:08 ` Wesley Parish
2021-03-21 0:18 ` Larry McVoy
2021-03-21 1:12 ` Greg 'groggy' Lehey
2021-03-21 1:31 ` Larry McVoy
2021-03-21 1:42 ` Kevin Bowling
2021-03-21 2:38 ` [TUHS] SCO marketing FreeBSD (was: Micnet, Was: Surprised about Unix System V in the 80's - so sparse!) Greg 'groggy' Lehey
2021-03-21 2:43 ` Kevin Bowling
2021-03-21 3:02 ` Warner Losh
2021-03-21 3:04 ` Greg 'groggy' Lehey
2021-03-21 3:09 ` Warner Losh
2021-03-21 6:53 ` Dave Horsfall [this message]
2021-03-21 11:01 ` Harald Arnesen
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=alpine.BSF.2.21.9999.2103211744570.73872@aneurin.horsfall.org \
--to=dave@horsfall.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).