On 07/07/12 10:22 AM, Michael Tokarev wrote:
On 07.07.2012 17:53, Gary Dale wrote:
On 07/07/12 09:04 AM, Michael Tokarev wrote:
On 07.07.2012 16:25, Gary Dale wrote:
[]
I copied you in on it because this seems to a new behaviour in the krfb and/or
kvm software.
It is not. For qemu/kvm case,
On 07.07.2012 17:53, Gary Dale wrote:
> On 07/07/12 09:04 AM, Michael Tokarev wrote:
>> On 07.07.2012 16:25, Gary Dale wrote:
>> []
>>> I copied you in on it because this seems to a new behaviour in the krfb
>>> and/or kvm software.
>> It is not. For qemu/kvm case, you have to tell it explicitly
On 07/07/12 09:04 AM, Michael Tokarev wrote:
On 07.07.2012 16:25, Gary Dale wrote:
[]
I copied you in on it because this seems to a new behaviour in the krfb and/or
kvm software.
It is not. For qemu/kvm case, you have to tell it explicitly where
(on which port) to listen. This has always bee
On 07.07.2012 16:25, Gary Dale wrote:
[]
> I copied you in on it because this seems to a new behaviour in the krfb
> and/or kvm software.
It is not. For qemu/kvm case, you have to tell it explicitly where
(on which port) to listen. This has always been the case. So you
either told qemu-kvm dir
Package: openssh-client
Version: 1:6.0p1-2
Severity: important
Dear Maintainer,
* What led up to the situation?
example: ssh -L 5900:192.168.1.14:5900 dentaloffice -- will get the
bind: address error
* What exactly did you do (or not do) that was effective (or
ineffective)?
Tried this
5 matches
Mail list logo
