9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] notes on fossil, ANTS, and 9front/Bell labs controversies
Date: Mon, 13 Jan 2020 09:33:59 +0000	[thread overview]
Message-ID: <15eec2039882779ed0ee76b991ee8678@hamnavoe.com> (raw)
In-Reply-To: <CA+cCjXpnjuyOb5e59iaiiHAE9-=yV+qvT7rB8bRfAvrRm3hJzA@mail.gmail.com>

steve@quintile.net:
> the issue is 9boot would need tls to be able download the kernel from a
> file server and it doesn’t have it. this is the labs boot procedure of
> course.
>
> 9front booting uses a full kernel to bootstrap (correct me if i am wrong)
> so tls is not a problem there.

There isn't a single "labs boot procedure".  Any 4th edition Plan 9 system
can use the kernel to load another kernel, with whatever embellishments you
care to dream up.  That's what /dev/reboot is for.

If you want to boot over the network mediated by tls, you need a bit of
local storage to hold a (stripped down if you like) first-stage kernel
and a few commands (which may be embedded in the in-kernel /boot filesystem).
That kernel can run a small rc script to do this:
  srv -e 'tlsclient tcp!$fs!777' reboot /n/reboot
  reboot /n/reboot/path/to/next/kernel
On the server you need a corresponding /bin/service/tcp777 with
  #!/bin/rc
  /bin/tlssrv -c /path/to/cert.pem -l listen /bin/aux/trampoline -9 tcp!127.1!564

No exotic extra facilities needed: tlssrv and tlsclient were introduced
with 4th edition Plan 9 in 2002.


  reply	other threads:[~2020-01-13  9:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-10 18:29 mycroftiv
2020-01-10 21:36 ` [9fans] " hiro
2020-01-11 10:31   ` Steve Simon
2020-01-11 10:41     ` Rodrigo G. López
2020-01-11 15:56       ` Steve Simon
2020-01-11 19:32         ` Rodrigo G. López
2020-01-13  9:33           ` Richard Miller [this message]
2020-01-11  4:36 ` 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=15eec2039882779ed0ee76b991ee8678@hamnavoe.com \
    --to=9fans@hamnavoe.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).