--- /dev/null
+/* $Id$
+ * Captive MS-Windows Driver Survey helper.
+ * Copyright (C) 2005 Jan Kratochvil <project-www.jankratochvil.net@jankratochvil.net>
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; exactly version 2 of June 1991 is required
+ *
+ * This program is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ * GNU General Public License for more details.
+ *
+ * You should have received a copy of the GNU General Public License
+ * along with this program; if not, write to the Free Software
+ * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ */
+
+
+// Double-run protection due to the My::Web "text/javascript" compatibility hack.
+if (!window.var_project_captive_DriverSurvey_done) {
+ var var_project_captive_DriverSurvey_done=1;
+
+function DriverSurvey_validate(form)
+{
+ var e_kinds_array=form.elements["kind"];
+ var checked=0;
+ for (var kindi=0;kindi<e_kinds_array.length;kindi++)
+ if (e_kinds_array[kindi].checked)
+ checked++;
+ if (1!=checked) {
+ // FIXME: Unify with: project::captive::DriverSurvey
+ alert("Please check the appropriate leftmost checkmark.");
+ return false;
+ }
+ return true;
+}
+
+function DriverSurvey_error_check()
+{
+ var e_error=document.getElementById("error");
+ if (e_error && e_error.textContent)
+ alert(e_error.textContent);
+}
+
+function DriverSurvey_error_check_delayed()
+{
+ // HACK: 0ms - wait for 'css_inherit.js' finalization.
+ setTimeout('DriverSurvey_error_check();',0);
+}
+
+function display(name,state)
+{
+ var e=document.getElementById(name);
+ if (e)
+ e.style.display=(state ? "table-row" : "none");
+ return e;
+}
+
+var products_shown;
+
+function display_product(producti,state)
+{
+ for (var rowi=0;display("product"+producti+"_row"+rowi,state);rowi++);
+ return !!rowi;
+}
+
+function DriverSurvey_init()
+{
+ DriverSurvey_error_check_delayed();
+ display("product0_row0",0);
+ display_product("next",1);
+ products_shown=1;
+ for (var producti=products_shown;display_product(producti+0);producti++);
+}
+
+function Survey_productnext(form)
+{
+ display("product0_row0",1);
+ display_product(products_shown++,1);
+ if (!display_product(products_shown,0))
+ display_product("next",0);
+ return false;
+}
+
+function click_on(id)
+{
+ var e;
+ if (document.getElementById)
+ e=document.getElementById(id);
+ if (e)
+ e.click();
+}
+
+/* Origin: http://simon.incutio.com/archive/2004/05/26/addLoadEvent */
+function addLoadEvent(func)
+{
+ var onload_orig=window.onload;
+ if (typeof(onload_orig)!='function')
+ window.onload = func;
+ else
+ window.onload = function()
+ {
+ onload_orig();
+ func();
+ };
+}
+
+if (document.getElementById)
+ addLoadEvent(DriverSurvey_init);
+
+}
--- /dev/null
+# $Id$
+# Captive project DriverSurvey page Perl template.
+# Copyright (C) 2005 Jan Kratochvil <project-www.jankratochvil.net@jankratochvil.net>
+#
+# This program is free software; you can redistribute it and/or modify
+# it under the terms of the GNU General Public License as published by
+# the Free Software Foundation; exactly version 2 of June 1991 is required
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program; if not, write to the Free Software
+# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+
+
+package project::captive::DriverSurvey;
+require 5.6.0; # at least 'use warnings;' but we need some 5.6.0+ modules anyway
+our $VERSION=do { my @r=(q$Revision$=~/\d+/g); sprintf "%d.".("%03d"x$#r),@r; };
+our $CVS_ID=q$Id$;
+use strict;
+use warnings;
+
+use My::Web;
+use Apache2::Cookie;
+require Time::Piece::ISO;
+use Carp qw(confess cluck);
+
+
+our $HTML_TEST_QUERY_STRING="captive-static-1.1.6-0.i386.rpm";
+
+
+# It will not return the new cookie if you set one!
+sub cookie(;$)
+{
+my($val)=@_;
+
+ my $trash; # For {"headers_in"} stability.
+ $trash=$W->{"headers_in"}{"Cookie"};
+ $trash=$W->{"headers_in"}{"Cookie2"};
+ my $jar=Apache2::Cookie::Jar->new($W->{"r"});
+ my $name=__PACKAGE__;
+ if (defined $val) {
+ my $cookie=Apache2::Cookie->new($W->{"r"},
+ "name" =>$name,
+ "value" =>$val,
+ "expires"=>"+3M",
+ "domain" =>$W->{"web_hostname"},
+ # No __PACKAGE__ as it needs to be retrieved also from: /project/captive/Index.pm
+ "path" =>"/project/captive/",
+ "secure" =>0,
+ # Do not: # Prevent: Can't bake2 a Netscape cookie
+ # "version"=>1,
+ # as RFCed "Cookie2" somehow does not work and even nobody uses it.
+ );
+ # Do not: $cookie->bake2($W->{"r"});
+ # as RFCed "Cookie2" somehow does not work and even nobody uses it.
+ $cookie->bake($W->{"r"});
+ }
+ # Somehow it may croak on error parsing the cookie headers or whatever.
+ return eval { $jar->cookies($name) };
+}
+
+
+my $COLS=50;
+
+sub nameval($)
+{
+my($name)=@_;
+
+ my $val=$W->{"args"}{$name};
+ return 'name="'.$name.'"'.(!defined $val ? "" : ' value="'.escapeHTML($val).'"');
+}
+
+sub textarea($$;$)
+{
+my($name,$rows,$attr)=@_;
+
+ return <<"HERE";
+ <textarea rows="$rows" cols="$COLS" name="$name"@{[
+ !$attr ? '' : ' '.$attr
+ ]}>@{[ escapeHTML($W->{"args"}{$name}||"") ]}</textarea>
+HERE
+}
+
+sub radio($$;$)
+{
+my($name,$value,$attr)=@_;
+
+ return <<"HERE";
+ <input type="radio" name="$name" value="$value"@{[
+ ($W->{"args"}{$name}||"") ne $value ? '' : ' checked="checked"'
+ ]}@{[
+ !$attr ? '' : ' '.$attr
+ ]} />
+HERE
+}
+
+sub store()
+{
+ my $data="";
+ $data.=<<"HERE";
+stamp: @{[ Time::Piece::ISO::gmtime()."+00:00" ]}
+HERE
+ for my $key (qw(
+ User-Agent
+ Referer
+ _remote_ip
+ )) {
+ next if !defined (my $val=$W->{"headers_in"}{$key});
+ $data.=<<"HERE"
+headers_in::$key=$val
+HERE
+ }
+ $data.="\n";
+ for my $key (sort keys(%{$W->{"args"}})) {
+ next if $key eq "file";
+ next if $key eq "submit";
+ my $val=$W->{"args"}{$key};
+ next if !defined $val;
+ next if $val eq "";
+ $data.=<<"HERE";
+$key:
+$val
+
+HERE
+ }
+ $data.=("-" x 78)."\n\n";
+
+ my $filename=">>".path_abs_disk("./DriverSurvey.out");
+ local *F;
+ open F,$filename or confess "open \"$filename\": $!";
+ print F $data or confess "write \"$filename\": $!";
+ close F or confess "close \"$filename\": $!";
+}
+
+sub submit()
+{
+ return "Please check the appropriate leftmost checkmark."
+ if !$W->{"args"}{"kind"};
+ store();
+ # It works as &Apache2::Cookie::bake uses &err_headers_out - it is a redirect (not 200 OK).
+ cookie(1);
+ My::Web->http_moved("./");
+}
+
+sub handler
+{
+My::Web->init(
+ "title"=>'Captive NTFS - Linux Drivers Availability Survey',
+ "js_push"=>"./DriverSurvey.js",
+ "args_check"=>{
+ "file"=>'^[^/]*$',
+ },
+ "args_persistent"=>{map(($_=>1),qw(
+ file
+ ))},
+ "css_push"=>"./Lib.css",
+ "heading"=>0,
+ "footer"=>0,
+ "no_job"=>1,
+ "http_safe"=>0,
+ );
+
+# Workaround persistence of 'empty' argument - omit it instead.
+do { $$_=undef() if !$$_; } for \$W->{"args"}{"file"};
+
+my $error=submit() if $W->{"args"}{"submit"};
+
+# At least after &submit !
+My::Web->heading();
+
+
+my $PRODUCTS_MAX=5;
+
+
+print <<"HERE";
+
+<h1>Linux Drivers Availability</h1>
+HERE
+
+if (!$error) {
+ print <<"HERE";
+<p>Please take a minute before downloading Captive NTFS to fill in this survey
+for the possibility to extend Captive for free support of other MS-Windows drivers
+(besides the current file system drivers). The original MS-Windows installation
+(<b>ntoskrnl.exe</b>) would not even be needed in such case.</p>
+HERE
+ }
+else {
+ print <<"HERE";
+<p align="center" class="error" id="error">$error</p>
+HERE
+ }
+
+print <<"HERE";
+<form action="DriverSurvey.pm" @{[ form_method "post" ]} onsubmit="return DriverSurvey_validate(this);">
+@{[ input_hidden_persistents() ]}
+<table border="0" width="80%" class="margin-center padded">
+ <tr><td><table border="1" width="100%" class="padded">
+ <tr><td>
+ <p>@{[ radio "kind","owned" ]} I would like such MS-Windows drivers interface
+ - I have a hardware device missing Linux support.</p>
+ <p>@{[ radio "kind","wannabuy" ]} I would like to buy a hardware device
+ but so far I could not as it is not Linux compatible.</p>
+
+ <table border="0" class="vtop">
+ <tr><td style="font-size: larger;" align="center" colspan="2">Incompatible Hardware Details</td></tr>
+HERE
+for my $producti (0..$PRODUCTS_MAX-1) {
+print <<"HERE";
+ <tr id="product${producti}_row0"><td align="center">Product #@{[ 1+$producti ]}</td></tr>
+ <tr id="product${producti}_row1">
+ <td>Vendor (if known) and product name</td>
+ <td><input type="text" size="$COLS" @{[ nameval "product${producti}_name" ]} /></td>
+ </tr>
+ <tr id="product${producti}_row2">
+ <td>Product webpage URL (if known)</td>
+ <td><input type="text" size="$COLS" @{[ nameval "product${producti}_url" ]} /></td>
+ </tr>
+HERE
+ }
+# Just a protection for non-CSS non-JS browsers to no longer display the button:
+if (!$W->{"args"}{"productnext"}) {
+ print <<"HERE";
+ <tr style="display: none;" id="productnext_row0"><td colspan="2"> </td></tr>
+ <tr style="display: none;" id="productnext_row1"><td colspan="2" align="center">
+ <input type="submit" name="productnext" value="More Devices >>>"
+ onclick="return Survey_productnext(this);" />
+ </td></tr>
+HERE
+ }
+print <<"HERE";
+ <!-- cooperate -->
+ <tr><td colspan="2"> </td></tr>
+ <tr>
+ <td rowspan="4">Would you like to cooperate on the driver testing?</td>
+ <td>
+ @{[ radio "coop","yes" ]} Yes, I want to test a snapshot of the driver right now.
+ </td>
+ </tr>
+ <tr><td>
+ @{[ radio "coop","buy" ]} Yes but only if the driver somehow works
+ to buy the device first.
+ </td></tr>
+ <tr><td>
+ @{[ radio "coop","no" ]} No, I do not own the device
+ or I do not want to test it.
+ </td></tr>
+ <tr><td>
+ @{[ radio "coop","other",'id="coop_other_radio"' ]} Other answer:<br />
+ @{[ textarea "coop_other_textarea",2,q{onkeypress="click_on('coop_other_radio');"} ]}
+ </td></tr>
+
+ </table>
+ </td></tr>
+
+ <tr><td>@{[ radio "kind","oss" ]} I know a specific hardware (either mine or just seen)
+ is not compatible but I do not want to use MS-Windows drivers in Linux.
+
+ <p>What are the more specific reasons? Are you aware the drivers in Linux are
+ in many times just reverse engineered out of their MS-Windows counterparts?</p>
+
+ @{[ textarea "kind_oss",3 ]}
+ </td></tr>
+
+ <tr><td>@{[ radio "kind","working" ]} All my hardware is working perfectly in Linux.</td></tr>
+
+ <tr><td>@{[ radio "kind","answered" ]} I already answered this survey before.</td></tr>
+ </table></td></tr>
+
+ <tr><td>Your e-mail; optional but appreciated: <input type="text" size="30" @{[ nameval "email" ]} /></td></tr>
+
+ <tr><td>Comments<br />
+ @{[ textarea "comment",3 ]}
+ </td></tr>
+HERE
+if ($error) {
+ print <<"HERE";
+ <tr><td align="center" class="error">$error</td></tr>
+HERE
+ }
+print <<"HERE";
+ <tr><td align="center">
+ <input type="submit" name="submit" value="@{[
+ $W->{"args"}{"file"}
+ ? "Submit and download ".escapeHTML($W->{"args"}{"file"})
+ : "Submit the survey"
+ ]}" />
+ </td></tr>
+</table>
+</form>
+
+<p>Direct e-mail address: @{[ a_href 'mailto:driversurvey@jankratochvil.net' ]}</p>
+
+HERE
+
+
+exit;
+}
+1;
"priority"=>666,
"summary"=>"The first free NTFS read/write filesystem for GNU/Linux",
"license"=>"GPL",
- "maintenance"=>"update",
+ "maintenance"=>"active",
"language"=>"i386 asm, C, Perl",
"icon"=>"captive-install-acquire-icon.png",
"cvs-of main tree"=>"captive",
"cvs-of branched ReactOS subdir"=>"reactos:captive",
- "cvs-of branched LUFS"=>"lufs:captive",
- "cvs-of 'httpcaptive://' method"=>"gnome-vfs-httpcaptive:captive",
- "cvs-of 'libntfs://' method"=>"ntfsprogs-gnomevfs",
"description"=>sub { return <<"HERE"; },
<p>Project implements the first full read/write free access to NTFS disk drives.
You can mount your Microsoft Windows NT, 200x or XP partition as
.'<td>• '.a_href('#seealso','See Also').'</td>'
.'</tr></table>'
},
+ "project::Lib-init-hook"=>sub {
+ if (my $file=$W->{"args"}{"file"}) {
+ My::Web::header("Refresh"=>"1;url=".path_web("./dist/$file","abs"=>1));
+ }
+ },
);
&{$_}() for reverse @{$W->{"footing_delimit_sub_push"}};
-my %version=(
- map(($_=>["1.1.5","0"]),qw(captive captive-lufs captive-install)),
- "lufs"=>["0.9.7","1captive8"],
- );
+my $version="1.1.6.1";
+my $revision="0";
+
+Wrequire 'project::captive::DriverSurvey';
+my $survey_want=1;
+$survey_want=0 if $W->{"args"}{"file"};
+$survey_want=0 if project::captive::DriverSurvey::cookie();
+
+local *download=sub($)
+{
+my($name)=@_;
+
+ # Do not: ,"attr"=>'target="_blank"'
+ # as it would require Framed XHTML.
+ my $real="dist/$name";
+ return a_href './DriverSurvey.pm?file='.$name,$name,"size"=>$real
+ if $survey_want;
+ return a_href $real,$name,"size"=>1;
+};
print <<"HERE";
<h2 id="download">Download</h2>
<td>
<p>RPM i386 binary<br />tested for distributions:</p>
<table border="0"><tr><td align="left"><ul>
- <li>Red Hat 9 Shrike</li>
- <li>Red Hat 8 Psyche</li>
- <li>SuSE 9.0</li>
- <li>SuSE 9.1</li>
- <li>Mandrake 9.1 Bamboo</li>
+ <li>Fedora Core 4</li>
</ul></td></tr></table>
</td>
- <td>@{[ a_href 'dist/captive-static-'.$version{"captive"}[0].'-'.$version{"captive"}[1].'.i386.rpm',
- undef(),"size"=>1,"basename"=>1 ]}</td>
+ <td>@{[ download("captive-static-$version-$revision.i386.rpm") ]}</td>
</tr>
<tr>
<td>
<p>.tar.gz i386 binary<br />(for non-RPM distributions)</p>
</td>
- <td>@{[ a_href 'dist/captive-static-'.$version{"captive"}[0].'.tar.gz',undef(),"size"=>1,"basename"=>1 ]}</td>
+ <td>@{[ download("captive-static-$version.tar.gz") ]}</td>
</tr>
<tr>
<td>Source archives</td>
<td>@{[ a_href 'CVS.pm#source','download link' ]}</td>
</tr>
</table>
+HERE
-<h4>Development Status</h4>
-
-<p>Project is no longer developed. The key functionality is reached
-by the latest released version. All its resources are available
-@{[ a_href 'CVS.pm#source','here' ]} for download.</p>
-
-<h4>Known Issue</h4>
-
-<p>Captive was written to interface with the Linux kernel via
-@{[ a_href 'http://lufs.sourceforge.net/lufs/','LUFS' ]}.
-Unfortunately, this project is no longer being maintained by its author.
-Mounting of NTFS devices usually works, but is no longer supported by the
-author of Captive. Always unmount the device by umount(8) command before shutting
-down your GNU/Linux system.</p>
-
-<p>A port of Captive to the newer
-@{[ a_href 'http://fuse.sourceforge.net/','FUSE' ]}
-interface has not yet been implemented.
-There is an experimental LUFS-FUSE bridge called
-@{[ a_href 'http://sourceforge.net/project/showfiles.php?group_id=121684','lufis' ]}
-that can be used in the meanwhile.
-Also, the captive-cmdline(1) interface will get around any kernel compatibility
-problems.</p>
+if (!$survey_want) {
+ print <<"HERE";
+<p>@{[ a_href 'DriverSurvey.pm','Linux Drivers Availability survey' ]} link
+- if you already answered before.</p>
+HERE
+ }
+print <<"HERE";
@{[ vskip "3ex" ]}
<h2 id="news">NEWS</h2>
<dl>
- <dt>captive-1.1.5 (2004-01-18) [@{[ a_href $W->{"project_viewcvs"}.'/*checkout*/captive/NEWS?rev=HEAD','archive' ]}]</dt>
+ <dt>captive-1.1.6.1 (2005-12-29) [@{[ a_href $W->{"project_viewcvs"}.'captive/NEWS?rev=HEAD','archive' ]}]</dt>
<dd>
<ul>
- <li>Fixed ignorance of the file truncate operation via LUFS (Matthias R.)</li>
- <li>Support for reading of HIDDEN SYSTEM NTFS files via LUFS</li>
- <li>Fixed refusal to mount some NT4.0 NTFSes (Nerijus Baliunas, Scott Chevalley)</li>
- <li>Support <code>/dev/ataraid</code> devices (Ivan Tonov)</li>
+ <li>New FUSE interface, deprecated LUFS - improve compatibility of Linux kernel</li>
+ <li>Provided script for proper NTFS unmounts during GNU/Linux OS shutdown</li>
+ <li>Updates for recent Microsoft installed binaries and files for download</li>
+ <li>Hopefully survives reading of many small files like on XMMS scanning</li>
+ <li>Improved recent GNU/Linux build environment compatibility</li>
</ul>
</dd>
- <dt>lufs-0.9.7captive8 (2003-12-06) [@{[ a_href $W->{"project_viewcvs"}.'/*checkout*/lufs/NEWS.captive?rev=1.1.2.11','archive' ]}]</dt>
</dl>
@{[ vskip "3ex" ]}
available Microsoft Windows drivers versions. Now you can execute:</p>
<blockquote>
- <p class="quote" style="white-space: pre;"
-># captive-cmdline \\
- --load-module=/var/lib/captive/ntoskrnl.exe \\
- --filesystem=/var/lib/captive/ntfs.sys \\
- --sandbox-server=/usr/sbin/captive-sandbox-server \\
- --bug-pathname=/tmp/captive-bug-%FT%T.captivebug.xml.gz \\
- --disk --rw /dev/hda1
-# Now you can use ftp(1)-like command-line interface for the NTFS disk access.</p
- >
- <p>(Backslash end-of-line characters '\\' to be omitted for line continuation.)</p>
+ <p class="quote">
+ # mkdir /mnt/dosc<br />
+ # mount -t captive-ntfs /dev/hda1 /mnt/dosc
+ </p>
</blockquote>
<h2>Overview</h2>
-<p>Any errors from '<b>captive-lufs</b>' are written to '<b>/var/log/messages</b>'.</p>
+<p>Any errors from '<b>captive-fuse</b>' are written to '<b>/var/log/messages</b>'.</p>
<p>Needed drivers (at least ntoskrnl.exe+ntfs.sys) must be in '<b>/var/lib/captive</b>'.</p>
<p>'<b>captive</b>' package creates '<b>captive</b>' user and '<b>captive</b>' group on your system.</p>
-<h2>LUFS Kernel Driver Module</h2>
-
-<p>@{[ a_href 'http://lufs.sourceforge.net/lufs/','LUFS' ]} (Linux Userland File
-System) needs Linux kernel module driver (<i>lufs.o</i>) compatible with your
-running Linux kernel. The binary driver is supplied already precompiled for many
-Linux kernel versions in the binary packages above (<b>.i386.rpm</b> and
-<b>_i386.deb</b> archives).</p>
+<h2>FUSE Kernel Driver Module</h2>
-<p>If you cannot <b>mount</b>(8) your NTFS filesystem you should run <span
-class="quote">/usr/share/lufs/prepmod</span> to see the reasons. It is always
-recommended to upgrade to the latest stable kernel supplied by your GNU/Linux
-distribution vendor. You may need to install package
-<b>kernel-source</b> (Red Hat) or <b>kernel-headers</b> (Debian) matching your
-Linux kernel version (<b>rpm -q kernel</b>) and re-run <span
-class="quote">/usr/share/lufs/prepmod</span>.</p>
+<p>@{[ a_href 'http://fuse.sourceforge.net/','FUSE' ]} (Filesystem in Userspace)
+needs Linux kernel module driver (<i>fuse.ko</i>) compatible with your
+running Linux kernel.</p>
-<p><b>WARNING:</b> This 'captive' package may modify your Linux kernel
-sources matching your currently running kernel version. These minor
-modifications may include a dependencies rebuild, compiling build tools, fixes of
-several include files, etc. All the modifications are done at the mount(8) time
-by the automatically executed <span class="quote">/usr/share/lufs/prepmod</span> script.
-This behavior was not present in the original
-@{[ a_href 'http://lufs.sourceforge.net/lufs/','LUFS' ]} distribution
-by @{[ a_href 'http://www.malinux.net/main/','Florin Malita' ]}.</p>
+<p>If you cannot <b>mount</b>(8) your NTFS filesystem you should check your
+Linux kernel is based on version at least 2.6.14 where
+@{[ a_href 'http://fuse.sourceforge.net/','FUSE' ]} got imported. You should
+also check the module is enabled or even built-in.</p>
HERE
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'],
.name { font-style: italic; }
+table.padded > tr > td { padding: 15px; }
+table.vtop > tr > td { vertical-align: top; }
Preview.pm \
CVS.pm \
Press.pm \
- TestimonialBrunoSantos.pm
+ TestimonialBrunoSantos.pm \
+ DriverSurvey.pm
+
+EXTRA_DIST+= \
+ DriverSurvey.js
+++ /dev/null
------BEGIN PGP SIGNED MESSAGE-----
-Hash: SHA1
-
-Format: 1.0
-Source: gnome-vfs-httpcaptive
-Version: 2.3.8captive2
-Binary: gnome-vfs-httpcaptive
-Maintainer: Jan Kratochvil <project-captive@jankratochvil.net>
-Architecture: i386
-Standards-Version: 3.5.2
-Build-Depends: debhelper (>> 3.0.0), libgnomevfs2-dev, libglib2.0-dev
-Files:
- 28b11b8bad6afd34358c7164cf115b26 548681 gnome-vfs-httpcaptive_2.3.8captive2.tar.gz
-
------BEGIN PGP SIGNATURE-----
-Version: GnuPG v1.2.3 (GNU/Linux)
-
-iD8DBQE/cQF0zD78uUT8djIRAg0BAJ41drC99NHu0WeZ1jbrOeqBVDskagCgjiBh
-LGCDaoxg6ntOx5MKZezbgbA=
-=R87D
------END PGP SIGNATURE-----
+++ /dev/null
------BEGIN PGP SIGNED MESSAGE-----
-Hash: SHA1
-
-Format: 1.7
-Date: Sun, 17 Aug 2003 14:16:59 +0200
-Source: gnome-vfs-httpcaptive
-Binary: gnome-vfs-httpcaptive
-Architecture: source i386
-Version: 2.3.8captive2
-Distribution: unstable
-Urgency: low
-Maintainer: Jan Kratochvil <project-captive@jankratochvil.net>
-Changed-By: Jan Kratochvil <pgp-44FC7632@jankratochvil.net>
-Description:
- gnome-vfs-httpcaptive - Improved http handler for GNOME virtual file-system libraries
-Changes:
- gnome-vfs-httpcaptive (2.3.8captive2) unstable; urgency=low
- .
- * See package ChangeLog entries.
-Files:
- 17cb718d117e7d9379f82f0bd6921f5e 601 main/base optional gnome-vfs-httpcaptive_2.3.8captive2.dsc
- 28b11b8bad6afd34358c7164cf115b26 548681 main/base optional gnome-vfs-httpcaptive_2.3.8captive2.tar.gz
- ced34037f2394693e125d93569fa3c05 29014 main/base optional gnome-vfs-httpcaptive_2.3.8captive2_i386.deb
-
------BEGIN PGP SIGNATURE-----
-Version: GnuPG v1.2.3 (GNU/Linux)
-
-iD8DBQE/cQF5zD78uUT8djIRAi+lAJ4kX3A7BRernUTWY3ULbjyNhjjSrQCdFBjH
-BMDmPvZSKiguLfa47mNMDbM=
-=cNwB
------END PGP SIGNATURE-----
+++ /dev/null
------BEGIN PGP SIGNED MESSAGE-----
-Hash: SHA1
-
-Format: 1.0
-Source: ntfsprogs-gnomevfs
-Version: 1.0.2
-Binary: ntfsprogs-gnomevfs
-Maintainer: Jan Kratochvil <project-captive@jankratochvil.net>
-Architecture: i386
-Standards-Version: 3.5.2
-Build-Depends: debhelper (>> 3.0.0),
- libgnomevfs2-dev,
- libglib2.0-dev,
- ntfsprogs-dev
-Files:
- 4087f57e2f6a38b2ec8956396b61bc24 312531 ntfsprogs-gnomevfs_1.0.2.tar.gz
-
------BEGIN PGP SIGNATURE-----
-Version: GnuPG v1.2.3 (GNU/Linux)
-
-iD8DBQE/k4zXzD78uUT8djIRAqQKAJ0cxz6Uo7RBg1AXyXBBOgBzFOLsYwCgk1Pq
-q4pv3fUOIAv8zUdOMVRYpV4=
-=KIUE
------END PGP SIGNATURE-----
+++ /dev/null
------BEGIN PGP SIGNED MESSAGE-----
-Hash: SHA1
-
-Format: 1.7
-Date: Sun, 17 Aug 2003 14:16:59 +0200
-Source: ntfsprogs-gnomevfs
-Binary: ntfsprogs-gnomevfs
-Architecture: source i386
-Version: 1.0.2
-Distribution: unstable
-Urgency: low
-Maintainer: Jan Kratochvil <project-captive@jankratochvil.net>
-Changed-By: Jan Kratochvil <pgp-44FC7632@jankratochvil.net>
-Description:
- ntfsprogs-gnomevfs - NTFS filesystem library GNOME virtual file-system interface
-Changes:
- ntfsprogs-gnomevfs (1.0.2) unstable; urgency=low
- .
- * See package ChangeLog entries.
-Files:
- 770c049238a95f00920aff1f08cfdcce 594 main/base optional ntfsprogs-gnomevfs_1.0.2.dsc
- 4087f57e2f6a38b2ec8956396b61bc24 312531 main/base optional ntfsprogs-gnomevfs_1.0.2.tar.gz
- 5833cbaa6611d8afaaf8f10632755fc8 9896 main/base optional ntfsprogs-gnomevfs_1.0.2_i386.deb
-
------BEGIN PGP SIGNATURE-----
-Version: GnuPG v1.2.3 (GNU/Linux)
-
-iD8DBQE/k4zczD78uUT8djIRAni7AJ4zzu9GWno8xcPJ/m/ySrMTLRxlmQCfZEs7
-GYgWB1y2Lm0QeHQtx+VRBRE=
-=RhCE
------END PGP SIGNATURE-----
+++ /dev/null
------BEGIN PGP SIGNED MESSAGE-----
-Hash: SHA1
-
-Format: 1.0
-Source: ntfsprogs
-Version: 200309071734captive1
-Binary: ntfsprogs, ntfsprogs-dev
-Maintainer: Jan Kratochvil <project-captive@jankratochvil.net>
-Architecture: i386
-Standards-Version: 3.5.2
-Files:
- d1d605893444b80fd837301320dd2261 535278 ntfsprogs_200309071734captive1.tar.gz
-
------BEGIN PGP SIGNATURE-----
-Version: GnuPG v1.2.3 (GNU/Linux)
-
-iD8DBQE/bdcpzD78uUT8djIRAjnhAKCE3ofdN1P9M434xfCqJTuqAVSHSQCdFiq1
-0Mg8noB5XT55apyd7hq6RbI=
-=LrBu
------END PGP SIGNATURE-----
+++ /dev/null
------BEGIN PGP SIGNED MESSAGE-----
-Hash: SHA1
-
-Format: 1.7
-Date: Tue, 09 Sep 2003 08:22:48 +0200
-Source: ntfsprogs
-Binary: ntfsprogs ntfsprogs-dev
-Architecture: source i386
-Version: 200309071734captive1
-Distribution: unstable
-Urgency: low
-Maintainer: Jan Kratochvil <project-captive@jankratochvil.net>
-Changed-By: Jan Kratochvil <pgp-44FC7632@jankratochvil.net>
-Description:
- ntfsprogs - NTFS filesystem libraries and utilities
- ntfsprogs-dev - files required to compile software that uses libntfs
-Changes:
- ntfsprogs (200309071734captive1) unstable; urgency=low
- .
- * See package ChangeLog entries.
-Files:
- d4fd74a7e479d42cb3e375c0c50f0694 524 contrib/base optional ntfsprogs_200309071734captive1.dsc
- d1d605893444b80fd837301320dd2261 535278 contrib/base optional ntfsprogs_200309071734captive1.tar.gz
- 202a161dc4b512e94ed4ef65a798b33a 169968 contrib/base optional ntfsprogs_200309071734captive1_i386.deb
- 80b2f06832c66bb07c439f7c7e175b64 91630 contrib/base optional ntfsprogs-dev_200309071734captive1_i386.deb
-
------BEGIN PGP SIGNATURE-----
-Version: GnuPG v1.2.3 (GNU/Linux)
-
-iD8DBQE/bdcuzD78uUT8djIRAvX4AJoC11uEH2aQNfmLgeRGOOU5u0098gCcDHpS
-cN3+Cbhbo775wc68qlvhSqw=
-=FheU
------END PGP SIGNATURE-----
<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">
<!-- INDEX BEGIN -->
<ul>
-
<li><a href="#name">NAME</a></li>
<li><a href="#synopsis">SYNOPSIS</a></li>
<li><a href="#description">DESCRIPTION</a></li>
<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>
+Use if <strong>mount.captive</strong>(8) not available; also useful during debugging.</p>
<p>
</p>
<hr />
<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>
+<dt><strong><a name="item__2d_2dfilesystem_3dpathname"><strong>--filesystem</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-Pathname to <strong>.sys</strong> or <strong>.so</strong> filesystem module file. You will use exactly
+<p>Pathname to <strong>.sys</strong> or <strong>.so</strong> filesystem module file. You will use exactly
once this option. Possible choices are
-<strong>/var/lib/captive/ntfs.sys</strong>
-etc.
+<strong>/usr/local/var/lib/captive/ntfs.sys</strong>
+etc.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dload%2dmodule%3dpathname"><strong>--load-module</strong>=<strong>pathname</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dload_2dmodule_3dpathname"><strong>--load-module</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-Pathname to any W32 module to load w/o initialization. Multiple modules can be
+<p>Pathname to any W32 module to load w/o initialization. Multiple modules can be
loaded although in common case you will use just
-<strong>/var/lib/captive/ntoskrnl.exe</strong>
-here.
+<strong>/usr/local/var/lib/captive/ntoskrnl.exe</strong>
+here.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dro"><strong>--ro</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dmodid_2dpath_3dpathname"><strong>--modid-path</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-Read/write mode: Any write access will be forbidden. You should set this mode
+<p>Pathname to the <strong>.captivemodid.xml</strong> database of existing W32 module
+identifications. The default used one is:
+<strong>/usr/local/etc/w32-mod-id.captivemodid.xml</strong>
+You must have this database update for any W32 binary module you are using.
+If you miss such database you may also try to use <strong>--load-untested</strong> below.</p>
+</dd>
+<dt><strong><a name="item__2d_2dload_2duntested"><strong>--load-untested</strong></a></strong></dt>
+
+<dd>
+<p>Load tthe W32 modules despite they may not match the current <strong>--modid-path</strong>
+identifications database. If you use this option Captive may fail very easily
+as such module was never tested before the release and may need some
+compatibility updates. Still no data should be corrupted even if using this
+<strong>--load-untested</strong> option.</p>
+</dd>
+<dt><strong><a name="item__2d_2dro"><strong>--ro</strong></a></strong></dt>
+
+<dd>
+<p>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>.
+<strong>--blind</strong> and <strong>--rw</strong>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dblind"><strong>--blind</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dblind"><strong>--blind</strong></a></strong></dt>
+
<dd>
-Read/write mode: All writes are just simulated in memory (default). Microsoft
+<p>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>.
+This option is mutually exclusive with <strong>--ro</strong> and <strong>--rw</strong>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2drw"><strong>--rw</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2drw"><strong>--rw</strong></a></strong></dt>
+
<dd>
-Read/write mode: Write directly to the image file/device. Standard read/write
+<p>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>.
+This option is mutually exclusive with <strong>--ro</strong> and <strong>--blind</strong>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dcdrom"><strong>--cdrom</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dcdrom"><strong>--cdrom</strong></a></strong></dt>
+
<dd>
-Media type: CD-ROM. You must set this media type for <strong>cdfs.sys</strong>.
+<p>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>.
+<strong>\Device\CdRom0</strong>. This option is mutually exclusive with <strong>--disk</strong>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2ddisk"><strong>--disk</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2ddisk"><strong>--disk</strong></a></strong></dt>
+
<dd>
-Media type: Disk (default). You must set this media type for all the Microsoft
+<p>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>.
+This option is mutually exclusive with <strong>--cdrom</strong>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2ddebug%2dmessages"><strong>--debug-messages</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2ddebug_2dmessages"><strong>--debug-messages</strong></a></strong></dt>
+
<dd>
-Turn on debugging messages. Be prepared for substation debug output.
-Use of <strong>--syslog</strong> feature is not recommended in this case.
+<p>Turn on debugging messages. Be prepared for substation debug output.
+Use of <strong>--syslog</strong> feature is not recommended in this case.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dsandbox%2dserver%3dpathname"><strong>--sandbox-server</strong>=<strong>pathname</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dsandbox_2dserver_3dpathname"><strong>--sandbox-server</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-Pathname to
-<strong>/usr/sbin/captive-sandbox-server</strong>
+<p>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
+to <strong>captive</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.
+option during debugging.</p>
</dd>
<dd>
<p>This option is turned on automatically during the mount operation by
<strong>mount.captive-ntfs</strong>(8).
Option needs to be used by hand for the <strong>captive-cmdline</strong>(2) client.</p>
</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>
+<dt><strong><a name="item__2d_2dsandbox_2dserver_2dior_3dior"><strong>--sandbox-server-ior</strong>=<strong>IOR</strong></a></strong></dt>
+
<dd>
-Specify <em>CORBA IOR</em> of
-<strong>/usr/sbin/captive-sandbox-server</strong>
+<p>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.
+possible in this case.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dno%2dsandbox"><strong>--no-sandbox</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dno_2dsandbox"><strong>--no-sandbox</strong></a></strong></dt>
+
<dd>
-Turn off sandboxing feature (default). No
-<strong>/usr/sbin/captive-sandbox-server</strong>
+<p>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.
+It is dangerous to use <strong>--rw</strong> together, see its description for the details.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dbug%2dpathname%3dpathname"><strong>--bug-pathname</strong>=<strong>pathname</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dbug_2dpathname_3dpathname"><strong>--bug-pathname</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-Pathname to <strong>strftime</strong>(3) for <strong>.captivebug.xml.gz</strong> bugreports. Every crash of
+<p>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>.
+required for <strong>--bug-pathname</strong>.</p>
</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>
+<dt><strong><a name="item__2d_2dsyslog"><strong>--syslog</strong></a></strong></dt>
+
<dd>
-Messages sent to <strong>syslog</strong>(3) instead of <em>stderr</em>. This option gets handy
+<p>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.
+filesystem driver crash.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dsyslog%2dfacility%3dfacility"><strong>--syslog-facility</strong>=<strong>facility</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dsyslog_2dfacility_3dfacility"><strong>--syslog-facility</strong>=<strong>facility</strong></a></strong></dt>
+
<dd>
-<strong>openlog</strong>(3) facility for <strong>--syslog</strong>. See <strong>facility</strong> section of
+<p><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.
+<strong>user</strong> are supported.</p>
</dd>
-<p></p></dl>
+</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><strong>captive</strong>(7), <strong>mount.captive</strong>(8)</p>
<p>
</p>
<hr />
<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">
<!-- INDEX BEGIN -->
<ul>
-
<li><a href="#name">NAME</a></li>
<li><a href="#synopsis">SYNOPSIS</a></li>
<li><a href="#description">DESCRIPTION</a></li>
<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>/var/lib/captive/</strong>
+<strong>/usr/local/var/lib/captive/</strong>
where they are
expected by <strong>mount.captive</strong>(8).</p>
<p>
<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>
+<dt><strong><a name="item__2d_2dtext"><strong>--text</strong></a></strong></dt>
+
<dd>
-Disable <em>Gnome</em> user interface even if <em>X Window System</em> is available.
+<p>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).
+interactive mode (no action options specified).</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2dv%7c%2d%2dverbose"><strong>-v</strong>|<strong>--verbose</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2dv_7c_2d_2dverbose"><strong>-v</strong>|<strong>--verbose</strong></a></strong></dt>
+
<dd>
-Display additional information during disks scanning.
+<p>Display additional information during disks scanning.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2dn%7c%2d%2ddry"><strong>-n</strong>|<strong>--dry</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2dn_7c_2d_2ddry"><strong>-n</strong>|<strong>--dry</strong></a></strong></dt>
+
<dd>
-Perform all the operations but do not modify anything (no drivers are
+<p>Perform all the operations but do not modify anything (no drivers are
stored to
-<strong>/var/lib/captive/</strong>
-directory).
+<strong>/usr/local/var/lib/captive/</strong>
+directory).</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dmodid%2dpath%3dpath"><strong>--modid-path</strong>=<strong>path</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dmodid_2dpath_3dpath"><strong>--modid-path</strong>=<strong>path</strong></a></strong></dt>
+
<dd>
-Path to <strong>.captivemodid.xml</strong> database (default:
-<strong>/etc/w32-mod-id.captivemodid.xml</strong>). This file contains
+<p>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>/var/lib/captive/</strong>
-manually for <strong>captive</strong>(7) clients.
+<strong>/usr/local/var/lib/captive/</strong>
+manually for <strong>captive</strong>(7) clients.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dscan%2ddisks"><strong>--scan-disks</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dscan_2ddisks"><strong>--scan-disks</strong></a></strong></dt>
+
<dd>
-Scan all files on any local hard drive (mounted or unmounted) <strong>NTFS</strong> or
+<p>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.
+archives. This scanning can last for very long time.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dscan%2ddisks%2dquick"><strong>--scan-disks-quick</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dscan_2ddisks_2dquick"><strong>--scan-disks-quick</strong></a></strong></dt>
+
<dd>
-Reduced version of <strong>--scan-disks</strong>. Only <strong>windows/system32</strong> subdirectory in
+<p>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.
+in already existing <em>Microsoft Windows XP</em> installations.</p>
</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>
+<dt><strong><a name="item__2d_2dscan_2dpath_3dpath_2furi"><strong>--scan-path</strong>=<strong>path/URI</strong></a></strong></dt>
+
<dd>
-Scan the specified <strong>path/URI</strong> for device driver files. You may use either
+<p>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.
+(such as <strong><a href="http://server/subdir/">http://server/subdir/</a></strong>) is not supported.</p>
</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>
+<dt><strong><a name="item__2d_2dmicrosoft_2dcom"><strong>--microsoft-com</strong></a></strong></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
+<p>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 2
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>)
+<strong><a href="http://msdn.microsoft.com/security/productinfo/xpsp2">http://msdn.microsoft.com/security/productinfo/xpsp2</a></strong>)</p>
</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;
+<p>Program will need to download approx 61MB of data (the cabinet file is 307MB;
1MB=1e6B here).</p>
</dd>
-<p></p></dl>
+</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><strong>captive-install-fstab</strong>(1), <strong>captive</strong>(7), <strong>mount.captive</strong>(8)</p>
<p>
</p>
<hr />
<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">
<!-- INDEX BEGIN -->
<ul>
-
<li><a href="#name">NAME</a></li>
<li><a href="#synopsis">SYNOPSIS</a></li>
<li><a href="#description">DESCRIPTION</a></li>
<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>
+<dt><strong><a name="item__2dv_7c_2d_2dverbose"><strong>-v</strong>|<strong>--verbose</strong></a></strong></dt>
+
+<dd>
+<p>Display additional information during disks scanning.</p>
+</dd>
+<dt><strong><a name="item__2dn_7c_2d_2ddry"><strong>-n</strong>|<strong>--dry</strong></a></strong></dt>
+
<dd>
-Display additional information during disks scanning.
+<p>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>].</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2dn%7c%2d%2ddry"><strong>-n</strong>|<strong>--dry</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dadd"><strong>--add</strong></a></strong></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>].
+<p>Add all the found <strong>NTFS</strong> disk drive partitions to <strong>/etc/fstab</strong>.
+Previous <strong>captive-ntfs</strong> entries for the same device will be kept
+if <strong>--replace</strong> is not used.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dadd"><strong>--add</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dremove"><strong>--remove</strong></a></strong></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.
+<p>Remove all lines of filesystem type <strong>captive-ntfs</strong> and device name in
+<strong>/dev</strong> directory.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dremove"><strong>--remove</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dreplace"><strong>--replace</strong></a></strong></dt>
+
<dd>
-Remove all lines of filesystem type <strong>captive-ntfs</strong> and device name in
-<strong>/dev</strong> directory.
+<p>Replace existing entries by new ones on <strong>--add</strong>. By default the existing
+<strong>captive-ntfs</strong> entries are kept untouched.</p>
</dd>
-<p></p></dl>
+</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><strong>captive-install-acquire</strong>(1), <strong>captive</strong>(7), <strong>mount.captive</strong>(8)</p>
<p>
</p>
<hr />
<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">
<!-- INDEX BEGIN -->
<ul>
-
<li><a href="#name">NAME</a></li>
<li><a href="#synopsis">SYNOPSIS</a></li>
<li><a href="#description">DESCRIPTION</a></li>
</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><strong>captive</strong>(7), <strong>captive-cmdline</strong>(1), <strong>mount.captive</strong>(8)</p>
<p>
</p>
<hr />
<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">
<!-- INDEX BEGIN -->
<ul>
-
<li><a href="#name">NAME</a></li>
<li><a href="#description">DESCRIPTION</a></li>
<li><a href="#options">OPTIONS</a></li>
<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>
+<dt><strong><a name="item__2d_2dfilesystem_3dpathname"><strong>--filesystem</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-Pathname to <strong>.sys</strong> or <strong>.so</strong> filesystem module file. You will use exactly
+<p>Pathname to <strong>.sys</strong> or <strong>.so</strong> filesystem module file. You will use exactly
once this option. Possible choices are
-<strong>/var/lib/captive/ntfs.sys</strong>
-etc.
+<strong>/usr/local/var/lib/captive/ntfs.sys</strong>
+etc.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dload%2dmodule%3dpathname"><strong>--load-module</strong>=<strong>pathname</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dload_2dmodule_3dpathname"><strong>--load-module</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-Pathname to any W32 module to load w/o initialization. Multiple modules can be
+<p>Pathname to any W32 module to load w/o initialization. Multiple modules can be
loaded although in common case you will use just
-<strong>/var/lib/captive/ntoskrnl.exe</strong>
-here.
+<strong>/usr/local/var/lib/captive/ntoskrnl.exe</strong>
+here.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dro"><strong>--ro</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dmodid_2dpath_3dpathname"><strong>--modid-path</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-Read/write mode: Any write access will be forbidden. You should set this mode
+<p>Pathname to the <strong>.captivemodid.xml</strong> database of existing W32 module
+identifications. The default used one is:
+<strong>/usr/local/etc/w32-mod-id.captivemodid.xml</strong>
+You must have this database update for any W32 binary module you are using.
+If you miss such database you may also try to use <strong>--load-untested</strong> below.</p>
+</dd>
+<dt><strong><a name="item__2d_2dload_2duntested"><strong>--load-untested</strong></a></strong></dt>
+
+<dd>
+<p>Load tthe W32 modules despite they may not match the current <strong>--modid-path</strong>
+identifications database. If you use this option Captive may fail very easily
+as such module was never tested before the release and may need some
+compatibility updates. Still no data should be corrupted even if using this
+<strong>--load-untested</strong> option.</p>
+</dd>
+<dt><strong><a name="item__2d_2dro"><strong>--ro</strong></a></strong></dt>
+
+<dd>
+<p>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>.
+<strong>--blind</strong> and <strong>--rw</strong>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dblind"><strong>--blind</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dblind"><strong>--blind</strong></a></strong></dt>
+
<dd>
-Read/write mode: All writes are just simulated in memory (default). Microsoft
+<p>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>.
+This option is mutually exclusive with <strong>--ro</strong> and <strong>--rw</strong>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2drw"><strong>--rw</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2drw"><strong>--rw</strong></a></strong></dt>
+
<dd>
-Read/write mode: Write directly to the image file/device. Standard read/write
+<p>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>.
+This option is mutually exclusive with <strong>--ro</strong> and <strong>--blind</strong>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dcdrom"><strong>--cdrom</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dcdrom"><strong>--cdrom</strong></a></strong></dt>
+
<dd>
-Media type: CD-ROM. You must set this media type for <strong>cdfs.sys</strong>.
+<p>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>.
+<strong>\Device\CdRom0</strong>. This option is mutually exclusive with <strong>--disk</strong>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2ddisk"><strong>--disk</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2ddisk"><strong>--disk</strong></a></strong></dt>
+
<dd>
-Media type: Disk (default). You must set this media type for all the Microsoft
+<p>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>.
+This option is mutually exclusive with <strong>--cdrom</strong>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2ddebug%2dmessages"><strong>--debug-messages</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2ddebug_2dmessages"><strong>--debug-messages</strong></a></strong></dt>
+
<dd>
-Turn on debugging messages. Be prepared for substation debug output.
-Use of <strong>--syslog</strong> feature is not recommended in this case.
+<p>Turn on debugging messages. Be prepared for substation debug output.
+Use of <strong>--syslog</strong> feature is not recommended in this case.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dsandbox%2dserver%3dpathname"><strong>--sandbox-server</strong>=<strong>pathname</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dsandbox_2dserver_3dpathname"><strong>--sandbox-server</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-Pathname to
-<strong>/usr/sbin/captive-sandbox-server</strong>
+<p>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
+to <strong>captive</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.
+option during debugging.</p>
</dd>
<dd>
<p>This option is turned on automatically during the mount operation by
<strong>mount.captive-ntfs</strong>(8).
Option needs to be used by hand for the <strong>captive-cmdline</strong>(2) client.</p>
</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>
+<dt><strong><a name="item__2d_2dsandbox_2dserver_2dior_3dior"><strong>--sandbox-server-ior</strong>=<strong>IOR</strong></a></strong></dt>
+
<dd>
-Specify <em>CORBA IOR</em> of
-<strong>/usr/sbin/captive-sandbox-server</strong>
+<p>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.
+possible in this case.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dno%2dsandbox"><strong>--no-sandbox</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dno_2dsandbox"><strong>--no-sandbox</strong></a></strong></dt>
+
<dd>
-Turn off sandboxing feature (default). No
-<strong>/usr/sbin/captive-sandbox-server</strong>
+<p>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.
+It is dangerous to use <strong>--rw</strong> together, see its description for the details.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dbug%2dpathname%3dpathname"><strong>--bug-pathname</strong>=<strong>pathname</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dbug_2dpathname_3dpathname"><strong>--bug-pathname</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-Pathname to <strong>strftime</strong>(3) for <strong>.captivebug.xml.gz</strong> bugreports. Every crash of
+<p>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>.
+required for <strong>--bug-pathname</strong>.</p>
</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>
+<dt><strong><a name="item__2d_2dsyslog"><strong>--syslog</strong></a></strong></dt>
+
<dd>
-Messages sent to <strong>syslog</strong>(3) instead of <em>stderr</em>. This option gets handy
+<p>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.
+filesystem driver crash.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2d%2dsyslog%2dfacility%3dfacility"><strong>--syslog-facility</strong>=<strong>facility</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dsyslog_2dfacility_3dfacility"><strong>--syslog-facility</strong>=<strong>facility</strong></a></strong></dt>
+
<dd>
-<strong>openlog</strong>(3) facility for <strong>--syslog</strong>. See <strong>facility</strong> section of
+<p><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.
+<strong>user</strong> are supported.</p>
</dd>
-<p></p></dl>
+</dl>
<p>
</p>
<hr />
+++ /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>channels</strong>} option of <strong>lufsd</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>/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>/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/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>
-<dd>
-<p>This option is turned on automatically during the mount operation by
-<strong>mount.captive-ntfs</strong>(8).
-Option needs to be used by hand for the <strong>captive-cmdline</strong>(2) client.</p>
-</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/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/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>lufsd</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>
<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">
<!-- INDEX BEGIN -->
<ul>
-
<li><a href="#name">NAME</a></li>
<li><a href="#synopsis">SYNOPSIS</a></li>
<li><a href="#description">DESCRIPTION</a></li>
</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>lufsd</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) provides <strong>mount</strong>(8) interface to <strong>captive</strong>(7) library
+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
<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>
+<dt><strong><a name="item__7bimage_2dfile_7cdevice_7d">{<strong>image-file</strong>|<strong>device</strong>}</a></strong></dt>
+
<dd>
-Pathname such as <strong>/dev/hda1</strong> or <strong>/tmp/ntfs.bin</strong>. You should refer to the
+<p>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.
+on your system.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_mountdir"><strong>mountdir</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item_mountdir"><strong>mountdir</strong></a></strong></dt>
+
<dd>
-Existing empty target directory where {<strong>image-file</strong>|<strong>device</strong>} will be
-mounted.
+<p>Existing empty target directory where {<strong>image-file</strong>|<strong>device</strong>} will be
+mounted.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2dn"><strong>-n</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2dn"><strong>-n</strong></a></strong></dt>
+
<dd>
-Do not modify <strong>/etc/mtab</strong>. This option is currently not supported (ignored),
-<strong>/etc/mtab</strong> is modified notwithstanding.
+<p>No effect. The standard functionality of 'do not modify <strong>/etc/mtab</strong>' is not
+supported - <strong>/etc/mtab</strong> is always modified.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2dv"><strong>-v</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2dv"><strong>-v</strong></a></strong></dt>
+
<dd>
-Enable verbose mode. Command <strong>lufsd</strong>(1) being called is shown.
+<p>No effect. The standard functionality of 'verbose mode' is not supported.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_%2do_options"><strong>-o</strong> <strong>options</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2do_options"><strong>-o</strong> <strong>options</strong></a></strong></dt>
+
<dd>
-Custom options passed to <strong>captive</strong>(7) separated by comma (<strong>,</strong>).
-See the <strong>captive</strong>(7) manpage for details on options prefixed by
-double-dashes (<strong>--</strong>) will be used for <strong>lufs-captivefs</strong>(7) /
-<strong>mount.captive</strong>(8). Options without double-dashes (<strong>--</strong>) will be used for
-<strong>lufsd</strong>(1). You may be interested in these unprefixed options:
+<p>Custom options passed to <strong>captive</strong>(7) separated by comma (<strong>,</strong>).</p>
+</dd>
+<dd>
+<p>Options without double-dashes (<strong>--</strong>) will be used for FUSE, please
+see their description in the section ``<strong>Mount options</strong>'' of your local
+<strong>/usr/share/doc/fuse/README</strong> or the online:
+<a href="http://cvs.sourceforge.net/viewcvs.py/fuse/fuse/README?rev=HEAD">http://cvs.sourceforge.net/viewcvs.py/fuse/fuse/README</a></p>
+</dd>
+<dd>
+<p>Options prefixed by double-dashes (<strong>--</strong>) are used for libcaptive, the
+options list:</p>
</dd>
<dl>
-<dt><strong><a name="item_force"><strong>force</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dfilesystem_3dpathname"><strong>--filesystem</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-Force the mount of {<strong>image-file</strong>|<strong>device</strong>} despite it appears to be already
-mounted according to <strong>mtab</strong>(5). You should never mount a device multiple
-times in read-write mode. It is safe to mount it multiple times in read-only
-mode. It is safe to mount it once in read-write mode and multiple times
-in read-only mode although you may encounter filesystem errors by the read-only
-filesystems in such case.
+<p>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.</p>
</dd>
+<dt><strong><a name="item__2d_2dload_2dmodule_3dpathname"><strong>--load-module</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-<p>This is the only option is interpreted by <strong>mount.captive</strong> itself; it is not
-<strong>lufs-captivefs</strong>(7) nor <strong>lufsd</strong>(1) option.</p>
+<p>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.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_private"><strong>private</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dmodid_2dpath_3dpathname"><strong>--modid-path</strong>=<strong>pathname</strong></a></strong></dt>
+
<dd>
-<strong>mount.captive</strong>(8) defaults to filesystem files <strong>644</strong> - read-write for system
-root (or the regular user owner) and read-only for others. You can force the
-mode <strong>600</strong> by this option (read-write for the owner, inaccessible for others).
-Mode <strong>755</strong> or <700> applies to directories. Options <strong>fmask</strong>/<strong>dmask</strong> will
-be OR-ed to the private/public permissions set by this option.
+<p>Pathname to the <strong>.captivemodid.xml</strong> database of existing W32 module
+identifications. The default used one is:
+<strong>/usr/local/etc/w32-mod-id.captivemodid.xml</strong>
+You must have this database update for any W32 binary module you are using.
+If you miss such database you may also try to use <strong>--load-untested</strong> below.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_fmask%3d666"><strong>fmask</strong>=<strong>666</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dload_2duntested"><strong>--load-untested</strong></a></strong></dt>
+
+<dd>
+<p>Load tthe W32 modules despite they may not match the current <strong>--modid-path</strong>
+identifications database. If you use this option Captive may fail very easily
+as such module was never tested before the release and may need some
+compatibility updates. Still no data should be corrupted even if using this
+<strong>--load-untested</strong> option.</p>
+</dd>
+<dt><strong><a name="item__2d_2dro"><strong>--ro</strong></a></strong></dt>
+
+<dd>
+<p>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>.</p>
+</dd>
+<dt><strong><a name="item__2d_2dblind"><strong>--blind</strong></a></strong></dt>
+
<dd>
-Octal mask to be OR-ed on file permissions (minimum file permissions).
+<p>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>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_dmask%3d777"><strong>dmask</strong>=<strong>777</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2drw"><strong>--rw</strong></a></strong></dt>
+
<dd>
-Octal mask to be OR-ed on directory permissions (minimum directory
-permissions).
+<p>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>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_uid%3d500"><strong>uid</strong>=<strong>500</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2dcdrom"><strong>--cdrom</strong></a></strong></dt>
+
<dd>
-Supply the <strong>UID</strong> to be the user identification number owning all the files.
+<p>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>.</p>
</dd>
-<p></p>
-<dt><strong><a name="item_gid%3d500"><strong>gid</strong>=<strong>500</strong></a></strong><br />
-</dt>
+<dt><strong><a name="item__2d_2ddisk"><strong>--disk</strong></a></strong></dt>
+
<dd>
-Supply the <strong>GID</strong> to be the group identification number owning all the files.
+<p>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>.</p>
</dd>
-<p></p></dl>
+<dt><strong><a name="item__2d_2ddebug_2dmessages"><strong>--debug-messages</strong></a></strong></dt>
+
+<dd>
+<p>Turn on debugging messages. Be prepared for substation debug output.
+Use of <strong>--syslog</strong> feature is not recommended in this case.</p>
+</dd>
+<dt><strong><a name="item__2d_2dsandbox_2dserver_3dpathname"><strong>--sandbox-server</strong>=<strong>pathname</strong></a></strong></dt>
+
+<dd>
+<p>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</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.</p>
+</dd>
+<dd>
+<p>This option is turned on automatically during the mount operation by
+<strong>mount.captive-ntfs</strong>(8).
+Option needs to be used by hand for the <strong>captive-cmdline</strong>(2) client.</p>
+</dd>
+<dt><strong><a name="item__2d_2dsandbox_2dserver_2dior_3dior"><strong>--sandbox-server-ior</strong>=<strong>IOR</strong></a></strong></dt>
+
+<dd>
+<p>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.</p>
+</dd>
+<dt><strong><a name="item__2d_2dno_2dsandbox"><strong>--no-sandbox</strong></a></strong></dt>
+
+<dd>
+<p>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.</p>
+</dd>
+<dt><strong><a name="item__2d_2dbug_2dpathname_3dpathname"><strong>--bug-pathname</strong>=<strong>pathname</strong></a></strong></dt>
+
+<dd>
+<p>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>.</p>
+</dd>
+<dd>
+<p><strong>!!! Be aware '.captivebug.xml.gz' will contain data from your disk drive !!!</strong></p>
+</dd>
+<dt><strong><a name="item__2d_2dsyslog"><strong>--syslog</strong></a></strong></dt>
+
+<dd>
+<p>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.</p>
+</dd>
+<dt><strong><a name="item__2d_2dsyslog_2dfacility_3dfacility"><strong>--syslog-facility</strong>=<strong>facility</strong></a></strong></dt>
+
+<dd>
+<p><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.</p>
+</dd>
+</dl>
</dl>
<p>
</p>
<hr />
<h1><a name="see_also">SEE ALSO</a></h1>
-<p><strong>lufs-captivefs</strong>(7), <strong>lufsd</strong>(1)</p>
+<p><strong>captive</strong>(7)</p>
<p>
</p>
<hr />
git://git.jankratochvil.net / www.jankratochvil.net.git / commitdiff