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: [9fans] Re: Duplicate entries in fresh plan9.ini
Date: Mon,  7 Jan 2008 11:44:31 +0100	[thread overview]
Message-ID: <ba0d3bc70801070244q51fbe9fgf0fa40ba4b8d8582@mail.gmail.com> (raw)
In-Reply-To: <ba0d3bc70712271211g12ced417tce242d2b5954f496@mail.gmail.com>

Hi all,

Since no one has replied to this, I'm wondering if this was the right
place to send it to. Is 9trouble more appropriate for this?

Thanks,
Sander.

On Dec 27, 2007 9:11 PM, Sander van Dijk <a.h.vandijk@gmail.com> wrote:
> Hi,
>
> As has been noticed in the thread "Qemu question" (started on Nov 9,
> 2007), installing from recent cd images gives duplicate *nobiosload=1
> and *noahciload=1 entries, causing a rather useless (because the lines
> are identical) menu at boot time.
>
> I've been looking for the cause of these duplicate entries, and they
> appear to have been introduced together with the third boot option on
> the cd, "Boot Plan 9 from this CD and debug 9load".
> I've been able to trace the cause of the duplicate entries back to the
> following line in /sys/lib/dist/pc/inst/bootsetup on the cd:
>
> grep -v '(^\[)|menuitem|adisk|bootfile|bootdisk|bootargs|nobootprompt|mouseport|vgasize|monitor|cdboot'
> /tmp/plan9.orig
>
> This line causes the following to be added to the new plan9.ini:
>
> *nomp=1
> *nodumpstack=1
> partition=new
> dmamode=ask
>
> *nobiosload=1
> *noahciload=1
>
> *nobiosload=1
> *noahciload=1
>
> *debugload=1
>
> The reason for the duplicate entries here are obvious given the
> contents of /tmp/plan9.orig.
>
> Now, there are a couple of things I'm wondering about:
>
> Are the *nobiosload=1 and *noahciload=1 entries still necessary? Is
> the third boot option on the cd still necessary? If not, removing them
> would fix the duplicate entry problem.
>
> If these entries and/or the third boot option are still necessary, I
> guess the mentioned line in /sys/lib/dist/pc/inst/bootsetup should be
> changed so that it doesn't cause duplicate lines anymore?
> If the entries and the third boot option are meant to be temporary, a
> quick and dirty change like the following line (which add everything
> that the current line does, without duplicate entries) might suffice:
>
> grep -v '(^\[)|menuitem|adisk|bootfile|bootdisk|bootargs|nobootprompt|mouseport|vgasize|monitor|cdboot'
> /tmp/plan9.orig | sort | uniq
>
> If the entries and the third boot option are stayers, I guess
> something more sophisticated would be nicer...
>
> Greetings, Sander.
>


  reply	other threads:[~2008-01-07 10:44 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 ` Sander van Dijk [this message]
2008-01-07 22:18   ` [9fans] " erik quanstrom
2008-01-08  2:57     ` Pietro Gagliardi
2008-01-08  3:07       ` erik quanstrom
2008-01-08 19:25     ` Sander van Dijk
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=ba0d3bc70801070244q51fbe9fgf0fa40ba4b8d8582@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).