In the spirit of "thinking outside the box"...*cough*...
You would need to:
1) know what type of file-system your files reside on.
2) Open the device (note: not opening the file!)
3) interpret the file system structure to find the blocks corresponding to your file on disk
4) retrieve the file blocks corresponding to the file and perform your search on the data in memory.
---
Of course you can search multiple files on the same disk, using the same device handle, so of course you save yourself the overhead of multiple "open" calls.
Note: this likely would not work if the file was a remote (networked) file.
Note 2: This would likely be quite painful, but if you're into that sort of thing...:-)
As others have said, within the definition of your problem is an "inherent" open to be able to look into the contents of the file. What are you trying to do that you want to avoid opening the file in perl?
FWIW, I'd change Ted's answer, above, to use "pcregrep" instead of "grep" to maintain use of perl-compatible regular expressions :-).
p.s. -- sometimes you just have to put on your hat of "literalness" :-)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
