From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] partial cp
Date: Tue, 26 Jan 2010 19:55:13 +0000 [thread overview]
Message-ID: <df49a7371001261155t155e5dfdx2e1fc493577b8090@mail.gmail.com> (raw)
In-Reply-To: <4B5DD1C5.2080600@maht0x0r.net>
modify the source of fc to specify an offset is
probably your easiest solution if you want to
carry on copying at the same speed.
2010/1/25 maht <maht-9fans@maht0x0r.net>:
> On 25/01/2010 01:45, Akshat Kumar wrote:
>>
>> what are some suggested ways to copy just
>> the rest of the file, without starting all over?
>>
>
> dd
>
>
>
next prev parent reply other threads:[~2010-01-26 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 1:45 Akshat Kumar
2010-01-25 17:15 ` maht
2010-01-26 19:55 ` roger peppe [this message]
2010-01-26 20:03 ` maht
2010-01-27 1:51 ` Federico G. Benavento
2010-01-27 7:27 ` Akshat Kumar
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=df49a7371001261155t155e5dfdx2e1fc493577b8090@mail.gmail.com \
--to=rogpeppe@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).