available Microsoft Windows drivers versions. Now you can execute:</p>
<blockquote>
+<p class="quote"># mkdir /mnt/dosc</p>
<p class="quote"># mount -t captive-ntfs /dev/hda1 /mnt/dosc</p>
</blockquote>
<li>@{[ a_href 'Preview.html.pl','Technology Preview' ]}</li>
<li>@{[ a_href 'doc/','Developer Documentation' ]}</li>
<li>@{[ a_href 'http://cvs.jankratochvil.net/viewcvs/*checkout*/priv/captive/TODO?rev=HEAD','Known Bugs' ]}</li>
+ <li>Man pages<ul>
+ @{[
+ do {
+ my @mans=(
+ 'captive'=>[7,'Microsoft Windows NT kernel emulation for NTFS disk access'],
+ 'mount.captive'=>[8,'mount(8) interface for NTFS disk access'],
+ 'lufs-captivefs'=>[7,'Linux Userland File System module for NTFS as filesystem'],
+ 'captive-cmdline'=>[1,'Command-line client for captive(7) NTFS disk access'],
+ 'captive-sandbox-server'=>[1,'Security+safety wrapper for NTFS disk access'],
+ 'captive-install-acquire'=>[1,'Find MS Windows XP driver files for NTFS'],
+ 'captive-install-fstab'=>[1,'Manage captive-ntfs /etc/fstab entries'],
+ );
+ my @r;
+ while (@mans) {
+ my $file=shift @mans;
+ my($section,$name)=@{shift @mans};
+ push @r,"<li>".a_href("man/$file.pod.html",$file)."($section) - $name</li>\n";
+ }
+ @r;
+ }
+ ]}
+ </ul></li>
<li>@{[ a_href 'Resources.html.pl','Related Pages' ]}</li>
<li>@{[ a_href 'Thanks.html.pl','Thanks' ]}</li>
</ul>
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>captive-cmdline - Command-line client for B<captive> NTFS disk access</title>
+<link rev="made" href="mailto:root@localhost" />
+</head>
+
+<body style="background-color: white">
+
+<p><a name="__index__"></a></p>
+<!-- INDEX BEGIN -->
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#author">AUTHOR</a></li>
+</ul>
+<!-- INDEX END -->
+
+<hr />
+<p>
+</p>
+<h1><a name="name">NAME</a></h1>
+<p>captive-cmdline - Command-line client for <strong>captive</strong>(7) NTFS disk access</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>Simple <strong>ftp</strong>(1)-like client to access disks by Microsoft Windows drivers.
+Use if <strong>lufs-captivefs</strong>(7) not available; also useful during debugging.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<p>All programs using <strong>captive</strong>(7) library share the common set of configuration
+options:</p>
+<dl>
+<dt><strong><a name="item_%2d%2dfilesystem%3dpathname"><strong>--filesystem</strong>=<strong>pathname</strong></a></strong><br />
+</dt>
+<dd>
+Pathname to <strong>.sys</strong> or <strong>.so</strong> filesystem module file. You will use exactly
+once this option. Possible choices are
+<strong>/usr/local/var/lib/captive/ntfs.sys</strong>
+etc.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dload%2dmodule%3dpathname"><strong>--load-module</strong>=<strong>pathname</strong></a></strong><br />
+</dt>
+<dd>
+Pathname to any W32 module to load w/o initialization. Multiple modules can be
+loaded although in common case you will use just
+<strong>/usr/local/var/lib/captive/ntoskrnl.exe</strong>
+here.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dro"><strong>--ro</strong></a></strong><br />
+</dt>
+<dd>
+Read/write mode: Any write access will be forbidden. You should set this mode
+for <strong>cdfs.sys</strong> (<em>CD-ROM</em> filesystem). This option is mutually exclusive with
+<strong>--blind</strong> and <strong>--rw</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dblind"><strong>--blind</strong></a></strong><br />
+</dt>
+<dd>
+Read/write mode: All writes are just simulated in memory (default). Microsoft
+Windows filesystem driver will see no difference between <strong>--blind</strong> and <strong>--rw</strong>
+although the UNIX image file/device will be open read/only as for <strong>--ro</strong>.
+All the changes get 'written' as long as <strong>captive</strong>(7) program runs - all the
+changes will be lost afterwards. This mode is the most suitable for debugging.
+This option is mutually exclusive with <strong>--ro</strong> and <strong>--rw</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2drw"><strong>--rw</strong></a></strong><br />
+</dt>
+<dd>
+Read/write mode: Write directly to the image file/device. Standard read/write
+disk mode. You should use <strong>--sandbox-server</strong> option in this case to have the
+disk protected against Microsoft Windows filesystem driver crashes. Modified
+disk image blocks are in <strong>--sandbox-server</strong> <strong>--rw</strong> mode buffered in the
+memory and they get reflected to the disk only after successful completion
+of all filesystem operations including filesystem unmount.
+This option is mutually exclusive with <strong>--ro</strong> and <strong>--blind</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dcdrom"><strong>--cdrom</strong></a></strong><br />
+</dt>
+<dd>
+Media type: CD-ROM. You must set this media type for <strong>cdfs.sys</strong>.
+Virtual Microsoft Windows block device driver used by Captive maps to
+<strong>\Device\CdRom0</strong>. This option is mutually exclusive with <strong>--disk</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2ddisk"><strong>--disk</strong></a></strong><br />
+</dt>
+<dd>
+Media type: Disk (default). You must set this media type for all the Microsoft
+Windows filesystem drivers except <strong>cdfs.sys</strong>. Virtual Microsoft Windows block
+device driver used by Captive maps to <strong>\Device\CaptiveHarddisk0</strong>.
+This option is mutually exclusive with <strong>--cdrom</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2ddebug%2dmessages"><strong>--debug-messages</strong></a></strong><br />
+</dt>
+<dd>
+Turn on debugging messages. Be prepared for substation debug output.
+Use of <strong>--syslog</strong> feature is not recommended in this case.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dsandbox%2dserver%3dpathname"><strong>--sandbox-server</strong>=<strong>pathname</strong></a></strong><br />
+</dt>
+<dd>
+Pathname to
+<strong>/usr/local/sbin/captive-sandbox-server</strong>
+program, turns on sandboxing.
+You should always use this option in conjunction with <strong>--rw</strong>, see it for
+details. Although this program is <em>setuid root</em> and it drops it privileges
+to <strong>@CAPTIVE_SANDBOX_SETUID@</strong> user. Your system gets protected by
+<strong>chroot</strong>(2), <strong>setuid</strong>(2), <strong>setgid</strong>(2) and <strong>setrlimit</strong>(2) UNIX security
+features against malicious Microsoft Windows drivers. You should never use this
+option during debugging.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dsandbox%2dserver%2dior%3dior"><strong>--sandbox-server-ior</strong>=<strong>IOR</strong></a></strong><br />
+</dt>
+<dd>
+Specify <em>CORBA IOR</em> of
+<strong>/usr/local/sbin/captive-sandbox-server</strong>
+program, turns on
+sandboxing. Specified <em>CORBA IOR</em> should be the string starting by ``<strong>IOR:</strong>''
+text. This option is useful only for debugging. No sandbox restarting is
+possible in this case.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dno%2dsandbox"><strong>--no-sandbox</strong></a></strong><br />
+</dt>
+<dd>
+Turn off sandboxing feature (default). No
+<strong>/usr/local/sbin/captive-sandbox-server</strong>
+is run. Microsoft Windows filesystem driver is run in native UNIX environment
+without any <em>CORBA</em> separation. This option is recommended only for debugging.
+It is dangerous to use <strong>--rw</strong> together, see its description for the details.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dbug%2dpathname%3dpathname"><strong>--bug-pathname</strong>=<strong>pathname</strong></a></strong><br />
+</dt>
+<dd>
+Pathname to <strong>strftime</strong>(3) for <strong>.captivebug.xml.gz</strong> bugreports. Every crash of
+sandbox child gets bugreported to the specified file. You should attempt to
+minimize the number of operations from the mount operation till the expected
+crash to minimize the snapshot file size. <strong>--sandbox-server</strong> option is
+required for <strong>--bug-pathname</strong>.
+</dd>
+<dd>
+<p><strong>!!! Be aware '.captivebug.xml.gz' will contain data from your disk drive !!!</strong></p>
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dsyslog"><strong>--syslog</strong></a></strong><br />
+</dt>
+<dd>
+Messages sent to <strong>syslog</strong>(3) instead of <em>stderr</em>. This option gets handy
+for <strong>mount</strong>(8) operation as the messages would be lost otherway.
+Watch our for possible ``<strong>Filesystem crash broke dirty object</strong>'' messages where
+some written filesystem data got lost in the case of Microsoft Windows
+filesystem driver crash.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dsyslog%2dfacility%3dfacility"><strong>--syslog-facility</strong>=<strong>facility</strong></a></strong><br />
+</dt>
+<dd>
+<strong>openlog</strong>(3) facility for <strong>--syslog</strong>. See <strong>facility</strong> section of
+<strong>openlog</strong>(3) man page for details. Lowercased values such as <strong>daemon</strong> or
+<strong>user</strong> are supported.
+</dd>
+<p></p></dl>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><strong>captive</strong>(7), <strong>lufs-captivefs</strong>(7)</p>
+<p>
+</p>
+<hr />
+<h1><a name="author">AUTHOR</a></h1>
+<p><table cellspacing="0" cellpadding="0"><tr><td>Jan Kratochvil <<strong><a href="mailto:project-captive@jankratochvil.net">project-captive@jankratochvil.net</a></strong>>,
+<tr><td><td><em><a href="http://www.jankratochvil.net/">http://www.jankratochvil.net/</a></em></table></p>
+
+</body>
+
+</html>
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>captive-install-acquire - Find MS Windows XP driver files for B<NTFS></title>
+<link rev="made" href="mailto:root@localhost" />
+</head>
+
+<body style="background-color: white">
+
+<p><a name="__index__"></a></p>
+<!-- INDEX BEGIN -->
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#author">AUTHOR</a></li>
+</ul>
+<!-- INDEX END -->
+
+<hr />
+<p>
+</p>
+<h1><a name="name">NAME</a></h1>
+<p>captive-install-acquire - Find MS Windows XP driver files for <strong>NTFS</strong></p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>Program acquires the needed <em>Microsoft Windows XP</em> driver files. Multiple
+methods of getting the driver files are supported. All the driver files are
+stored to the directory
+<strong>/usr/local/var/lib/captive/</strong>
+where they are
+expected by <strong>mount.captive</strong>(8).</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<p>Program will run interactively if no action options (<strong>--scan-disks</strong>,
+<strong>--scan-disks-quick</strong>, <strong>--scan-path</strong> or <strong>--microsoft-com</strong>) are specified.
+Otherwise the requested <code>action(s)</code> is proceeded in silent batch mode.</p>
+<dl>
+<dt><strong><a name="item_%2d%2dtext"><strong>--text</strong></a></strong><br />
+</dt>
+<dd>
+Disable <em>Gnome</em> user interface even if <em>X Window System</em> is available.
+You must specify this option as the first one. This option has effect only for
+interactive mode (no action options specified).
+</dd>
+<p></p>
+<dt><strong><a name="item_%2dv%7c%2d%2dverbose"><strong>-v</strong>|<strong>--verbose</strong></a></strong><br />
+</dt>
+<dd>
+Display additional information during disks scanning.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2dn%7c%2d%2ddry"><strong>-n</strong>|<strong>--dry</strong></a></strong><br />
+</dt>
+<dd>
+Perform all the operations but do not modify anything (no drivers are
+stored to
+<strong>/usr/local/var/lib/captive/</strong>
+directory).
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dmodid%2dpath%3dpath"><strong>--modid-path</strong>=<strong>path</strong></a></strong><br />
+</dt>
+<dd>
+Path to <strong>.captivemodid.xml</strong> database (default:
+<strong>/usr/local/etc/w32-mod-id.captivemodid.xml</strong>). This file contains
+identifications (<strong>md5sum</strong>(1)) of known compatible <em>Microsoft Windows XP</em>
+driver files. <strong>captive-install-acquire</strong>(1) will ignore any files not
+identified by this file although you may try to copy them to
+<strong>/usr/local/var/lib/captive/</strong>
+manually for <strong>captive</strong>(7) clients.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dscan%2ddisks"><strong>--scan-disks</strong></a></strong><br />
+</dt>
+<dd>
+Scan all files on any local hard drive (mounted or unmounted) <strong>NTFS</strong> or
+(mounted) <strong>FAT</strong> partitions. This scanning includes <em>cabinet</em> (<strong>.cab</strong>)
+archives. This scanning can last for very long time.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dscan%2ddisks%2dquick"><strong>--scan-disks-quick</strong></a></strong><br />
+</dt>
+<dd>
+Reduced version of <strong>--scan-disks</strong>. Only <strong>windows/system32</strong> subdirectory in
+the root of any local hard drive (mounted or unmounted) <strong>NTFS</strong> or (mounted)
+<strong>FAT</strong> partition is investigated. This scan should find existing driver files
+in already existing <em>Microsoft Windows XP</em> installations.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dscan%2dpath%3dpath%2furi"><strong>--scan-path</strong>=<strong>path/URI</strong></a></strong><br />
+</dt>
+<dd>
+Scan the specified <strong>path/URI</strong> for device driver files. You may use either
+filename (<strong>/tmp/ntoskrnl.ex_</strong>), directory (<strong>/tmp/servicepack.cab</strong>), <strong>NTFS</strong>
+disk file/directory (<strong>file:///dev/hda1#libntfs:/windows/system32</strong>) or remote
+<em>URI</em> filename (<strong><a href="http://server/path/to/ntfs.sys">http://server/path/to/ntfs.sys</a></strong>). Remote <em>URI</em> directory
+(such as <strong><a href="http://server/subdir/">http://server/subdir/</a></strong>) is not supported.
+</dd>
+<dd>
+<p>Possibly specified directory is always scanned recursively.</p>
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dmicrosoft%2dcom"><strong>--microsoft-com</strong></a></strong><br />
+</dt>
+<dd>
+You can download the best available version of needed drivers from
+<em>Microsoft</em>. They can be found in <em>Microsoft Windows XP Service Pack 1
+Checked Build</em> (URL
+<strong><a href="http://www.microsoft.com/WindowsXP/pro/downloads/servicepacks/sp1/checkedbuild.asp">http://www.microsoft.com/WindowsXP/pro/downloads/servicepacks/sp1/checkedbuild.asp</a></strong>)
+</dd>
+<dd>
+<p>Legal: In some countries you need to have valid <em>Microsoft Windows XP</em> license
+to use it.</p>
+</dd>
+<dd>
+<p>Program will need to download approx 29MB of data (the cabinet file is 151MB;
+1MB=1e6B here).</p>
+</dd>
+<p></p></dl>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><strong>captive-install-fstab</strong>(1), <strong>captive</strong>(7), <strong>lufs-captivefs</strong>(7)</p>
+<p>
+</p>
+<hr />
+<h1><a name="author">AUTHOR</a></h1>
+<p><table cellspacing="0" cellpadding="0"><tr><td>Jan Kratochvil <<strong><a href="mailto:project-captive@jankratochvil.net">project-captive@jankratochvil.net</a></strong>>,
+<tr><td><td><em><a href="http://www.jankratochvil.net/">http://www.jankratochvil.net/</a></em></table></p>
+
+</body>
+
+</html>
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>captive-install-fstab - Manage B<captive-ntfs> B</etc/fstab> entries</title>
+<link rev="made" href="mailto:root@localhost" />
+</head>
+
+<body style="background-color: white">
+
+<p><a name="__index__"></a></p>
+<!-- INDEX BEGIN -->
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#author">AUTHOR</a></li>
+</ul>
+<!-- INDEX END -->
+
+<hr />
+<p>
+</p>
+<h1><a name="name">NAME</a></h1>
+<p>captive-install-fstab - Manage <strong>captive-ntfs</strong> <strong>/etc/fstab</strong> entries</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>Program will scan your local disk drive partitions (from <strong>/proc/partitions</strong>)
+and it will add/remove appropriate file-system type <strong>captive-ntfs</strong> entries
+in <strong>/etc/fstab</strong>.</p>
+<p>Destination directory is chosen automatically as <strong>/mnt/captive-</strong>LABEL_NAME
+where <strong>LABEL_NAME</strong> is the label used for the <strong>NTFS</strong> partition. Directory
+<strong>/mnt/captive-</strong> may be used if no volume label is set. Different (numbered)
+directory name is used if multiple disks have the same volume label set.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="item_%2dv%7c%2d%2dverbose"><strong>-v</strong>|<strong>--verbose</strong></a></strong><br />
+</dt>
+<dd>
+Display additional information during disks scanning.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2dn%7c%2d%2ddry"><strong>-n</strong>|<strong>--dry</strong></a></strong><br />
+</dt>
+<dd>
+Perform all the operations but do not modify anything (file <strong>/etc/fstab</strong>).
+You will probably use this option together with [<strong>-v</strong>|<strong>--verbose</strong>].
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dadd"><strong>--add</strong></a></strong><br />
+</dt>
+<dd>
+Add all the found <strong>NTFS</strong> disk drive partitions to <strong>/etc/fstab</strong>.
+Any previous <strong>captive-ntfs</strong> entries will be deleted as described in
+<strong>--remove</strong> option.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dremove"><strong>--remove</strong></a></strong><br />
+</dt>
+<dd>
+Remove all lines of filesystem type <strong>captive-ntfs</strong> and device name in
+<strong>/dev</strong> directory.
+</dd>
+<p></p></dl>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><strong>captive-install-acquire</strong>(1), <strong>captive</strong>(7), <strong>lufs-captivefs</strong>(7)</p>
+<p>
+</p>
+<hr />
+<h1><a name="author">AUTHOR</a></h1>
+<p><table cellspacing="0" cellpadding="0"><tr><td>Jan Kratochvil <<strong><a href="mailto:project-captive@jankratochvil.net">project-captive@jankratochvil.net</a></strong>>,
+<tr><td><td><em><a href="http://www.jankratochvil.net/">http://www.jankratochvil.net/</a></em></table></p>
+
+</body>
+
+</html>
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>captive-sandbox-server - Security+safety wrapper for NTFS disk access</title>
+<link rev="made" href="mailto:root@localhost" />
+</head>
+
+<body style="background-color: white">
+
+<p><a name="__index__"></a></p>
+<!-- INDEX BEGIN -->
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#author">AUTHOR</a></li>
+</ul>
+<!-- INDEX END -->
+
+<hr />
+<p>
+</p>
+<h1><a name="name">NAME</a></h1>
+<p>captive-sandbox-server - Security+safety wrapper for NTFS disk access</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>captive-sandbox-server</strong></p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p>Program implementing separation of emulated <em>Microsoft Windows NT</em> kernel
+environment from the rest of <em>UNIX</em> system. Your system gets protected by
+<strong>chroot</strong>(2), <strong>setuid</strong>(2), <strong>setgid</strong>(2) and <strong>setrlimit</strong>(2) UNIX security
+features against malicious Microsoft Windows drivers.</p>
+<p>Use this program as argument of <strong>--sandbox-server</strong> option of <strong>captive</strong>(7).
+Do not use this option/program during <strong>captive</strong>(7) debugging.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<p>No options are permitted for this command - it will display its <em>CORBA/ORBit</em>
+connection properties on its standard output.</p>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><strong>captive</strong>(7), <strong>captive-cmdline</strong>(1), <strong>lufs-captivefs</strong>(7)</p>
+<p>
+</p>
+<hr />
+<h1><a name="author">AUTHOR</a></h1>
+<p><table cellspacing="0" cellpadding="0"><tr><td>Jan Kratochvil <<strong><a href="mailto:project-captive@jankratochvil.net">project-captive@jankratochvil.net</a></strong>>,
+<tr><td><td><em><a href="http://www.jankratochvil.net/">http://www.jankratochvil.net/</a></em></table></p>
+
+</body>
+
+</html>
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>captive - Microsoft Windows NT kernel emulation for NTFS disk access</title>
+<link rev="made" href="mailto:root@localhost" />
+</head>
+
+<body style="background-color: white">
+
+<p><a name="__index__"></a></p>
+<!-- INDEX BEGIN -->
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#author">AUTHOR</a></li>
+</ul>
+<!-- INDEX END -->
+
+<hr />
+<p>
+</p>
+<h1><a name="name">NAME</a></h1>
+<p>captive - Microsoft Windows NT kernel emulation for NTFS disk access</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p><strong>captive</strong>(7) library allows applications running under the <strong>GNU/Linux</strong>
+operating system to access <strong>NTFS</strong> drives. File system driver compatibility
+with <strong>VFAT</strong>, <strong>ISO9660</strong> and <strong>EXT2</strong> is also provided.</p>
+<p>This man page <strong>captive</strong>(7) show the common options of all <strong>captive</strong>
+clients. You will always use a specific client such as
+<strong>mount.captive</strong>(8) or <strong>captive-cmdline</strong>(1).</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<p>All programs using <strong>captive</strong>(7) library share the common set of configuration
+options:</p>
+<dl>
+<dt><strong><a name="item_%2d%2dfilesystem%3dpathname"><strong>--filesystem</strong>=<strong>pathname</strong></a></strong><br />
+</dt>
+<dd>
+Pathname to <strong>.sys</strong> or <strong>.so</strong> filesystem module file. You will use exactly
+once this option. Possible choices are
+<strong>/usr/local/var/lib/captive/ntfs.sys</strong>
+etc.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dload%2dmodule%3dpathname"><strong>--load-module</strong>=<strong>pathname</strong></a></strong><br />
+</dt>
+<dd>
+Pathname to any W32 module to load w/o initialization. Multiple modules can be
+loaded although in common case you will use just
+<strong>/usr/local/var/lib/captive/ntoskrnl.exe</strong>
+here.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dro"><strong>--ro</strong></a></strong><br />
+</dt>
+<dd>
+Read/write mode: Any write access will be forbidden. You should set this mode
+for <strong>cdfs.sys</strong> (<em>CD-ROM</em> filesystem). This option is mutually exclusive with
+<strong>--blind</strong> and <strong>--rw</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dblind"><strong>--blind</strong></a></strong><br />
+</dt>
+<dd>
+Read/write mode: All writes are just simulated in memory (default). Microsoft
+Windows filesystem driver will see no difference between <strong>--blind</strong> and <strong>--rw</strong>
+although the UNIX image file/device will be open read/only as for <strong>--ro</strong>.
+All the changes get 'written' as long as <strong>captive</strong>(7) program runs - all the
+changes will be lost afterwards. This mode is the most suitable for debugging.
+This option is mutually exclusive with <strong>--ro</strong> and <strong>--rw</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2drw"><strong>--rw</strong></a></strong><br />
+</dt>
+<dd>
+Read/write mode: Write directly to the image file/device. Standard read/write
+disk mode. You should use <strong>--sandbox-server</strong> option in this case to have the
+disk protected against Microsoft Windows filesystem driver crashes. Modified
+disk image blocks are in <strong>--sandbox-server</strong> <strong>--rw</strong> mode buffered in the
+memory and they get reflected to the disk only after successful completion
+of all filesystem operations including filesystem unmount.
+This option is mutually exclusive with <strong>--ro</strong> and <strong>--blind</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dcdrom"><strong>--cdrom</strong></a></strong><br />
+</dt>
+<dd>
+Media type: CD-ROM. You must set this media type for <strong>cdfs.sys</strong>.
+Virtual Microsoft Windows block device driver used by Captive maps to
+<strong>\Device\CdRom0</strong>. This option is mutually exclusive with <strong>--disk</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2ddisk"><strong>--disk</strong></a></strong><br />
+</dt>
+<dd>
+Media type: Disk (default). You must set this media type for all the Microsoft
+Windows filesystem drivers except <strong>cdfs.sys</strong>. Virtual Microsoft Windows block
+device driver used by Captive maps to <strong>\Device\CaptiveHarddisk0</strong>.
+This option is mutually exclusive with <strong>--cdrom</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2ddebug%2dmessages"><strong>--debug-messages</strong></a></strong><br />
+</dt>
+<dd>
+Turn on debugging messages. Be prepared for substation debug output.
+Use of <strong>--syslog</strong> feature is not recommended in this case.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dsandbox%2dserver%3dpathname"><strong>--sandbox-server</strong>=<strong>pathname</strong></a></strong><br />
+</dt>
+<dd>
+Pathname to
+<strong>/usr/local/sbin/captive-sandbox-server</strong>
+program, turns on sandboxing.
+You should always use this option in conjunction with <strong>--rw</strong>, see it for
+details. Although this program is <em>setuid root</em> and it drops it privileges
+to <strong>@CAPTIVE_SANDBOX_SETUID@</strong> user. Your system gets protected by
+<strong>chroot</strong>(2), <strong>setuid</strong>(2), <strong>setgid</strong>(2) and <strong>setrlimit</strong>(2) UNIX security
+features against malicious Microsoft Windows drivers. You should never use this
+option during debugging.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dsandbox%2dserver%2dior%3dior"><strong>--sandbox-server-ior</strong>=<strong>IOR</strong></a></strong><br />
+</dt>
+<dd>
+Specify <em>CORBA IOR</em> of
+<strong>/usr/local/sbin/captive-sandbox-server</strong>
+program, turns on
+sandboxing. Specified <em>CORBA IOR</em> should be the string starting by ``<strong>IOR:</strong>''
+text. This option is useful only for debugging. No sandbox restarting is
+possible in this case.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dno%2dsandbox"><strong>--no-sandbox</strong></a></strong><br />
+</dt>
+<dd>
+Turn off sandboxing feature (default). No
+<strong>/usr/local/sbin/captive-sandbox-server</strong>
+is run. Microsoft Windows filesystem driver is run in native UNIX environment
+without any <em>CORBA</em> separation. This option is recommended only for debugging.
+It is dangerous to use <strong>--rw</strong> together, see its description for the details.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dbug%2dpathname%3dpathname"><strong>--bug-pathname</strong>=<strong>pathname</strong></a></strong><br />
+</dt>
+<dd>
+Pathname to <strong>strftime</strong>(3) for <strong>.captivebug.xml.gz</strong> bugreports. Every crash of
+sandbox child gets bugreported to the specified file. You should attempt to
+minimize the number of operations from the mount operation till the expected
+crash to minimize the snapshot file size. <strong>--sandbox-server</strong> option is
+required for <strong>--bug-pathname</strong>.
+</dd>
+<dd>
+<p><strong>!!! Be aware '.captivebug.xml.gz' will contain data from your disk drive !!!</strong></p>
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dsyslog"><strong>--syslog</strong></a></strong><br />
+</dt>
+<dd>
+Messages sent to <strong>syslog</strong>(3) instead of <em>stderr</em>. This option gets handy
+for <strong>mount</strong>(8) operation as the messages would be lost otherway.
+Watch our for possible ``<strong>Filesystem crash broke dirty object</strong>'' messages where
+some written filesystem data got lost in the case of Microsoft Windows
+filesystem driver crash.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dsyslog%2dfacility%3dfacility"><strong>--syslog-facility</strong>=<strong>facility</strong></a></strong><br />
+</dt>
+<dd>
+<strong>openlog</strong>(3) facility for <strong>--syslog</strong>. See <strong>facility</strong> section of
+<strong>openlog</strong>(3) man page for details. Lowercased values such as <strong>daemon</strong> or
+<strong>user</strong> are supported.
+</dd>
+<p></p></dl>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><strong>mount.captive</strong>(8), <strong>captive-cmdline</strong>(1), <strong>captive-install-acquire</strong>(1)</p>
+<p>
+</p>
+<hr />
+<h1><a name="author">AUTHOR</a></h1>
+<p><table cellspacing="0" cellpadding="0"><tr><td>Jan Kratochvil <<strong><a href="mailto:project-captive@jankratochvil.net">project-captive@jankratochvil.net</a></strong>>,
+<tr><td><td><em><a href="http://www.jankratochvil.net/">http://www.jankratochvil.net/</a></em></table></p>
+
+</body>
+
+</html>
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>lufs-captivefs - Linux Userland File System module for NTFS as filesystem</title>
+<link rev="made" href="mailto:root@localhost" />
+</head>
+
+<body style="background-color: white">
+
+<p><a name="__index__"></a></p>
+<!-- INDEX BEGIN -->
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#author">AUTHOR</a></li>
+</ul>
+<!-- INDEX END -->
+
+<hr />
+<p>
+</p>
+<h1><a name="name">NAME</a></h1>
+<p>lufs-captivefs - Linux Userland File System module for NTFS as filesystem</p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p><strong>lufs-captivefs</strong>(7) module for Linux Userland File System (LUFS) enables
+<strong>GNU/Linux</strong> system to access NTFS drives by Microsoft Windows drivers in
+the most common way of kernel-level filesystem implementation.</p>
+<p>{<strong>-c CHAN</strong>|<strong>--channels</strong>=<strong>CHAN</strong>} option of <strong>lufsmount</strong>(1) is respected
+although the final filesystem operations are always processed in single-channel
+mode. Do not set <strong>CHAN</strong> to <strong>1</strong> as it would invoke errors by LUFS kernel
+driver.</p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<p>All programs using <strong>captive</strong>(7) library share the common set of configuration
+options:</p>
+<dl>
+<dt><strong><a name="item_%2d%2dfilesystem%3dpathname"><strong>--filesystem</strong>=<strong>pathname</strong></a></strong><br />
+</dt>
+<dd>
+Pathname to <strong>.sys</strong> or <strong>.so</strong> filesystem module file. You will use exactly
+once this option. Possible choices are
+<strong>/usr/local/var/lib/captive/ntfs.sys</strong>
+etc.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dload%2dmodule%3dpathname"><strong>--load-module</strong>=<strong>pathname</strong></a></strong><br />
+</dt>
+<dd>
+Pathname to any W32 module to load w/o initialization. Multiple modules can be
+loaded although in common case you will use just
+<strong>/usr/local/var/lib/captive/ntoskrnl.exe</strong>
+here.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dro"><strong>--ro</strong></a></strong><br />
+</dt>
+<dd>
+Read/write mode: Any write access will be forbidden. You should set this mode
+for <strong>cdfs.sys</strong> (<em>CD-ROM</em> filesystem). This option is mutually exclusive with
+<strong>--blind</strong> and <strong>--rw</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dblind"><strong>--blind</strong></a></strong><br />
+</dt>
+<dd>
+Read/write mode: All writes are just simulated in memory (default). Microsoft
+Windows filesystem driver will see no difference between <strong>--blind</strong> and <strong>--rw</strong>
+although the UNIX image file/device will be open read/only as for <strong>--ro</strong>.
+All the changes get 'written' as long as <strong>captive</strong>(7) program runs - all the
+changes will be lost afterwards. This mode is the most suitable for debugging.
+This option is mutually exclusive with <strong>--ro</strong> and <strong>--rw</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2drw"><strong>--rw</strong></a></strong><br />
+</dt>
+<dd>
+Read/write mode: Write directly to the image file/device. Standard read/write
+disk mode. You should use <strong>--sandbox-server</strong> option in this case to have the
+disk protected against Microsoft Windows filesystem driver crashes. Modified
+disk image blocks are in <strong>--sandbox-server</strong> <strong>--rw</strong> mode buffered in the
+memory and they get reflected to the disk only after successful completion
+of all filesystem operations including filesystem unmount.
+This option is mutually exclusive with <strong>--ro</strong> and <strong>--blind</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dcdrom"><strong>--cdrom</strong></a></strong><br />
+</dt>
+<dd>
+Media type: CD-ROM. You must set this media type for <strong>cdfs.sys</strong>.
+Virtual Microsoft Windows block device driver used by Captive maps to
+<strong>\Device\CdRom0</strong>. This option is mutually exclusive with <strong>--disk</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2ddisk"><strong>--disk</strong></a></strong><br />
+</dt>
+<dd>
+Media type: Disk (default). You must set this media type for all the Microsoft
+Windows filesystem drivers except <strong>cdfs.sys</strong>. Virtual Microsoft Windows block
+device driver used by Captive maps to <strong>\Device\CaptiveHarddisk0</strong>.
+This option is mutually exclusive with <strong>--cdrom</strong>.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2ddebug%2dmessages"><strong>--debug-messages</strong></a></strong><br />
+</dt>
+<dd>
+Turn on debugging messages. Be prepared for substation debug output.
+Use of <strong>--syslog</strong> feature is not recommended in this case.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dsandbox%2dserver%3dpathname"><strong>--sandbox-server</strong>=<strong>pathname</strong></a></strong><br />
+</dt>
+<dd>
+Pathname to
+<strong>/usr/local/sbin/captive-sandbox-server</strong>
+program, turns on sandboxing.
+You should always use this option in conjunction with <strong>--rw</strong>, see it for
+details. Although this program is <em>setuid root</em> and it drops it privileges
+to <strong>@CAPTIVE_SANDBOX_SETUID@</strong> user. Your system gets protected by
+<strong>chroot</strong>(2), <strong>setuid</strong>(2), <strong>setgid</strong>(2) and <strong>setrlimit</strong>(2) UNIX security
+features against malicious Microsoft Windows drivers. You should never use this
+option during debugging.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dsandbox%2dserver%2dior%3dior"><strong>--sandbox-server-ior</strong>=<strong>IOR</strong></a></strong><br />
+</dt>
+<dd>
+Specify <em>CORBA IOR</em> of
+<strong>/usr/local/sbin/captive-sandbox-server</strong>
+program, turns on
+sandboxing. Specified <em>CORBA IOR</em> should be the string starting by ``<strong>IOR:</strong>''
+text. This option is useful only for debugging. No sandbox restarting is
+possible in this case.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dno%2dsandbox"><strong>--no-sandbox</strong></a></strong><br />
+</dt>
+<dd>
+Turn off sandboxing feature (default). No
+<strong>/usr/local/sbin/captive-sandbox-server</strong>
+is run. Microsoft Windows filesystem driver is run in native UNIX environment
+without any <em>CORBA</em> separation. This option is recommended only for debugging.
+It is dangerous to use <strong>--rw</strong> together, see its description for the details.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dbug%2dpathname%3dpathname"><strong>--bug-pathname</strong>=<strong>pathname</strong></a></strong><br />
+</dt>
+<dd>
+Pathname to <strong>strftime</strong>(3) for <strong>.captivebug.xml.gz</strong> bugreports. Every crash of
+sandbox child gets bugreported to the specified file. You should attempt to
+minimize the number of operations from the mount operation till the expected
+crash to minimize the snapshot file size. <strong>--sandbox-server</strong> option is
+required for <strong>--bug-pathname</strong>.
+</dd>
+<dd>
+<p><strong>!!! Be aware '.captivebug.xml.gz' will contain data from your disk drive !!!</strong></p>
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dsyslog"><strong>--syslog</strong></a></strong><br />
+</dt>
+<dd>
+Messages sent to <strong>syslog</strong>(3) instead of <em>stderr</em>. This option gets handy
+for <strong>mount</strong>(8) operation as the messages would be lost otherway.
+Watch our for possible ``<strong>Filesystem crash broke dirty object</strong>'' messages where
+some written filesystem data got lost in the case of Microsoft Windows
+filesystem driver crash.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2d%2dsyslog%2dfacility%3dfacility"><strong>--syslog-facility</strong>=<strong>facility</strong></a></strong><br />
+</dt>
+<dd>
+<strong>openlog</strong>(3) facility for <strong>--syslog</strong>. See <strong>facility</strong> section of
+<strong>openlog</strong>(3) man page for details. Lowercased values such as <strong>daemon</strong> or
+<strong>user</strong> are supported.
+</dd>
+<p></p></dl>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><strong>mount.captive</strong>(8), <strong>lufsmount</strong>(1), <strong>captive</strong>(7)</p>
+<p>
+</p>
+<hr />
+<h1><a name="author">AUTHOR</a></h1>
+<p><table cellspacing="0" cellpadding="0"><tr><td>Jan Kratochvil <<strong><a href="mailto:project-captive@jankratochvil.net">project-captive@jankratochvil.net</a></strong>>,
+<tr><td><td><em><a href="http://www.jankratochvil.net/">http://www.jankratochvil.net/</a></em></table></p>
+
+</body>
+
+</html>
--- /dev/null
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<title>mount.captive - B<mount> interface for NTFS disk access</title>
+<link rev="made" href="mailto:root@localhost" />
+</head>
+
+<body style="background-color: white">
+
+<p><a name="__index__"></a></p>
+<!-- INDEX BEGIN -->
+
+<ul>
+
+ <li><a href="#name">NAME</a></li>
+ <li><a href="#synopsis">SYNOPSIS</a></li>
+ <li><a href="#description">DESCRIPTION</a></li>
+ <li><a href="#options">OPTIONS</a></li>
+ <li><a href="#see_also">SEE ALSO</a></li>
+ <li><a href="#author">AUTHOR</a></li>
+</ul>
+<!-- INDEX END -->
+
+<hr />
+<p>
+</p>
+<h1><a name="name">NAME</a></h1>
+<p>mount.captive - <strong>mount</strong>(8) interface for NTFS disk access</p>
+<p>
+</p>
+<hr />
+<h1><a name="synopsis">SYNOPSIS</a></h1>
+<p><strong>mount.ntfs</strong> {<strong>image-file</strong>|<strong>device</strong>} <strong>mountdir</strong>
+[<strong>-n</strong>] [<strong>-v</strong>] [<strong>-o</strong> <strong>options</strong>]</p>
+<p><strong>mount</strong> <strong>-t</strong> <strong>captive-ntfs</strong>
+[<strong>-n</strong>] [<strong>-v</strong>] [<strong>-o</strong> <strong>options</strong>]
+{<strong>image-file</strong>|<strong>device</strong>} <strong>dir</strong></p>
+<p>
+</p>
+<hr />
+<h1><a name="description">DESCRIPTION</a></h1>
+<p><strong>mount.captive</strong>(8) provides <strong>mount</strong>(8) interface to <strong>lufs-captivefs</strong>(7)
+by calling <strong>lufsmount</strong>(1) with appropriate arguments. You should never call
+this command directly - use <strong>mount</strong>(8) instead.</p>
+<p><strong>mount.captive</strong>(8) (<strong>captive</strong> filesystem type) is never used - this command
+is provided just as a base <code>mount(8)</code> interface to <strong>captive</strong>(7). You must always
+use captive-<strong>fstype</strong> filesystem type such as <strong>captive-ntfs</strong>. Other supported
+filesystem types are:
+<strong>ntfs</strong>, <strong>fastfat</strong>, <strong>cdfs</strong>, <strong>ext2fsd</strong></p>
+<p>
+</p>
+<hr />
+<h1><a name="options">OPTIONS</a></h1>
+<dl>
+<dt><strong><a name="item_%7bimage%2dfile%7cdevice%7d">{<strong>image-file</strong>|<strong>device</strong>}</a></strong><br />
+</dt>
+<dd>
+Pathname such as <strong>/dev/hda1</strong> or <strong>/tmp/ntfs.bin</strong>. You should refer to the
+partition name, not the whole device (<strong>/dev/hda</strong> is forbidden).
+<strong>/dev/hda1</strong> may correspond to <strong>/dev/ide/host0/bus0/target0/lun0/part1</strong>
+on your system.
+</dd>
+<p></p>
+<dt><strong><a name="item_mountdir"><strong>mountdir</strong></a></strong><br />
+</dt>
+<dd>
+Existing empty target directory where {<strong>image-file</strong>|<strong>device</strong>} will be
+mounted.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2dn"><strong>-n</strong></a></strong><br />
+</dt>
+<dd>
+Do not modify <strong>/etc/mtab</strong>. This option is currently not supported (ignored),
+<strong>/etc/mtab</strong> is modified notwithstanding.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2dv"><strong>-v</strong></a></strong><br />
+</dt>
+<dd>
+Enable verbose mode. Command <strong>lufsmount</strong>(1) being called is shown.
+</dd>
+<p></p>
+<dt><strong><a name="item_%2do_options"><strong>-o</strong> <strong>options</strong></a></strong><br />
+</dt>
+<dd>
+Custom options passed to <strong>captive</strong>(7). See its manpage for details. Options
+double-dashes (<strong>--</strong>) can be omitted for <strong>lufs-captivefs</strong>(7) or
+<strong>mount.captive</strong>(8).
+</dd>
+<p></p></dl>
+<p>
+</p>
+<hr />
+<h1><a name="see_also">SEE ALSO</a></h1>
+<p><strong>lufs-captivefs</strong>(7), <strong>lufsmount</strong>(1)</p>
+<p>
+</p>
+<hr />
+<h1><a name="author">AUTHOR</a></h1>
+<p><table cellspacing="0" cellpadding="0"><tr><td>Jan Kratochvil <<strong><a href="mailto:project-captive@jankratochvil.net">project-captive@jankratochvil.net</a></strong>>,
+<tr><td><td><em><a href="http://www.jankratochvil.net/">http://www.jankratochvil.net/</a></em></table></p>
+
+</body>
+
+</html>
git://git.jankratochvil.net / www.jankratochvil.net.git / commitdiff