From: Conor Williams <conor.williams@gmail.com>
To: erik quanstrom <quanstro@labs.coraid.com>
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Ideas from Plan-9
Date: Thu, 19 Dec 2013 22:36:28 +0000 [thread overview]
Message-ID: <CAL6pNZ_n1=5_J-_Tx9MN_K_8Cvn-QDrZUMNa6aTJgN_rMHgTgg@mail.gmail.com> (raw)
In-Reply-To: <573dcee27e153a7e9ad877e22ef5e904@coraid.com>
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
cool man, nice follow up... it's the bell-labs one is code 87... your one
was fine but it crashed... and that was the pic I sent...
don't worry too much about it... gonna get some of my old hardware after
christmas, that I know is supported... I will let you know what happens
then my friend...
On Wed, Dec 18, 2013 at 8:51 PM, erik quanstrom <quanstro@labs.coraid.com>wrote:
> On Wed Dec 18 04:48:29 EST 2013, conor.williams@gmail.com wrote:
>
>
> > i'm getting an error code 87 writing usbdisk to my key:
> >
> > according to the web: The second fix prevents USB Image Tool from
> > restoring invalid images in device mode. A valid device mode image
> > has to be multiple of 512. If that’s not the case, the write
> > operation will fail with error code 87 close to the end of the
> > process. To prevent this, USB Image Tool now checks, if the image
> > file size is a multiple of 512.
> > http://www.alexpage.de/tag/usb-image-tool/
>
> i'm not sure what tool you're using, but the image is a multiple of
> 512 bytes long.
>
> ; </n/atom/ftp/usbinstamd64.bz2 >/tmp/usbinstamd64 bunzip2
> ; ls -ltr /tmp
> --rw-rw-r-- M 788 quanstro quanstro 524288000 Dec 18 15:48
> /tmp/usbinstamd64
> ; echo 524288000 % 512 | hoc
> 0
>
> perhaps something got corrupted.
>
> the crash dump is good information but in this case the pc does not appear
> to be valid, so i don't see what's wrong yet.
>
> - erik
>
[-- Attachment #2: Type: text/html, Size: 2127 bytes --]
next prev parent reply other threads:[~2013-12-19 22:36 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 17:05 Blake McBride
2013-12-15 17:18 ` Bence Fábián
2013-12-15 17:51 ` Blake McBride
2013-12-15 18:00 ` Bence Fábián
2013-12-15 18:43 ` Blake McBride
2013-12-15 20:30 ` erik quanstrom
2013-12-15 19:18 ` Steve Simon
2013-12-15 19:28 ` Blake McBride
2013-12-15 19:31 ` Steve Simon
2013-12-15 20:03 ` Blake McBride
2013-12-15 20:17 ` erik quanstrom
2013-12-15 21:17 ` Blake McBride
2013-12-15 21:23 ` Bence Fábián
2013-12-16 0:30 ` Blake McBride
2013-12-15 21:25 ` Lee Fallat
2013-12-15 22:17 ` Blake McBride
2013-12-15 22:06 ` Kurt H Maier
2013-12-15 22:30 ` Matthew Veety
2013-12-15 22:48 ` Tristan
2013-12-15 23:28 ` erik quanstrom
2013-12-17 0:29 ` Jeff Sickel
2013-12-17 4:09 ` Bruce Ellis
2013-12-18 9:47 ` Conor Williams
2013-12-18 20:51 ` erik quanstrom
2013-12-19 22:36 ` Conor Williams [this message]
2013-12-19 22:53 ` erik quanstrom
2013-12-19 23:15 ` Conor Williams
2013-12-20 0:29 ` Conor Williams
2013-12-20 0:37 ` Conor Williams
2013-12-20 0:56 ` Conor Williams
2013-12-20 1:44 ` erik quanstrom
2013-12-20 1:53 ` Conor Williams
2013-12-23 23:11 ` erik quanstrom
2013-12-23 23:44 ` Blake McBride
2013-12-24 0:29 ` David Arnold
2013-12-24 1:03 ` erik quanstrom
2013-12-24 3:13 ` Blake McBride
2013-12-24 3:30 ` erik quanstrom
2013-12-24 3:36 ` Blake McBride
2013-12-24 3:45 ` erik quanstrom
2013-12-15 18:59 ` Oleg
2013-12-15 19:13 ` Blake McBride
2013-12-15 20:19 ` Oleg
2013-12-15 20:43 ` Bence Fábián
2013-12-15 20:55 ` Oleg
2013-12-15 20:59 ` Bence Fábián
2013-12-15 20:47 ` Kurt H Maier
2013-12-16 21:26 ` Oleksandr Iakovliev
2013-12-16 21:47 ` Blake McBride
2013-12-16 21:55 ` Anthony Sorace
2013-12-16 22:08 ` Kurt H Maier
-- strict thread matches above, loose matches on Subject: below --
2013-10-24 7:57 Keith
2013-12-15 18:43 ` Blake McBride
2013-12-16 4:54 ` David Arnold
2013-12-16 19:51 ` tyrrell t
2013-12-16 20:59 ` Charles Forsyth
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='CAL6pNZ_n1=5_J-_Tx9MN_K_8Cvn-QDrZUMNa6aTJgN_rMHgTgg@mail.gmail.com' \
--to=conor.williams@gmail.com \
--cc=9fans@9fans.net \
--cc=quanstro@labs.coraid.com \
/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).