Date: Tue, 24 Aug 2010 08:09:04 -0400 From: Christer Solstrand Johannessen <christer@csj.no> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: RE: Lingua franca file system Linux-NetBSD-FreeBSD? Message-ID: <AFA3E13074D7694F80D9DA93D46FDBAC483D534D68@IAD2MBX02.mex02.mlsrvr.com> In-Reply-To: <20100824125442.25f45233.freebsd@edvax.de> References: <4c739685.g1aaLUnEPIT1pDne%mueller6727@bellsouth.net> <20100824125442.25f45233.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd- > questions@freebsd.org] On Behalf Of Polytropon > Sent: 24. august 2010 12:55 > To: Thomas Mueller > Cc: freebsd-questions@freebsd.org > Subject: Re: Lingua franca file system Linux-NetBSD-FreeBSD? >=20 =20 > > Also, Linux and the BSDs go separate ways with some newer file > > systems (ext4fs, btrfs, jfs in Linux; zfs in FreeBSD). >=20 > An option would be to avoid the file system level at all. Maybe > that's > not a solution to your requirements, but let me mention this: In a > interoperability environment, I did use a disk enclosure with > built-in > FTP server. In this way, all OSes can r/w access its content via > FTP. > There are no limits regarding 8.3 filenames. Even MacOS X runs > well > in such a setting. The downside, of course, is that you have to > run > a FTP session for every transfer (instead of just mounting a > disk's > partition), but it's basically no problem to use a kind of "FTP- > backed > file system", I think I have seen this in some KDE or Gnome... I've successfully used CIFS/Samba and NFS between Linux, OpenBSD, FreeBSD, Solaris and Windows for years. Easy to set up and works well. If there are no Windows clients involved, I'd use NFS or AFS; with Windows in the mix, CIFS/Samba may be a better choice as Windows NFS clients are dodgy at best. - Christer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AFA3E13074D7694F80D9DA93D46FDBAC483D534D68>