This is really something that's not easily made platform independent. If you can limit yourself to a single OS you might can find some pattern to the dev_t numbers (negative for NFS apparently doesn't hold on your platform). One way which only depends on a single external command would be:

• parse the output from df to build a list of filesystems and their type
• for each filesystem save off the dev_t value from (stat( "$mountpoint/." ))[0]
• compare (stat( $file_in_question ))[0] to your saved dev_t list

More of a long shot would be to use Inline::C to get a version of the major()/minor() macros (or hand-roll them), and then compare those against disk device files in /dev. If there's one with the same major/minor, it's a local file; if not it's probably remote (but then you probably wouldn't be able to figure out NFS vs SMB vs . . .).

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.