From: John Weaver <jweaver@ehzed.com>
To: 9front@9front.org
Subject: Re: [9front] UEFI boot on ARM / RPi
Date: Sat, 23 May 2020 12:20:32 -0700 [thread overview]
Message-ID: <20200523192032.GA1189@nitrogen.ehzed.com> (raw)
In-Reply-To: <CAFSF3XNMoifKby0Z+3j5CCD=53VDvg5WDAWWYN-jvvnU3Qsppw@mail.gmail.com>
On Sat, May 23, 2020 at 07:34:15AM +0000, hiro wrote:
> >> /dev/reboot
> >
> > When I last tried that it didn't work. Not sure why.
> > The system is slightly broken right now because all my mice stopped
> > working for some reason (even though the setup is basically the same
> > one i used a few months ago), so I'll try to reproduce it later. But I'm
> > pretty sure that doing what the docs said didn't work, so I just
> > assumed the bcm(64) kernel doesn't support it.
> > I also want to try out some Linux and BSD distros on it, and I'm not
> > sure if I can kexec between them and 9front. My conservative guess was
> > that I cannot, or at the very least there will be limitations.
> >
>
> well, if you fix whatever issues /dev/reboot still have for you it
> will save you time in the long run. maintaining an efi operating
> system alongside the bootloader firmware and all your other bsd, linux
> shit is much more complexity than you will be able to handle.
I think the error is that reboot(8) doesn't recognize the signature of the
kernel for 9pi{,2,3,4}. The 's' kernels so work with reboot(8).
-john
next prev parent reply other threads:[~2020-05-23 19:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 23:51 raingloom
2020-05-22 2:14 ` [9front] " Roman Shaposhnik
2020-05-22 2:29 ` ori
2020-05-22 8:23 ` hiro
2020-05-22 15:16 ` raingloom
2020-05-22 16:58 ` hiro
2020-05-22 22:44 ` raingloom
2020-05-22 22:52 ` Daniel Morandini
2020-05-23 3:34 ` raingloom
2020-05-23 7:34 ` hiro
2020-05-23 19:20 ` John Weaver [this message]
2020-05-22 10:59 ` cinap_lenrek
2020-05-25 3:14 ` Roman Shaposhnik
2020-05-25 6:49 ` cinap_lenrek
2020-05-23 23:13 ` Ethan Gardener
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=20200523192032.GA1189@nitrogen.ehzed.com \
--to=jweaver@ehzed.com \
--cc=9front@9front.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).