For :

diff -u faq9.html.orig faq9.html
--- faq9.html.orig    2015-12-28 02:20:43.148113257 +0100
+++ faq9.html    2015-12-28 03:42:08.119953895 +0100
@@ -33,6 +33,7 @@
 Edition-style) password file to BSD-style.</a>
 <li><a href= "#Interact">9.4 - Running Linux binaries on OpenBSD</a>
 <li><a href= "#Ext2FS">9.5 - Accessing your Linux files from OpenBSD</a>
+<li><a href= "#UFSisFFS">9.6 - Accessing your OpenBSD files from Linux</a>

 For more information for Linux users, please refer to <a href="";></a>.
@@ -381,6 +382,31 @@
 For further information, see <a href="faq14.html#foreignfs">FAQ 14</a>.

+<h2 id="UFSisFFS">9.6 - Accessing your OpenBSD files from Linux</h2>
+While documenting the features of other operating systems is
+technically out of scope for this FAQ, users migrating or
+interoperating between Linux and OpenBSD may find themselves wanting to
+access OpenBSD FFS partitions from Linux. Users are advised that at
+least <a href="";>this
+common Linux implementation</a> of mount refers to FFS as UFS (for more
+names, <a href="";>see
+Wikipedia</a>), and that said mount command requires users to specify a
+ufstype option of 44bsd, i.e. use <tt>-o ufstype=44bsd</tt> in addition
+to <tt>-t ufs</tt>, because that program's FFS support defaults to a
+ufstype of old, which is probably helpful to the fewest number of FFS
+users. It may be a good idea to run <tt>dmesg|tail</tt> on the Linux
+system after mounting. As of this writing, a helpful example of ufstype
+option usage and a warning that an incorrect or omitted ufstype might
+cause data corruption ("<i>Wrong ufstype may corrupt your filesystem,
+default is ufstype=old</i>") may show up in the Linux dmesg, but is not
+included in the corresponding mount man page.<br />
+The OpenBSD project does not audit the FFS support code of other
+operating systems, so given a choice between accessing a Linux
+partition from OpenBSD and accessing an OpenBSD partition from Linux,
+the former may be preferable. <i>Caveat emptor.</i>

Reply via email to