9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cherry <lunaria21@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Loongson port, and 64 bit MIPS
Date: Sun, 17 Aug 2014 14:39:43 -0400	[thread overview]
Message-ID: <CACzOosBHiG+Z7DfMkivVL-etmGhR2HPsZw2Vc+q86s+CrRaVfQ@mail.gmail.com> (raw)
In-Reply-To: <3ccc01397290ed4a848e13f90c878e7e@proxima.alt.za>

On Sun, Aug 17, 2014 at 1:24 AM,  <lucio@proxima.alt.za> wrote:
>> This kernel has an in-kernel bzfs including binaries like sam, acme
>> and the compiler (so it is a little big in size).
>
> This is valiant (not dissimilar in intent from miller's 9pi) and
> useful, but in my opinion you'll get a lot more support from people
> who like me are willing to build the system from scratch.
Of course. Thank you :)

>
> There are three issues that strike me here: 1.  if I understand the
> 9front-loader, you have built something that resembles it;
I am not sure, probably not. Not familiar with 9front's loader. In my
case, the kernel image is ELF which the bootloader recognizes. The
boot process all come from /sys/src/9/boot from the Labs.

> 2.  if you
> did, it would be nice to converge your version and theirs (I remember
> you did a lot of work building the bzroot that 9front (and 9pi) may
> want to adopt
Yes, I did build the bzroot. My intention was to boot the machine even
before the ethernet or disk driver was done. It turned out to be very
helpful for me to write the driver and fix issues at that early stage.
Now it used as a "live" image for people to start with, before
building everything. Maybe turn it into a installation image in the
future.

It basically resembles the Labs' pc live/installation image, 9pcflop.
I just don't need to do the tricks for putting everything into a
floppy.

> 3.  more specifically, your understanding of how a
> boot image is build could benefit the way 9pi is constructed as well.
>
> The above is from discussions we have had and not yet validated by
> careful investigation of the actual release sources.  In any case, I
> believe that all plan 9 distributions have an opportunity with 9pi and
> 9ln to consider a commonly maintained installation process.  Maybe all
> it takes is more documentation, but more likely just a little more
> effort.
Yes, any advice is welcomed.

Thanks,
- cherry



  reply	other threads:[~2014-08-17 18:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15  2:07 cherry
2014-08-15  4:41 ` Skip Tavakkolian
2014-08-15  5:54   ` Fausto Saporito
2014-08-15 14:20     ` cherry
2014-08-15  7:23 ` David du Colombier
2014-08-15 17:34   ` cherry
2014-08-15 18:30     ` David du Colombier
2014-08-16 20:29       ` cherry
2014-08-16  6:54     ` lucio
2014-08-16 10:13       ` Shane Morris
2014-08-16 20:58         ` cherry
2014-08-16 22:34           ` Shane Morris
2014-08-17  5:28           ` lucio
2014-08-17 18:16             ` cherry
2014-08-16 16:03 ` lucio
2014-08-16 20:42   ` cherry
2014-08-17  5:24     ` lucio
2014-08-17 18:39       ` cherry [this message]
2014-08-17 12:37 Richard Miller
2014-08-17 14:17 ` lucio
2014-08-17 15:49 Richard Miller

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=CACzOosBHiG+Z7DfMkivVL-etmGhR2HPsZw2Vc+q86s+CrRaVfQ@mail.gmail.com \
    --to=lunaria21@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).