From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20130312161528.GA72387@intma.in> References: <6CA24CFD-122D-41E3-9323-8E1BBD519A8D@mostlymaths.net> <20130312161528.GA72387@intma.in> From: =?ISO-8859-1?Q?Rub=E9n_Berenguel?= Date: Tue, 12 Mar 2013 18:52:33 +0100 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=20cf3074b3b46fea0b04d7bdf57d Subject: Re: [9fans] Some benevolent user... Topicbox-Message-UUID: 27f4153e-ead8-11e9-9d60-3106f5b1d025 --20cf3074b3b46fea0b04d7bdf57d Content-Type: text/plain; charset=ISO-8859-1 Ben: Yup, I can write perfectly on your generated images, so it's not a problem with qemu. I thought the correct boot option would be 5, but then I'll use 9queen and then sooner or later I'll see if I can understand everything else is there, Plan9 is relatively complex in its namespace stuff (coming from a mostly Linux/Mac OS background) and ANTS is... complex, although your use cases look very interesting & appealing :). And also, if it works, why break it :)? I have a working image! Kurt: My system is an old Macbook (Early 2008 IIRC, underpowered by today's standards but it's relatively okay) but qemu in general works relatively well, and once an image works and is booted works perfectly. So I'm guessing it's some problem with my qemu build (1.4.0) tied with some way Plan9 tries to write to disk. Or not, it's quite puzzling. Thanks! Ruben On Tue, Mar 12, 2013 at 5:15 PM, Kurt H Maier wrote: > On Tue, Mar 12, 2013 at 01:53:26PM +0100, Ruben Berenguel wrote: > > > > Hangs on copydist (waited ~20 minutes.) > > I've seen copydist take longer than this on underpowered or incorrectly > configured systems. The way it performs the copy is an unmitigated seek > festival. On one of my machines it took a little over an hour; this is > why I'm grateful for cinap's virtio driver, which cut that time in half. > > khm > > --20cf3074b3b46fea0b04d7bdf57d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Ben: Yup, I can write perfectly on your generated images, so it's not a= problem with qemu. I thought the correct boot option would be 5, but then = I'll use 9queen and then sooner or later I'll see if I can understa= nd everything else is there, Plan9 is relatively complex in its namespace s= tuff (coming from a mostly Linux/Mac OS background) and ANTS is... complex,= although your use cases look very interesting & appealing :). And also= , if it works, why break it :)? I have a working image!

Kurt: My system is an old Macbook (Early 2008 IIRC, underpow= ered by today's standards but it's relatively okay) but qemu in gen= eral works relatively well, and once an image works and is booted works per= fectly. So I'm guessing it's some problem with my qemu build (1.4.0= ) tied with some way Plan9 tries to write to disk. Or not, it's quite p= uzzling.

Thanks!

Ruben

On Tue, Mar 12, 2013 at 5:15 PM, Kurt H Maier <khm-9@intm= a.in> wrote:
On Tue, Mar 12, 2013 at 01= :53:26PM +0100, Ruben Berenguel wrote:
>
> Hangs on copydist (waited ~20 minutes.)

I've seen copydist take longer than this on underpowered or incor= rectly
configured systems. =A0The way it performs the copy is an unmitigated seek<= br> festival. =A0On one of my machines it took a little over an hour; this is why I'm grateful for cinap's virtio driver, which cut that time in = half.

khm


--20cf3074b3b46fea0b04d7bdf57d--