Re: FreeBSD NFSv4.1 nfsd, named attribute support (OPENATTR)?
- Reply: Rick Macklem : "Re: FreeBSD NFSv4.1 nfsd, named attribute support (OPENATTR)?"
- Reply: Rick Macklem : "Re: FreeBSD NFSv4.1 nfsd, named attribute support (OPENATTR)?"
- In reply to: Lionel Cons : "Re: FreeBSD NFSv4.1 nfsd, named attribute support (OPENATTR)?"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 19 Feb 2025 00:13:27 UTC
On Mon, 20 Jan 2025 at 13:15, Lionel Cons <lionelcons1972@gmail.com> wrote: > > On Sun, 12 Jan 2025 at 16:50, Rick Macklem <rick.macklem@gmail.com> wrote: > > > > On Sun, Jan 12, 2025 at 2:09 AM Cedric Blancher > > <cedric.blancher@gmail.com> wrote: > > > > > > Good morning! > > > > > > Does FreeBSD NFSv4.1 nfsd support named attributes (e.g. OPENATTR), > > > per https://datatracker.ietf.org/doc/html/rfc5661#section-5.3 > > > > > > ZFS and Solaris UFS support named attributes (via O_XATTR), does > > > FreeBSD do it too? > > No. fork files/resource forks (or whatever you choose to call them) > > have been discussed multiple times. > > > > If I recall correctly, one showstopper was fixing the archive tools. > > There was also the generic argument that Linux doesn't support them. > > Then there was the issue of what VFS/VOP changes were required. > > (The FreeBSD VFS carries vnode locks across VOP calls and is at > > what I would call a lower level than Solaris.) > > --> Which all comes down to who will do the work? > > > > If I recall correctly, there was a time when a group associated with > > CERN needed them to transition away from Solaris. > > That was my team, and there is still the need to do it. What keeps us > FRUSTRATED is the lack of progress. Well, and "no", we cannot do it > ourselves, this is well beyond the expertise my team has. Does anyone have any suggestions on how to proceed? Lionel