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 <[email protected]> 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 > <[email protected]> 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 >> >> >> >
