From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] manumatic picture copy
Date: Thu, 9 Sep 2010 13:27:28 -0400 [thread overview]
Message-ID: <f21d01f62a06d6523b0c704bb5a3c1bc@brasstown.quanstro.net> (raw)
i put a couple of scripts on sources that you may
be able to bend to your own will
/n/sources/contrib/quanstro/^(camera: cameracp mkthumb)
these scripts automate three things, and facilliate
a manumatic process for resetting cranky usb devices.
0. camera: starts a fat fs on the camera's storage. it's assumed to
be a cannon.
1. unique new pictures are copied to /n/other/pictures/yyyymmdd
2. if a usb error occurs that needs the device replugged,
cameracp waits for the user to do that
3. mkthumb makes reasonable-sized plan 9 image thumbnails
(15%) from the images. full size images tend to crash plan 9
terminals. i should probablly use richard's resize, but since i keep
these things around, i might as well burn cpu. my i7 does about
200 thumbs/minute and appears to be slightly limited by the fs,
peaking out at ~30000 packets/sec.
absolutely positively no man page. sorry.
- erik
reply other threads:[~2010-09-09 17:27 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=f21d01f62a06d6523b0c704bb5a3c1bc@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).