From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <7d3530220608130723k29e3f708ue283b8315a51109a@mail.gmail.com> Date: Sun, 13 Aug 2006 07:23:27 -0700 From: "John Floren" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] vncs on a cpu/auth machine In-Reply-To: <42346c1b5889a272439cb0ceacd4aaa5@mail.gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7d3530220608121644q48f2298fn57148e1853a087f2@mail.gmail.com> <42346c1b5889a272439cb0ceacd4aaa5@mail.gmx.net> Topicbox-Message-UUID: 9e8d39b6-ead1-11e9-9d60-3106f5b1d025 On 8/13/06, Sascha Retzki wrote: > > Hi all > > I've got my little old auth/cpu machine sitting here, and I'd like to > > run vncs (for a persistent desktop, and to show that I can), but when > > I run "vncs", it starts a desktop, but when I try to connect from my > > Linux box, I get this message: > > > > You know cpu(1), right? What does that have to do with it? > > vncs: vncchal: needkey dom? proto=p9sk1 user? > > your vnc-client does not supply a username, imho. > So... what do I do? I have connected to both 9grid.de and tip9ug.jp using vnc clients that do not supply usernames. John -- "The first thing we do, let's kill all the lawyers" -- Shakespeare, Henry VI