9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <john@jfloren.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] GSoC 2012
Date: Wed, 14 Mar 2012 12:38:53 -0700	[thread overview]
Message-ID: <CAL4LZyhGqa84UNTv-s-L_FtAinq6c4ZU9nig+W3tp_FUNP5S5Q@mail.gmail.com> (raw)
In-Reply-To: <20120314190332.GA17909@polynum.com>

On Wed, Mar 14, 2012 at 12:03 PM,  <tlaronde@polynum.com> wrote:
> May I suggest to add an "easy" project to the list: review Plan9
> installation.
>
> The "howto install without" (explaining how to create a Plan9 realm
> from another OS if the CD can not be used) that I posted a while
> ago did not attract a lot of attention. But dealing with the install,
> I saw many details that prevent a more versatile installation.
>
> And fdisk(8) has still to be fixed (on the stack but too many things
> going on with KerGIS or kerTeX for me).
>
> From what I have seen, it is a light project.

I agree that the install situation could use some work--it can be a
little bit odd if you aren't installing from a CD like a good boy, or
if you try to build an ISO from somewhere that *isn't* Bell Labs. It's
actually pretty straightforward to modify, though; it didn't take me
very long to get an iso building and figure out how the installer
works.

I've already done some tweaking with this in Nix, moving the inst/
programs to /rc/bin/inst, which makes it possible to easily start an
installation when booted from the CD with option 2, "boot plan 9 from
this cd", eliminating the need for the 9pcflop kernel and its limited
root environment.

I'd worry that doing an overhaul of the installation process is more
of a 1-2 week project, although it would be useful and a very nice
simple task.

John



  reply	other threads:[~2012-03-14 19:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 16:13 Anthony Sorace
2012-02-24 16:19 ` Calvin Morrison
2012-02-24 16:23   ` Devon H. O'Dell
2012-02-24 16:30     ` Calvin Morrison
2012-02-27  8:40       ` JIghtuse
2012-02-28 17:36         ` Anthony Sorace
2012-03-14 19:03           ` tlaronde
2012-03-14 19:38             ` John Floren [this message]
2012-03-14 22:15               ` Charles Forsyth
2012-03-14 22:57                 ` Anthony Sorace
2012-03-15  0:35                   ` Devon H. O'Dell
2012-03-15 22:01                   ` Jeremy Jackins
     [not found]                   ` <CAOr72mhZkyOd_0BmUMn3dYjF64dtvcO3yL7beAK8n+cwPr2oBg@mail.gmail.c>
2012-03-16  0:38                     ` erik quanstrom
2012-03-16  1:55                       ` Jeremy Jackins
2012-03-16  2:06                         ` andrew zerger
2012-03-16  2:43                           ` Stanley Lieber
     [not found]                   ` <CAEDadry=HSYbzrScF+J7AT2qUxzNr7TNy=tL8fXyt3qdH035cA@mail.gmail.c>
2012-03-16  2:34                     ` erik quanstrom
2012-02-24 16:23   ` Anthony Sorace
2012-03-15 22:27 Paschke Christoph
     [not found] ` <CAB+41mHTO=anpHyxSrPrv-8tGW19_-cA9=21HEjQPcemXdCVOA@mail.gmail.com>
2012-03-16  6:58   ` Paschke Christoph

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=CAL4LZyhGqa84UNTv-s-L_FtAinq6c4ZU9nig+W3tp_FUNP5S5Q@mail.gmail.com \
    --to=john@jfloren.net \
    --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).