Re: [OpenAFS] Version of du that doesn't traverse AFS mount points?
just to get out of a pinch, you could start with fsr since that has the logic to not traverse mount points. Then add du functionality to it. Although that might be more of a PITA then just writing a recursive call that does it the right way. *shrugs* On Wed, 27 Aug 2008, Chas Williams (CONTRACTOR) wrote: > In message <[EMAIL PROTECTED]>,"Derric > k Brashear" writes: > >>> i have an interesting idea. on linux this would be pretty easy. > >>> after generic_fill_attr() we could encode the volumeid in the i_dev > >>> field instead of the s_dev field from the superblock. this should make > >>> this work. i cant think of anything it would break. > >> > >> Unless I'm missing something, this breaks anything that relies on stat's > >> st_dev field to determine whether a file is in AFS or not. Filedrawers is > >> one example, and I'm sure there are others. > > > >I wanted to do something like this to make Finder happy on MacOS; The > >side effects get exciting. I might have notes somewhere. I recommend > >against it. > > ok. however, suppose you wanted to add a flag to du that says means > don't traverse mount points however, you arent interested in the pile > of afs libraries you would need to do this 'correctly'. how about > we sneak the volume id in the st_rdev field? this would make it > easier for someone to write the utility since they would only need > the existing to use the stat() syscall. > > i dont think st_rdev has a posix defined meaning. > ___ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info > -- Sean O'Malley, Information Technologist Michigan State University - ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Version of du that doesn't traverse AFS mount points?
In message <[EMAIL PROTECTED]>,"Derric k Brashear" writes: >>> i have an interesting idea. on linux this would be pretty easy. >>> after generic_fill_attr() we could encode the volumeid in the i_dev >>> field instead of the s_dev field from the superblock. this should make >>> this work. i cant think of anything it would break. >> >> Unless I'm missing something, this breaks anything that relies on stat's >> st_dev field to determine whether a file is in AFS or not. Filedrawers is >> one example, and I'm sure there are others. > >I wanted to do something like this to make Finder happy on MacOS; The >side effects get exciting. I might have notes somewhere. I recommend >against it. ok. however, suppose you wanted to add a flag to du that says means don't traverse mount points however, you arent interested in the pile of afs libraries you would need to do this 'correctly'. how about we sneak the volume id in the st_rdev field? this would make it easier for someone to write the utility since they would only need the existing to use the stat() syscall. i dont think st_rdev has a posix defined meaning. ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Version of du that doesn't traverse AFS mount points?
On Wed, Aug 27, 2008 at 2:57 AM, Simon Wilkinson <[EMAIL PROTECTED]> wrote: > > On 27 Aug 2008, at 02:18, Chas Williams (CONTRACTOR) wrote: > >> In message >> <[EMAIL PROTECTED]>,Mike Shaddock >> writes: >>> >>> I'm looking for a version of du where the -x option (skip directories on >>> different file systems) doesn't traverse an AFS mount poi >>> nt. Haven't been able to find anything via searching, so I thought I'd >>> ask here. >> >> i have an interesting idea. on linux this would be pretty easy. >> after generic_fill_attr() we could encode the volumeid in the i_dev >> field instead of the s_dev field from the superblock. this should make >> this work. i cant think of anything it would break. > > Unless I'm missing something, this breaks anything that relies on stat's > st_dev field to determine whether a file is in AFS or not. Filedrawers is > one example, and I'm sure there are others. I wanted to do something like this to make Finder happy on MacOS; The side effects get exciting. I might have notes somewhere. I recommend against it. ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Version of du that doesn't traverse AFS mount points?
Simon Wilkinson wrote: On 27 Aug 2008, at 02:18, Chas Williams (CONTRACTOR) wrote: In message <[EMAIL PROTECTED]>,Mike Shaddock writes: I'm looking for a version of du where the -x option (skip directories on different file systems) doesn't traverse an AFS mount poi nt. Haven't been able to find anything via searching, so I thought I'd ask here. i have an interesting idea. on linux this would be pretty easy. after generic_fill_attr() we could encode the volumeid in the i_dev field instead of the s_dev field from the superblock. this should make this work. i cant think of anything it would break. Unless I'm missing something, this breaks anything that relies on stat's st_dev field to determine whether a file is in AFS or not. Filedrawers is one example, and I'm sure there are others. It also breaks anybody who expects -x to traverse the whole filesystem. mountpoint != filesystem The OpenAFS "up" utility has an explicit flag for stopping its traversal at mountpoints. I don't see a cheap way to conflate the two meanings with one flag and not break somebody. ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Version of du that doesn't traverse AFS mount points?
In message <[EMAIL PROTECTED]>,Simon Wilkinson writes: >Unless I'm missing something, this breaks anything that relies on >stat's st_dev field to determine whether a file is in AFS or not. >Filedrawers is one example, and I'm sure there are others. too bad. it would be pretty elegant. although afs volume id's are fairly consistent. if the 2^29 bit is set are almost assured that is a file on an afs volume. ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Version of du that doesn't traverse AFS mount points?
On 27 Aug 2008, at 02:18, Chas Williams (CONTRACTOR) wrote: In message <[EMAIL PROTECTED]>,Mike Shaddock writes: I'm looking for a version of du where the -x option (skip directories on different file systems) doesn't traverse an AFS mount poi nt. Haven't been able to find anything via searching, so I thought I'd ask here. i have an interesting idea. on linux this would be pretty easy. after generic_fill_attr() we could encode the volumeid in the i_dev field instead of the s_dev field from the superblock. this should make this work. i cant think of anything it would break. Unless I'm missing something, this breaks anything that relies on stat's st_dev field to determine whether a file is in AFS or not. Filedrawers is one example, and I'm sure there are others. S. ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
Re: [OpenAFS] Version of du that doesn't traverse AFS mount points?
In message <[EMAIL PROTECTED]>,Mike Shaddock writes: >I'm looking for a version of du where the -x option (skip directories on >different file systems) doesn't traverse an AFS mount poi >nt. Haven't been able to find anything via searching, so I thought I'd ask >here. i have an interesting idea. on linux this would be pretty easy. after generic_fill_attr() we could encode the volumeid in the i_dev field instead of the s_dev field from the superblock. this should make this work. i cant think of anything it would break. ___ OpenAFS-info mailing list OpenAFS-info@openafs.org https://lists.openafs.org/mailman/listinfo/openafs-info
