From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Latest 9pcf crashes on boot
Date: Mon, 16 May 2016 05:41:27 +0200 [thread overview]
Message-ID: <5ac4132cfd3175bacc58de39589090dc@felloff.net> (raw)
In-Reply-To: <ea2f95c94d10c4c1e8aeb66d57eafa1f@hera.eonet.ne.jp>
the file is corrupted, just as jpg(1) said. i can see the last two rows
containing random garbage with the windows photo viewer as well.
i changed jpg now to output partial data so you can recover some
information.
--
cinap
next prev parent reply other threads:[~2016-05-16 3:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 1:57 sl
2016-05-16 2:03 ` BurnZeZ
2016-05-16 2:10 ` sl
2016-05-16 2:32 ` BurnZeZ
2016-05-16 2:39 ` stanley lieber
2016-05-16 4:49 ` BurnZeZ
2016-05-16 15:03 ` stanley lieber
2016-05-16 3:19 ` kokamoto
2016-05-16 3:41 ` cinap_lenrek [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-15 19:39 stanley lieber
2016-05-16 0:24 ` [9front] " kokamoto
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=5ac4132cfd3175bacc58de39589090dc@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/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).