• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
So what does VOL_CAP_INT_USERACCESS actually mean?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

So what does VOL_CAP_INT_USERACCESS actually mean?


  • Subject: So what does VOL_CAP_INT_USERACCESS actually mean?
  • From: James Bucanek <email@hidden>
  • Date: Fri, 23 Feb 2018 16:56:14 -0700

Hello,

I have a (low priority) question about the VOL_CAP_INT_USERACCESS volume attribute.

I often get the ATTR_CMN_USERACCESS value for files via getattrlist().

Today, while doing unrelated research, I stumbled across the description for VOL_CAP_INT_USERACCESS which says "If this bit is set the volume format implementation supports the ATTR_CMN_USERACCESS attribute."

This took me quit by surprise, since ATTR_CMN_USERACCESS has never failed me. In testing I've now identified volumes that report VOL_CAP_INT_USERACCESS=0, but when I get the attributes for a file and request ATTR_CMN_USERACCESS it reports completely reasonable values.

So what does it mean, in terms of requesting the ATTR_CMN_USERACCESS attribute, if a volume reports VOL_CAP_INT_USERACCESS=0.

Thanks,

James
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: So what does VOL_CAP_INT_USERACCESS actually mean?
      • From: Vivek Verma <email@hidden>
  • Next by Date: Re: So what does VOL_CAP_INT_USERACCESS actually mean?
  • Next by thread: Re: So what does VOL_CAP_INT_USERACCESS actually mean?
  • Index(es):
    • Date
    • Thread