From: dave at horsfall.org (Dave Horsfall)
Subject: [COFF] [TUHS] The most surprising Unix programs
Date: Wed, 18 Mar 2020 09:48:17 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2003180943250.10777@aneurin.horsfall.org> (raw)
In-Reply-To: <CAC20D2OgYLUjsrTs_fU71Yjw9gmLN15xQYQNeZ4_pnyBWVbmBw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
On Tue, 17 Mar 2020, Clem Cole wrote:
> > Can't say the same for UEFI, I disable that crap.
>
> Well, it beats the crap out of IBM's BIOS, but that bar is very low.
> UEFI was sort of a 'camel' (a horse designed by committee) and too
> many people peed on it. Intel created EFI to try to fix BIOS and then
> people went nuts. Apple's version is the best of them, but as you say,
> they all suck if you have seen anything better. A big problem IMO is
> that EFI tried to be somewhat compatible. In the end, they were not, so
> you got the worst of both (new interfaces and legacy functionality).
The first time I blundered into UEFI was when I tried to boot FreeBSD on a
newish PC, and of course it was not an authorised CD, was it? Or
something like that; anyway, I'm a great believer in allowing idiots to
shoot themselves in the foot if they so desire.
-- Dave
next prev parent reply other threads:[~2020-03-17 22:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202003132331.02DNVaxN061501@tahoe.cs.Dartmouth.EDU>
[not found] ` <7ec47fd97b1a3d383ffed428f21f5287@firemail.cc>
[not found] ` <CALMnNGjuQybT8_g_g498dOuV9OV67JEOn7Mz34vG1TeO9WrkYw@mail.gmail.com>
[not found] ` <cdef128a21d3ed60c79dc5253d761652@firemail.cc>
[not found] ` <20200317145723.GF26660@mcvoy.com>
2020-03-17 15:41 ` clemc
2020-03-17 22:48 ` dave [this message]
[not found] ` <alpine.BSF.2.21.9999.2003180908300.10777@aneurin.horsfall.org>
[not found] ` <c44be69f-846d-55f2-2709-8765f7f5fcc4@gmail.com>
2020-03-19 21:31 ` dave
2020-03-19 21:30 ` cym224
2020-03-19 21:48 ` stewart
2020-03-21 2:49 ` dave
2020-03-21 2:55 ` lm
2020-03-21 4:01 ` [COFF] HP calculator emulators (was: The most surprising Unix programs) grog
2020-03-21 7:21 ` [COFF] The most surprising Unix programs tih
2020-03-21 21:10 ` mparson
[not found] ` <6D9CA6C2-BDF2-4BCA-9503-0F8415C594C9@guertin.net>
2020-03-20 15:40 ` [COFF] [TUHS] " gtaylor
[not found] ` <202003201640.02KGerlG470796@darkstar.fourwinds.com>
[not found] ` <0b0d0ba3-7eae-a844-cc9a-ae542edb302b@tnetconsulting.net>
2020-03-20 19:11 ` clemc
2020-03-20 19:31 ` [COFF] " tih
2020-03-20 19:43 ` gtaylor
2020-03-20 19:47 ` gtaylor
2020-03-20 20:10 ` terry
2020-03-20 20:37 ` clemc
2020-03-20 20:30 ` tih
2020-03-20 20:31 ` clemc
2020-03-20 22:51 ` dave
[not found] <20200320140308.4FBBB18C073@mercury.lcs.mit.edu>
2020-03-20 16:07 ` [COFF] [TUHS] " gtaylor
2020-03-20 20:33 ` mike.ab3ap
2020-03-21 3:53 ` dave
2020-03-21 4:11 ` paul
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.2003180943250.10777@aneurin.horsfall.org \
--to=coff@minnie.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).