9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: LiteStar numnums <litestar@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] problems booting a new install
Date: Thu, 25 Aug 2005 10:42:05 -0400	[thread overview]
Message-ID: <283f5df1050825074268e37f05@mail.gmail.com> (raw)
In-Reply-To: <002501c5a980$f90b42e0$e000a8c0@OBLIVIONDT>

Did you try typing glenda?

On 8/25/05, Ezequiel Reyes <ezequiel.reyes@newhotel.co.cu> wrote:
> I just installed a plan 9 system on sdC0, configured the plan9.ini on 9fat
> and the system boots well to the point of showing:
> 
> user[none]:
> 
> I guess there is no user defined after install so I go on with none and this
> is the output:
> 
> kfs ... File system main inconsistent
> Would you like to ream (y/n)? bad nvram key
> bad authentication id
> bad authentication domain
>     tag : Tnone; expected Tdir; addr = 2
> kfs init7 : FID1 attach to root
> kfs 7: suicide: sys: trap: fault read addr=0x0 pc=0x0001cae4
> version ... panic: boot process died: sys: write on closed pipe
> pc=0x00007858
> dumpstack disabled
> cpu: exiting
> 
> these are the main variables in my ini file:
> 
> bootfile=sdC0!9fat!9pcdisk
> bootargs=local!#S/sdC0/fossil
> 
> there was a nobootprompt as well in the .ini file I took has a reference for
> modification with value: local!boot/bzboot
> But I saw no reference to it on the plan9.ini man page. So I tried comenting
> and uncomenting it, no results.
> Is it a problem with my root not defined in the ini? Need I use rootdir or
> something? which would be the path?
> 
> 


-- 
The subject of this essay (the Myth of Sisyphus) is precisely
this relationship between the absurd and suicide, the exact
degree to which suicide is a solution to the absurd. The 
principle can be established that for a man who does not cheat,
what he believes to be true must determine his action.
Belief in the absurdity of existence must then dictate his
conduct. It is legitimate to wonder, clearly and without
false pathos, whether a conclusion of this importance
requires forsaking as rapidly possiblean imcompre-
hensible condition. I am speaking, of course, of men
inclined to be in harmony with themselves.
  << Albert Camus>>


  reply	other threads:[~2005-08-25 14:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f9df42b7c5d3876bb2c68970a2c0425e@plan9.bell-labs.com>
2005-08-25  1:01 ` [9fans] complete control over our own website! Russ Cox
2005-08-25  1:02   ` Devon H. O'Dell
2005-08-25  6:48     ` Joseph Anthony Pasquale Holsten
2005-08-25 11:18   ` Sergey Zhilkin
2005-08-25 12:25     ` Gabriel Diaz
2005-08-25 14:26       ` [9fans] problems booting a new install Ezequiel Reyes
2005-08-25 14:42         ` LiteStar numnums [this message]
2005-08-25 15:20           ` Charles Forsyth
2005-08-25 15:34             ` Ezequiel Reyes
2005-08-25 16:24             ` LiteStar numnums
2005-08-25 15:42         ` Russ Cox
2005-08-25 15:49           ` Ezequiel Reyes
2005-08-25 15:59             ` Gabriel Diaz
2005-08-25 16:38               ` Ezequiel Reyes
2005-08-26  6:23                 ` Gabriel Diaz
2005-08-25 14:17   ` [9fans] complete control over our own website! Jason Gurtz

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=283f5df1050825074268e37f05@mail.gmail.com \
    --to=litestar@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).