Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 13 Mar 2014 18:32:10 -0400
From:      Richard Yao <ryao@gentoo.org>
To:        Julio Merino <jmmv@freebsd.org>
Cc:        freebsd-hackers@freebsd.org, CeDeROM <cederom@tlen.pl>
Subject:   Re: GSoC proposition: multiplatform UFS2 driver
Message-ID:  <532231EA.5090601@gentoo.org>
In-Reply-To: <53223140.9030208@gentoo.org>
References:  <CAFYkXjm1fCQDSvHTHSpmAbLPqNz0kwaWf%2BajLdaoBD3bLnMDAA@mail.gmail.com> <5321EF7E.7000500@gentoo.org> <CAFY7cWCqTUmASq3vSiRGtoiUOg4Us--o-VOxEp5L5R7wNN%2B2tw@mail.gmail.com> <53223140.9030208@gentoo.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--u0B2s4q76vRBhNuqVFtM7ERWW8rfbKRX6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 03/13/2014 06:29 PM, Richard Yao wrote:
> On 03/13/2014 06:12 PM, Julio Merino wrote:
>> On Fri, Mar 14, 2014 at 2:48 AM, Richard Yao <ryao@gentoo.org> wrote:
>>> On 03/12/2014 12:54 PM, CeDeROM wrote:
>>>> My proposition is to create universal UFS2 driver that would work on=

>>>> Windows, Linux, and maybe other OS, so we can use native UFS2 as dat=
a
>>>> partition among various OS.
>>>>
>>>
>>> I like this idea. In particular, I would like to have UFS2 SU+J
>>> available for use in certain Linux VMs and was thinking about this
>>> possibility earlier in the week. However, I no longer qualify to be a=

>>> GSoC student and I do not have time to do it myself.
>>> [...]
>>> Speaking as a kernel filesystem hacker (with most of my experience in=

>>> Linux), I think this could be too ambitious depending on how you add
>>> detail. In particular, Linux has a moving target of a VFS (which caus=
es
>>> much pain) and Windows' IFS is very different from the SunOS VFS that=

>>> has become the basis for implementing multiple filesystems on differe=
nt
>>> UNIX implementations and copy-cats.
>> [...]
>>
>> Something worth pointing out here: in NetBSD, and thanks to rump, you
>> can already get the *verbatim* in-kernel code of UFS2 built on a
>> variety of host platforms. You could very easily turn the existing
>> file system code into a FUSE file-system for Linux, for example, or
>> write the necessary shims to bundle the code into a kernel driver.
>=20
> This would work, but I think it dramatically reduces the value of the
> result.
>=20
>> In other words and in my opinion: rewriting file system code from
>> scratch is outside of the scope of GSoC, but writing the glue code for=

>> the above to happen doesn't sound too crazy. (The only problem may be
>> if NetBSD's UFS2 driver is not compatible with FreeBSD's... but I
>> believe they should be for the "basic stuff".)
>>
>> Some links:
>>
>> https://github.com/rumpkernel/buildrump.sh
>> http://wiki.netbsd.org/rumpkernel/
>>
>=20
> There is no need to write the code from scratch. He would just need to
> take the existing code and wrap it so that it builds as part of a kerne=
l
> module for other kernels. The only things that need to be written is
> glue code for mapping *BSD interfaces to foreign ones. I do not think i=
t
> is much more complex than writing a FUSE filesystem driver, especially
> given the existence of user-mode Linux. That would permit the filesyste=
m
> driver for Linux to be developed in userland on FreeBSD, much like a
> FUSE driver. Once the wrapper is written, the things that need revision=

> to support other kernels should be rather clearly defined.
>=20
> http://user-mode-linux.sourceforge.net/
>=20
> That being said, I do not like the idea of using NetBSD's UFS2 code. It=

> lacks Soft-Updates, which I consider to make FreeBSD UFS2 second only t=
o
> ZFS in desirability.
>=20

Something worth pointing out here that I missed is that rump could be
used to develop a port of FreeBSD UFS2 to NetBSD. ;)


--u0B2s4q76vRBhNuqVFtM7ERWW8rfbKRX6
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJTIjHxAAoJECDuEZm+6ExkoS0P/iuFyMM/QDj7REH5v8hvhLn1
8iWzWr6vJ0syRUf2KXNLHaz7IpkgYjESSWnEgZfIaoMN/QgkQRiKBFOYfbg1jw09
Ve1kInk7CY/0DoEf3Bokw4stgArzURhT4bjQGoNhUD8sRXxFbMdvX0pqdsv7JIFq
zKPkJuNfTdV+32SYlNlWQoIj8P+nKfHj6EH4ghdEVCyoxFdtA5uO5eY6bUi2DHUj
kcJP8tBzinGvP0HYzeZ4HtQbS0Zhln7WCHI2x9iEHRUq0ADZMrTE8+14icz5hoRz
bD9k3KasOsMa0TFTyGGhML7BG6GAF3/7FMSH01QHjCPP/DxFREbJqwSjdNzHstvr
2sqP/QXercOeanweZVK0CmAIveezpkqDzQjxBCRhsgoJAEVFXdIoGvH8oC4641Oo
XOoC4x/6CnDKs1sE9fHHTqgeE6hNb6vgbUUCg1aVqZta4TgVUk8lrxHdvuJWoCIZ
ysSfHoGbIgbVlRIriuHpTIDdv/YQFftR5KRO0qdYBe78T1gD03whcAqsW+QSNGmS
G5iCsPmcgvGGqI7sY15+5yu1qJr5OlpterV1FlL7oC558igdCi+BUc0EA5k3GwJm
RECzt7P7YLuyHZ1DMu6NiBkTsScTdrUOPb4ZKA5UH0AowejGS8ga7f2WTNGGe32d
n1JHahZoBkjJCh7oCs+J
=zNGF
-----END PGP SIGNATURE-----

--u0B2s4q76vRBhNuqVFtM7ERWW8rfbKRX6--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?532231EA.5090601>