From: Garth Dahlstrom <ironstorm@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU Windows binaries with PCNet NIC?
Date: Tue, 3 Aug 2004 22:11:07 -0400 [thread overview]
Message-ID: <76bfb9d2040803191176dc4c5b@mail.gmail.com> (raw)
In-Reply-To: <9090625756264628645@unknownmsgid>
Has anyone build Windows QEMU binaries with Anthony Curtis AMD PCNet
nic card added in?
I'm using the expect script below with 'screen', but it's killing
me... (dropped ssh sessions + corrupt downloads = not fun) :)
#!/usr/bin/expect
# Usage: ./rsshtunnel.sh user@host remoteport
if {[llength $argv] != 2} {
puts "Usage: rsshtunnel user@host remoteport"
exit
}
set account [lindex $argv 0]
set remoteport [lindex $argv 1]
puts "Enter password: "
gets stdin password
while 1 {
stty echo
spawn ssh -g -C -N -R $remoteport:localhost:22 $account
stty echo
expect -nocase "password:" {
send "$password\n"
stty echo
}
expect -timeout 3600 eof {
stty echo
}
sleep 2
}
parent reply other threads:[~2004-08-04 2:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <9090625756264628645@unknownmsgid>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76bfb9d2040803191176dc4c5b@mail.gmail.com \
--to=ironstorm@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).