From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: I/O edirection and dd
Date: Sun, 24 Apr 2016 10:10:52 -0700 [thread overview]
Message-ID: <160424101052.ZM3380@torch.brasslantern.com> (raw)
In-Reply-To: <20160424112209.GA20670@lilyforest.localdomain>
On Apr 24, 7:22pm, lilydjwg wrote:
} Subject: Re: I/O edirection and dd
}
} On Sun, Apr 24, 2016 at 11:53:42AM +0200, Meino.Cramer@gmx.de wrote:
} >
} > cat verylongfile | dd count=512 | file -
}
} Why don't you let file read the file itself? file won't read the entire
} file.
Indeed, if you check /etc/magic or /usr/share/file/magic (location should
be explained in "man file") you'll find that the number of bytes needed
is listed for most file types. (Encrypted ZIPs may need to read 75kb,
for one example from my system.)
--
Barton E. Schaefer
prev parent reply other threads:[~2016-04-24 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 9:53 Meino.Cramer
2016-04-24 11:22 ` guyzmo
2016-04-24 11:22 ` lilydjwg
2016-04-24 17:10 ` Bart Schaefer [this message]
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=160424101052.ZM3380@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).