From: Charles Forsyth <charles.forsyth@gmail.com>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] problem with installing plan9 from USB disk image
Date: Fri, 26 Mar 2021 15:21:14 +0000 [thread overview]
Message-ID: <CAOw7k5gtjnjqmbFxwPhqDM0W315YFgzQ6BGYzq1ni4-YSYnRdg@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5ju-i6ZuB29qivsTiVD3_kReNrW08y0NuG46hkNFgWh3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
That reminds me that this
https://retrage.github.io/2020/08/01/9pfspkg-en.html looked quite
interesting but I haven't had a chance to try it yet.
On Fri, Mar 26, 2021 at 3:20 PM Charles Forsyth <charles.forsyth@gmail.com>
wrote:
> I see that 9front has had some UEFI boot support for 6 years.
> I use an earlier version of their iplpxe on my 64-bit cpu servers (not
> booting 9front).
> I did use the iplfat and ipliso as well to boot other kernels.
> When I've got a moment I might diff to see what changes I made.
>
> On Fri, Mar 26, 2021 at 3:08 PM Richard Miller <9fans@hamnavoe.com> wrote:
>
>> > 1. Dual booting is not possible
>> > 2. UEFI introduced vulnerabilities ...
>>
>> Don't these two things cancel each other out? Can we not use
>> the same vulnerabilities to induce the firmware to boot our
>> own choice of operating system? It wouldn't be the first time
>> Plan 9 was installed using ... shall we say unofficial methods?
>>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T4a54d17e4c0f6c20-M4773c5f1d46810c88aa46837
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
[-- Attachment #2: Type: text/html, Size: 2833 bytes --]
next prev parent reply other threads:[~2021-03-26 15:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 9:53 saif.resun
2021-03-25 20:14 ` Richard Miller
2021-03-25 20:30 ` saif.resun
2021-03-25 20:40 ` Richard Miller
2021-03-25 20:51 ` saif.resun
2021-03-25 20:56 ` Richard Miller
2021-03-26 5:46 ` saif.resun
2021-03-26 6:53 ` Alexander Kapshuk
2021-03-26 7:35 ` Lucio De Re
2021-03-26 7:53 ` saif.resun
2021-03-26 8:34 ` Skip Tavakkolian
2021-03-26 8:36 ` saif.resun
2021-03-26 9:39 ` saif.resun
2021-03-26 10:03 ` Richard Miller
2021-03-26 13:20 ` Wes Kussmaul
2021-03-26 13:27 ` hiro
2021-03-26 16:06 ` Wes Kussmaul
2021-03-26 16:12 ` hiro
2021-03-26 17:26 ` Wes Kussmaul
2021-03-26 18:20 ` hiro
2021-03-26 19:51 ` Wes Kussmaul
2021-03-26 15:07 ` Richard Miller
2021-03-26 15:20 ` Charles Forsyth
2021-03-26 15:21 ` Charles Forsyth [this message]
2021-03-28 11:32 ` Lucio De Re
2021-03-26 16:18 ` Kurt H Maier
2021-03-26 16:27 ` Wes Kussmaul
2021-03-27 23:14 ` Ethan Gardener
2021-03-28 7:28 ` sirjofri
2021-03-26 10:03 ` Ethan Gardener
2021-03-26 11:01 ` Lucio De Re
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=CAOw7k5gtjnjqmbFxwPhqDM0W315YFgzQ6BGYzq1ni4-YSYnRdg@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.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).