From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ee9e417a0702271524x69e35c16ndfe765323452fad8@mail.gmail.com>
Date: Tue, 27 Feb 2007 18:24:01 -0500
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: booting a terminal in qemu
In-Reply-To: <7d3530220702271440l1315137fm8522ff3a00d2f853@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <7d3530220702271130w3b4dac5fld4a48f8cc5626093@mail.gmail.com>
	<7d3530220702271440l1315137fm8522ff3a00d2f853@mail.gmail.com>
Topicbox-Message-UUID: 164501e6-ead2-11e9-9d60-3106f5b1d025

This should work as far as Plan 9 is concerned.
It's qemu that is troublesome.  One possible approach
to debugging is to boot the live (install) CD and then
run ip/ipconfig -g 10.0.2.2 ether /net/ether0 10.0.2.15 255.255.255.0
and see if that's enough to get a working network (i.e.,
can you ping or telnet to port 567 or 9fs the remote machine).

I have this script as my /etc/qemu-ifup, though I can't
remember exactly why it is needed:

#!/bin/sh
sudo -p "Password for $0:" /sbin/ifconfig $1 172.20.0.1

Russ