From: John Soros <sorosj@gmail.com>
To: 9front@googlegroups.com
Subject: Re: /sys/lib/dist changes
Date: Wed, 13 Apr 2011 04:44:10 +0200 [thread overview]
Message-ID: <20110413044410.3aa977c1@martian.nonpub> (raw)
In-Reply-To: <BANLkTi=YzHg8j9v841J8m_1Vf0qupvgbFA@mail.gmail.com>
Hello,
my 2¢
On Tue, 12 Apr 2011 19:32:09 -0300
Iruatã Souza <iru.muzgo@gmail.com> wrote:
> Hello,
>
> It seems /sys/lib/dist needs some work here and there. Cinap started
> the process by minimizing the mkfile, and more should be done.
> Some goals I think we can accomplish without sacrificing the unholy
> principles are:
>
> 1. Promote the tools used by the installer (/sys/lib/dist/cmd) to
> common tools or get rid of them. This includes writing the relevant
> man pages.
> 2. A 9front cd should be easy to build. This is more or less done.
maybe at the same time building a rootfs should be easy as well
> 3. Make the installer as platform-independent as we can. Installing on
> the little ARMs shouldn't be difficult.
Isn't that usually done via flashing? That would mean one should be
able to build a working rootfs directly and make an image of it?
> 4. If you can boot the live cd, you can boot the installer, and you
> can run the installed system. The new boot code is a big step towards
> that, minor improvements may still be needed, though.
it would be nice if once could install directly from the live
environment.
>
> I mention this more as a rfc, since I am myself willing to devote some
> time to it.
>
> regards,
> iru
installing plan9 with the needed tools and cloning the repo as we
speak..so i'm hopefully not talking out my ass and will be able
to chip in
--
I'm cereal
-- Al Gore in South Park
next prev parent reply other threads:[~2011-04-13 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 22:32 Iruatã Souza
2011-04-13 2:44 ` John Soros [this message]
2011-04-13 16:47 ` cinap_lenrek
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=20110413044410.3aa977c1@martian.nonpub \
--to=sorosj@gmail.com \
--cc=9front@googlegroups.com \
/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).