9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rsc@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] "Can't read from nvram: /env/nvrof file does not exist"
Date: Fri, 18 Apr 2003 14:37:06 -0400	[thread overview]
Message-ID: <60f350c375d4ee1b27b7a0459fbeb046@plan9.bell-labs.com> (raw)
In-Reply-To: <200304181833.h3IIXK520049@augusta.math.psu.edu>

> I don't think so; why do you say that?  The environment variable you
> could use to force it would be to set nvram.  Eg, nvram=#S/sdD0/9fat
> will force it to look for plan9.nvr on the 9fat partition on sdD0.  If
> you set it to, e.g., #S/sdD0/9fat!foo.nvr, you can use a different
> filename.
>
> My guess is that plan9.nvr doesn't exist on the 9fat partition.  Did
> you `dd -if /dev/zero -of plan9.nvr -count 1'?

You could also set up an nvram partition and use #S/sdD0/nvram,
which I thought was what he did.

In any case, none of this is going to work unless 9load finds the
disk, parses the partition tables, and leaves the info for the kernel.
That's the real problem.



  reply	other threads:[~2003-04-18 18:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 23:18 ron minnich
2003-04-17 23:24 ` Russ Cox
2003-04-18  3:10   ` Dan Cross
2003-04-18  3:13     ` Russ Cox
2003-04-18 14:12     ` ron minnich
2003-04-18 15:22       ` Russ Cox
2003-04-18  3:24   ` Russ Cox
2003-04-18  6:13     ` Dan Cross
2003-04-18 14:17       ` ron minnich
2003-04-18 18:33         ` Dan Cross
2003-04-18 18:37           ` rsc [this message]
2003-04-18 18:38             ` ron minnich
2003-04-18 18:39             ` Dan Cross
2003-04-18 19:30             ` ron minnich
2003-04-18 19:43               ` Russ Cox
2003-04-18 19:51                 ` ron minnich
2003-04-18 19:56                   ` rsc
2003-04-18 14:13     ` ron minnich

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=60f350c375d4ee1b27b7a0459fbeb046@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.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).