From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Tue, 23 Nov 2004 21:26:57 -0500 From: Russ Cox To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] xen progress ... In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: Topicbox-Message-UUID: 0ab3af5c-eace-11e9-9e20-41e7f4b1d025 > You can see the problem below. Where are the old R messages below? > srvold9p:->Rwrite tag 10 count 29 > srvold9p:<-Twrite tag 10 fid 298 offset 52 count 5 'cpu% ' > srvold9p:=>old Twrite tag 10 fid 298 offset 52 count 5 'cpu% ' > srvold9p:->Rwrite tag 10 count 5 > srvold9p:<-Tread tag 10 fid 296 offset 5 count 512 > srvold9p:=>old Tread tag 10 fid 296 offset 5 count 512 > srvold9p:->Rread tag 10 count 3 'ps > ' > srvold9p:<-Twrite tag 8 fid 298 offset 57 count 3667 'bootes 1 0:01 0:04 88K Await init > bootes' > srvold9p:=>old Twrite tag 8 fid 298 offset 57 count 3667 'bootes 1 0:01 0:04 88K Await init > bootes' > srvold9p: (pid 101, errstr read or write too large) wrote -1 to old system; should be 3683 > > So srvold9p goes to write to the old9p fd and gets an error that makes no > sense on a tcp socket. I'm still trying to find the source of the error in > the kernel (I modified fatal() in srvold9p to use %r, hence the errstr ... > part of that message). I think that what is happening is your old 9P server (drawterm?) is responding with an old Rwrite with a -1 length, but that's not acceptable (it should respond with an Rerror instead), and the srvold9p code treats the number as unsigned and complains that it is too big (as too big as it could possibly be!). This is probably just a drawterm bug. Try using cpu -O instead. Russ