9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Sander van Dijk" <a.h.vandijk@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: Duplicate entries in fresh plan9.ini
Date: Tue,  8 Jan 2008 20:25:11 +0100	[thread overview]
Message-ID: <ba0d3bc70801081125i52aa95b6xf6265c3ac607a303@mail.gmail.com> (raw)
In-Reply-To: <eec3ed11c89cbae92a8e2e5555d10638@quanstro.net>

On Jan 7, 2008 11:18 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> 9fans is a fine place for this.  perhaps no one with much experience
> with the install process has had time to take a look.  you might also
> consider submitting a patch.

I'd like to, but I'm not sure yet what the right fix is. The hack I
suggested in my initial mail could be sufficient temporarily, but
definitely not in the long run.
Before the introduction of the third boot menu item, all the things
from the plan9.ini on the cd-rom that needed to go into a freshly
installed plan9.ini would be some of the lines under [common]. That's
what the original grep line accomplished back when the menu items only
indicated what bootfile and bootargs to use.
Now however, the menu items set more things.
So I guess a starting point would be to replace the grep line with
something that takes only the necessary lines from [common], and never
any other lines. This would create a fresh plan9.ini pretty much the
same as it was before the third boot menu item was introduced.
However, I believe the extra settings under the different menu items
aren't there for no reason; not adding them to a fresh plan9.ini could
possible leave a fresh installation unbootable.
In other words, some of the lines from [install] or [cdboot] should
probably go into a fresh plan9.ini as well, but I'm not sure which
ones (or based on what the install script should decide which ones,
and whether to take them from [install] or [cdboot]).
If anyone can answer those questions, or at least provide some
thoughts about it, thanks!

Greetings, Sander.


  parent reply	other threads:[~2008-01-08 19:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-27 20:11 [9fans] " Sander van Dijk
2008-01-07 10:44 ` [9fans] " Sander van Dijk
2008-01-07 22:18   ` erik quanstrom
2008-01-08  2:57     ` Pietro Gagliardi
2008-01-08  3:07       ` erik quanstrom
2008-01-08 19:25     ` Sander van Dijk [this message]
2008-01-09 16:07   ` Russ Cox
2008-01-09 19:50     ` Sander van Dijk
2008-01-15  9:08       ` Patrick Kristiansen

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=ba0d3bc70801081125i52aa95b6xf6265c3ac607a303@mail.gmail.com \
    --to=a.h.vandijk@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).