Date: Fri, 31 Jan 2014 09:20:38 -0800 From: Freddie Cash <fjwcash@gmail.com> To: Polytropon <freebsd@edvax.de> Cc: FreeBSD Filesystems <freebsd-fs@freebsd.org>, FreeBSD Questions Mailing List <freebsd-questions@freebsd.org>, CeDeROM <cederom@tlen.pl> Subject: Re: UFS(2) portable driver for other OS Message-ID: <CAOjFWZ4B3W=iXkycTymJb%2BpVnwKPF-tqezcNiBX9C0pCqLy8TQ@mail.gmail.com> In-Reply-To: <20140131150601.53ee40f4.freebsd@edvax.de> References: <CAFYkXj=xGbnVfJuBwXmj%2Bgu5gR7sWxk6o48rJ233N-=eRcTpyw@mail.gmail.com> <20140131150601.53ee40f4.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 31, 2014 at 6:06 AM, Polytropon <freebsd@edvax.de> wrote: > On Fri, 31 Jan 2014 14:41:13 +0100, CeDeROM wrote: > > Hello :-) > > > > Some time ago I have definitely moved from EXT2 to UFS2. This greatly > > improved my speed and stability on FreeBSD, but I somehow lost access > > and portability for other OS in "native" read-write mode. > > The lowest common denominator is msdosfs (DOS FAT) which is > usable in r/w nearly everywhere. If you require long file > names, you need the 16 bit version. This is commonly considered > the "typical solution" for the problem you're describing, even > though it doesn't really look any attractive because, as I > said, it's the _lowest_ common denominator where "lowest" is > determined by the inability of "Windows" products to be > willing to accept anything that isn't made, approved, certified > and sold by MICROS~1. :-) There's also UDF which doesn't suffer from a lot of the issues the FAT16/32/32x does on large-ish devices. FreeBSD, Windows, Linux, MacOSX all support read/write to UDF, although it may depend on the OS version for Windows (I think XP needs a 3rd party driver).=E2=80=8B=E2=80=8B I've used UDF successfully on USB drives, although I don't think you can boot off it. --=20 Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ4B3W=iXkycTymJb%2BpVnwKPF-tqezcNiBX9C0pCqLy8TQ>