From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <487A61D1.9020202@proweb.co.uk> Date: Sun, 13 Jul 2008 21:13:05 +0100 From: matt User-Agent: Icedove 1.5.0.14pre (X11/20080304) MIME-Version: 1.0 To: "9fans >> Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Anatomy of a vblade image Topicbox-Message-UUID: e48b9640-ead3-11e9-9d60-3106f5b1d025 > > however you can use the -i switch to initialize a blank > file. (you're free to use a raw disk or partition, too.) > > - erik > > or say "damn, where did my partition table go !" I can't remember if I lost any work :) strings /dev/sdC0/plan9 will let me know eventually ! note to self, be more careful when messing around at storage :> I'm serving drives to WinXP64 via AOE with http://winaoe.org/ I've had a few blue screens but I think they have been caused by the server side serving bad data. If the vblade goes away after being mounted the NT kernel keeps trying to read it which amounts to waiting for network packets to arrive and of course they never do so any NT syscalls take forever (though they run eventually). It does come back to life even if you vblade a different sized disk.