[9fans] Problem with drawterm.exe: "cpu: failed to chdir"

[9fans] Problem with drawterm.exe: "cpu: failed to chdir"

[Patrick Kristiansen]

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

Hello.
I have just installed plan9 as a cpu/auth/fileserver in vmware. After lots
of work and hours of reinstalling and messing around with networking and
bridging I finally got drawterm to connect to it.
Here's what I get:

user: bootes
bootes@something.net password:
cpu: failed to chdir to "C:\"

When I move drawterm.exe around C:\ changes to whereever it's placed.
I use the version of drawterm.exe from http://swtch.com/drawterm/. I can
both from plan9 to windows and from windows to plan9. I use the "host-only"
network setting in vmware because I couldn't get bridging to work (well, I
could, but then something happened....)
I downloaded the iso yesterday and at the moment I'm not capable of getting
it to pull from sources.

-Patrick Kristiansen

[-- Attachment #2: Type: text/html, Size: 1100 bytes --]

Re: [9fans] Problem with drawterm.exe: "cpu: failed to chdir"

[erik quanstrom]

drawterm, like cpu, trys to put you in the same directory on the remote
machine that you were in on the local machine.

in your case this is not possible -- there's no C:\ on plan 9.
but this should not be a problem.  you will just be plopped in bootes
home directory instead.

- erik

> Hello.
> I have just installed plan9 as a cpu/auth/fileserver in vmware. After lots
> of work and hours of reinstalling and messing around with networking and
> bridging I finally got drawterm to connect to it.
> Here's what I get:
>
> user: bootes
> bootes@something.net password:
> cpu: failed to chdir to "C:\"

Re: [9fans] Problem with drawterm.exe: "cpu: failed to chdir"

[Patrick Kristiansen]

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

That was acutualy what happened. It just took 5 minutes and the first time I
gave it so long was while I was writing to 9fans.
Any idea why it takes 5 minutes for it to work?
-Patrick


On 6/10/07, erik quanstrom <quanstro@coraid.com> wrote:
>
> drawterm, like cpu, trys to put you in the same directory on the remote
> machine that you were in on the local machine.
>
> in your case this is not possible -- there's no C:\ on plan 9.
> but this should not be a problem.  you will just be plopped in bootes
> home directory instead.
>
> - erik
>
> > Hello.
> > I have just installed plan9 as a cpu/auth/fileserver in vmware. After
> lots
> > of work and hours of reinstalling and messing around with networking and
> > bridging I finally got drawterm to connect to it.
> > Here's what I get:
> >
> > user: bootes
> > bootes@something.net password:
> > cpu: failed to chdir to "C:\"
>

[-- Attachment #2: Type: text/html, Size: 1306 bytes --]

Re: [9fans] Problem with drawterm.exe: "cpu: failed to chdir"

[Skip Tavakkolian]

> That was acutualy what happened. It just took 5 minutes and the first time I
> gave it so long was while I was writing to 9fans.
> Any idea why it takes 5 minutes for it to work?

i don't think chdir is causing the delay. do you have anything in
your $home/lib/profile that could take time when you sign in?

Re: [9fans] Problem with drawterm.exe: "cpu: failed to chdir"

[Patrick Kristiansen]

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

Hello again.
I rebooted the plan9 guest os and now it only takes a few seconds from login
to I have rio running.
I don't know what happened, but it's "fixed" now.

-Patrick


On 6/11/07, Skip Tavakkolian <9nut@9netics.com> wrote:
>
> > That was acutualy what happened. It just took 5 minutes and the first
> time I
> > gave it so long was while I was writing to 9fans.
> > Any idea why it takes 5 minutes for it to work?
>
> i don't think chdir is causing the delay. do you have anything in
> your $home/lib/profile that could take time when you sign in?
>
>

[-- Attachment #2: Type: text/html, Size: 929 bytes --]

Re: [9fans] Problem with drawterm.exe: "cpu: failed to chdir"

[erik quanstrom]

running snoopy on the cpu server and vmware's equivalent
(tcpdump?) might reveal who is waiting for what.

i had a similar problem, solved by adding my auth server to
/etc/hosts on a linux box that i sometimes use.

- erik