If execution speed is **really** critical then you'll have to go to
C (or something else low-level and
fast) as the mere overhead of running perl will be enough to slow you down from the sounds of it. Also, if you really want to grok the inode table you'll have to rule out perl as it doesn't have the functionality to do *really* low-level file-system stuff (unless you use
XS or
Inline::C).
I'm not a file-system ninja but I'd say the best place to look for inode info without actually reading straight off the 'metal' is to use the stat() function in C which should be in your standard library (and if you don't, you've got quite an unusual C install and a magical version of perl) and subsequently is very portable so worry not (too much ;-) about migrating it to other *nixes.
HTH
_________
broquaint
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.