9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] problem with installing plan9
Date: Tue,  2 Mar 2010 21:48:57 +0100	[thread overview]
Message-ID: <a560a5d01003021248y1452db97q8a0a06cdd5722354@mail.gmail.com> (raw)
In-Reply-To: <856fadf2a2128c808e2deffe7852ddbd@brasstown.quanstro.net>

[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]

On 2 March 2010 21:07, erik quanstrom <quanstro@quanstro.net> wrote:
>> I tried 9atom and got much further, but again hit something...
>> Everything goes well until about 50 % in the 'copydist' installation
>> task. Then I start getting messages caught in the attached pictures...
>> Finally I get the prompt saying 'Task to do [copydist]:'
>> Can anybody tell what's going on now?
>
> this is my fault.  fortuantely these messages should be
> harmless.
>
> the problem is that i put some impossible permissions on the cd.
> and replica is warning that it can't replicate these permissions.
>
> let me know if things really don't work.
>
> - erik
>

Ok.
So those errors are also only warnings? (there were two types of
messages, one starting with 'warning', other with 'error')

Anyway, after running 'copydist' for the first time the installation
program promted, as I said, 'copydist' again. I hit enter, then after
it has finished (it actually as if tries to do the same as it did for
the first time; producing the same or at least very similar messages)
it offers to configure the boot loader, then finish. After reboot I
saw what is attached as a picture. :(
When I rebooted again, it didn't stop, spat a lot other error messages
and now I am getting trillion messages as depicted in the second
picture...
Endless today :)

Any suggestion now?

Thanks for help!
R

[-- Attachment #2: IMG_2266.JPG --]
[-- Type: image/jpeg, Size: 71689 bytes --]

[-- Attachment #3: IMG_2267.JPG --]
[-- Type: image/jpeg, Size: 110351 bytes --]

  reply	other threads:[~2010-03-02 20:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02 12:21 Rudolf Sykora
2010-03-02 13:32 ` Alexander Sychev
2010-03-02 13:39 ` erik quanstrom
2010-03-02 20:02   ` Rudolf Sykora
2010-03-02 20:07     ` erik quanstrom
2010-03-02 20:48       ` Rudolf Sykora [this message]
2010-03-02 21:19         ` erik quanstrom
2010-03-05 16:21           ` Rudolf Sykora
2010-03-07 17:13           ` Rudolf Sykora
2003-03-08 13:23             ` kokamoto
2010-03-08 15:20               ` erik quanstrom
2010-03-08 15:26                 ` Rudolf Sykora
2010-03-08 15:27                 ` kokamoto
2010-03-03  7:27         ` David du Colombier
2010-03-03  9:49           ` Rudolf Sykora
2010-03-02 15:34 ` David Leimbach
     [not found] <mailman.10479.1267532528.1513.9fans@9fans.net>
2010-03-02 16:09 ` Artem Pylypchuk
2010-03-02 17:45   ` Rudolf Sykora
2010-03-03  9:03   ` Alexander Sychev
2010-03-03 13:07     ` erik quanstrom
2010-03-13 12:43       ` Alexander Sychev
2010-03-13 14:49         ` erik quanstrom

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=a560a5d01003021248y1452db97q8a0a06cdd5722354@mail.gmail.com \
    --to=rudolf.sykora@gmail.com \
    --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).