Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!ut-sally!std-unix
From: daveb@rtech.uucp (Dave Brower)
Newsgroups: comp.std.unix
Subject: Re: tar stop at mount points
Message-ID: <8046@ut-sally.UUCP>
Date: Wed, 13-May-87 21:01:14 EDT
Article-I.D.: ut-sally.8046
Posted: Wed May 13 21:01:14 1987
Date-Received: Sat, 16-May-87 12:14:21 EDT
References: <8018@ut-sally.UUCP> <8024@ut-sally.UUCP>
Sender: std-unix@ut-sally.UUCP
Reply-To: daveb@rtech.uucp (Dave Brower)
Organization: Relational Technology Inc, Alameda CA
Lines: 25
Approved: jsq@sally.utexas.edu (Moderator, John Quarterman)

From: daveb@rtech.uucp (Dave Brower)

In article <8024@ut-sally.UUCP> jsdy@hadron.uucp (Joseph S. D. Yao) writes:
>In article <8018@ut-sally.UUCP> rbj@icst-cmr.arpa writes:
>>I would also like to see an option not to cross mount points, that is
>>stay on the same partition. This should be added to several major utilities.
>Other than that, this is awfully hard to do unless you are willing
>to break modularity by sticking info about the FS into programs
>which have no need to know about it whatsoever.

Hmmm.  Since stat(2) returns

          struct stat {
               dev_t  st_dev; /* device inode resides on */
               ino_t  st_ino; /* this inode's number */
		.
         };

it should be easy enough to see when you've crossed a device boundary,
and this seems portable under POSIX.  Why do you need additional info
about the FS?

-dB

Volume-Number: Volume emor menu2 men