From: Conor Williams <conor.williams@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] 9front kernel and error 87 and 9atom change?
Date: Wed, 18 Dec 2013 09:48:47 +0000 [thread overview]
Message-ID: <CAL6pNZ9LqQGe7ARNZ6_DAEEGPkioK893WV=LYF3OZRv-nQ3NsQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1317 bytes --]
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/
9atom doesn't support my hard drive un-fortunately... (see attached
photo...)
going to try 9front now but i don't have a kernel... can i request one that
supports my AMD 2 core 1.8GHZ "Altec Lansing" HP Laptop?
On Tue, Dec 17, 2013 at 4:09 AM, Bruce Ellis <bruce.ellis@gmail.com> wrote:
> GreenArrays rocks. I still have no idea what to with all the cores. I've
> found that writing a go package that generates fun forth is fun.
>
> brucee
> On 17/12/2013 11:32 AM, "Jeff Sickel" <jas@corpus-callosum.com> wrote:
>
>>
>> On Dec 15, 2013, at 4:48 PM, Tristan <9p-st@imu.li> wrote:
>>
>> > and then there's chuck moore.
>>
>> I’m still rooting for GreenArrays as there are a few projects
>> where they chips would actually do well. But now that they’re
>> accepting bitcoin, who knows, who knows.
>>
>> -jas
>>
>>
>>
[-- Attachment #1.2: Type: text/html, Size: 3247 bytes --]
[-- Attachment #2: DSC00499.JPG --]
[-- Type: image/jpeg, Size: 711838 bytes --]
reply other threads:[~2013-12-18 9:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAL6pNZ9LqQGe7ARNZ6_DAEEGPkioK893WV=LYF3OZRv-nQ3NsQ@mail.gmail.com' \
--to=conor.williams@gmail.com \
--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).