From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Conrad Meyer <cem@freebsd.org>
Cc: Cy Schubert <Cy.Schubert@cschubert.com>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Carlos Maiolino <cmaiolino@redhat.com>,
"freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>,
Eric Sandeen <sandeen@redhat.com>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: FreeBSD and xfsprogs ?
Date: Tue, 27 Mar 2018 09:07:14 -0700 [thread overview]
Message-ID: <20180327160714.GB4818@magnolia> (raw)
In-Reply-To: <CAG6CVpXi3rb-NfLUXQqzStipmwRviKJPMpgKeQA9DfBmOWJ5oQ@mail.gmail.com>
[cc the xfsprogs maintainer]
[cc xfs list]
On Mon, Mar 26, 2018 at 12:57:55PM -0700, Conrad Meyer wrote:
> Yeah, someone broke the build recently via a base toolchain change or
> a ports framework/compiler change. I don't think that changes
> anything.
>
> On Mon, Mar 26, 2018 at 12:53 PM, Cy Schubert <Cy.Schubert@cschubert.com> wrote:
> > In message <CAG6CVpU3qe10UUY6B-N4fs9WTwwUerVcJh0CrP22D8hvB4Z14Q@mail.gma
> > il.com>
> > , Conrad Meyer writes:
> >> On Fri, Mar 23, 2018 at 12:18 PM, Luis R. Rodriguez <mcgrof@kernel.org> wrote
> >> :
> >> > On the Linux xfs development list there is an RFC to remove IRIX,
> >> > Darwin, and FreeBSD support from xfsprogs, the userspace program used
> >> > to create/interact with XFS filesystems. Just wanted to poke and check
> >> > to ensure that FreeBSD is not interested in XFS, if this is incorrect
> >> > now would be the good time to chime into the list and discussion.
> >> >
> >> > [0] https://lkml.kernel.org/r/20180322202102.wpff347scdmfpv62@odin.usersys.
> >> redhat.com
> >>
> >> Hi Luis,
> >>
> >> FreeBSD 11+ can mount XFS filesystems read and write via a FUSE port
> >> incorporating LKL[0] (sysutils/fusefs-lkl). I would appreciate
Yikes. I'm curious, how many people use fusefs-lkl?
Eric will have more to say about this, but is your xfsprogs port still
on 3.2.4 because ./configure can't find libblkid?
--D
> >> xfsprogs retaining FreeBSD support at least for creating or modifying
> >> offline XFS filesystems, if it isn't too painful for you.
> > fusefs-lkl is flagged broken as of r465272.
> >
> >
> > --
> > Cheers,
> > Cy Schubert <Cy.Schubert@cschubert.com>
> > FreeBSD UNIX: <cy@FreeBSD.org> Web: http://www.FreeBSD.org
> >
> > The need of the many outweighs the greed of the few.
> >
> >
next parent reply other threads:[~2018-03-27 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG6CVpU3qe10UUY6B-N4fs9WTwwUerVcJh0CrP22D8hvB4Z14Q@mail.gmail.com>
[not found] ` <201803261953.w2QJrYQm028227@slippy.cwsent.com>
[not found] ` <CAG6CVpXi3rb-NfLUXQqzStipmwRviKJPMpgKeQA9DfBmOWJ5oQ@mail.gmail.com>
2018-03-27 16:07 ` Darrick J. Wong [this message]
2018-03-27 16:48 ` FreeBSD and xfsprogs ? Eric Sandeen
2018-03-27 22:32 ` Dave Chinner
2018-03-28 12:02 ` Christoph Hellwig
2018-04-03 16:12 ` Eric Sandeen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180327160714.GB4818@magnolia \
--to=darrick.wong@oracle.com \
--cc=Cy.Schubert@cschubert.com \
--cc=cem@freebsd.org \
--cc=cmaiolino@redhat.com \
--cc=freebsd-arch@freebsd.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=sandeen@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).