From: mathieu.lonjaret@gmail.com (Mathieu Lonjaret)
Subject: [9fans] problem with rminnich's 9vx
Date: Tue, 29 Mar 2011 11:25:00 +0200 [thread overview]
Message-ID: <AANLkTinQkTy0Jm-na7UBy-z06JSB0PuOcgOfzZuHQdKm@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin8AH71r=drki=m+7JYEoYX1w3iJ530G5MRqM92@mail.gmail.com>
Nothing remote or fancy here, just starting 9vx locally (-u glenda -r
plan9vx) after having built it.
However, it is a 64 bits linux and I haven't done anything special or
set any flag when building (cd src; make; make install). Should I?
On Tue, Mar 29, 2011 at 11:18 AM, Noah Evans <noah.evans at gmail.com> wrote:
> I've seen this behavior before, once using 9vx on a remote xsession
> and once when using strace on a (broken) 9vx that was compiled for
> 32bit on a 64bit linux. Are there any mitigating factors that could be
> causing your problem?
>
> Noah
>
>
>
> On Tue, Mar 29, 2011 at 11:00 AM, Mathieu Lonjaret
> <mathieu.lonjaret at gmail.com> wrote:
>> Hi all,
>>
>> this is probably trivial; this is what I get when trying to start 9vx:
>>
>> Warning! factotum can't protect itself from debugging: '#p/5' file does not exist
>> init: warning: can't open #p/2/ctl: '#p/2' file does not exist
>>
>> init: starting /bin/rc
>> FAILED
>> Warning! auth/factotum can't protect itself from debugging: '#p/64' file does not exist
>> rio: can't open display: initdisplay: /dev/draw/new: no frame buffer
>> init: rc exit status: rio 9: display open
>>
>> init: starting /bin/rc
>> #d/0: rc: .: can't open: '#d/0' file does not exist
>> init: rc exit status: rc 67: error
>>
>> init: starting /bin/rc
>> #d/0: rc: .: can't open: '#d/0' file does not exist
>> init: rc exit status: rc 68: error
>>
>> this last error keeps on repeating.
>> as a plan 9 tree I'm using the same old one that I kept using with rsc's
>> 9vx (minimal tree provided by rsc, and later filled with more plan 9
>> stuff), could that be the issue? if yes, what do you guys for a tree
>> with ron's 9vx?
>>
>> uname -a:
>> Linux 2.6.32-30-generic #59-Ubuntu SMP Tue Mar 1 21:30:46 UTC 2011 x86_64 GNU/Linux
>>
>> Cheers,
>> mathieu
>>
>>
>>
>
next prev parent reply other threads:[~2011-03-29 9:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 9:00 Mathieu Lonjaret
2011-03-29 9:18 ` Noah Evans
2011-03-29 9:25 ` Mathieu Lonjaret [this message]
2011-03-29 9:33 ` Noah Evans
2011-03-29 9:47 ` yy
2011-03-29 11:49 ` Mathieu Lonjaret
2011-03-29 15:06 ` Christoph Lohmann
2011-03-29 15:42 ` Mathieu Lonjaret
2011-03-29 16:09 ` ron minnich
2011-03-29 16:20 ` Mathieu Lonjaret
2011-03-29 17:16 ` ron minnich
2011-03-29 20:25 ` Charles Forsyth
2011-03-29 20:16 ` ron minnich
2011-03-29 16:46 ` yy
2011-03-29 15:16 ` ron minnich
2011-03-29 16:44 ` Charles Forsyth
2011-03-29 17:00 ` Charles Forsyth
2011-03-29 19:05 ` erik quanstrom
2011-03-29 19:50 ` ron minnich
2011-03-29 20:20 ` Charles Forsyth
2011-03-29 20:55 ` 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=AANLkTinQkTy0Jm-na7UBy-z06JSB0PuOcgOfzZuHQdKm@mail.gmail.com \
--to=mathieu.lonjaret@gmail.com \
/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).