9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: matt <mattmobile@proweb.co.uk>
To: "9fans >> Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Anatomy of a vblade image
Date: Sun, 13 Jul 2008 21:13:05 +0100	[thread overview]
Message-ID: <487A61D1.9020202@proweb.co.uk> (raw)
In-Reply-To: <bcf6455ae643bb5cb35cb1b7877e2401@quanstro.net>

>
> 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.




       reply	other threads:[~2008-07-13 20:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bcf6455ae643bb5cb35cb1b7877e2401@quanstro.net>
2008-07-13 20:13 ` matt [this message]
2008-07-13 20:54   ` erik quanstrom
2008-07-13 22:20     ` matt
2008-07-14 14:24       ` [9fans] offtopic: winaoe erik quanstrom
2008-07-15 16:23 [9fans] Anatomy of a vblade image erik quanstrom
     [not found] <b3d39ccfed51c9103afdc527ef7bbf31@quanstro.net>
2008-07-15  9:06 ` matt
2008-07-15 11:49   ` erik quanstrom
2008-07-15 14:18     ` John Waters
  -- strict thread matches above, loose matches on Subject: below --
2008-07-11 12:31 erik quanstrom
2008-07-11 12:23 matt

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=487A61D1.9020202@proweb.co.uk \
    --to=mattmobile@proweb.co.uk \
    --cc=9fans@9fans.net \
    /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).