From: lace <>
Date: Thu, 29 Dec 2005 06:12:43 +0000 (+0000)
Subject: Captive release update: 1.1.6.1
X-Git-Url: http://git.jankratochvil.net/?p=www.jankratochvil.net.git;a=commitdiff_plain;h=749a32af91f56c9d3fc710e2eaa891aa01f27c4e;hp=57c6ee027fb80f9974764003f0e6d13ddcd745d7
Captive release update: 1.1.6.1
---
diff --git a/project/captive/DriverSurvey.js b/project/captive/DriverSurvey.js
new file mode 100644
index 0000000..21f1df0
--- /dev/null
+++ b/project/captive/DriverSurvey.js
@@ -0,0 +1,112 @@
+/* $Id$
+ * Captive MS-Windows Driver Survey helper.
+ * Copyright (C) 2005 Jan Kratochvil 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
+(ntoskrnl.exe) would not even be needed in such case. $error Direct e-mail address: @{[ a_href 'mailto:driversurvey@jankratochvil.net' ]} 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
@@ -76,15 +73,35 @@ my $W=project::Lib->init(
.' RPM i386 binary .tar.gz i386 binary 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. 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. 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. @{[ a_href 'DriverSurvey.pm','Linux Drivers Availability survey' ]} link
+- if you already answered before.Linux Drivers Availability
+HERE
+
+if (!$error) {
+ print <<"HERE";
+• '.a_href('#seealso','See Also').' '
.''
},
+ "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";
Download
@@ -96,67 +113,47 @@ print <<"HERE";
-
tested for distributions:
-
@{[ a_href 'dist/captive-static-'.$version{"captive"}[0].'-'.$version{"captive"}[1].'.i386.rpm',
- undef(),"size"=>1,"basename"=>1 ]}
+ @{[ download("captive-static-$version-$revision.i386.rpm") ]}
-
(for non-RPM distributions)@{[ a_href 'dist/captive-static-'.$version{"captive"}[0].'.tar.gz',undef(),"size"=>1,"basename"=>1 ]}
+ @{[ download("captive-static-$version.tar.gz") ]}
+HERE
-Source archives
@{[ a_href 'CVS.pm#source','download link' ]}
Development Status
-
-Known Issue
-
-NEWS
-
@{[ vskip "3ex" ]}
@@ -216,50 +213,30 @@ problems.
-
/dev/ataraid
devices (Ivan Tonov)
-# 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.
-(Backslash end-of-line characters '\\' to be omitted for line continuation.)
++ # mkdir /mnt/dosc
+ # mount -t captive-ntfs /dev/hda1 /mnt/dosc +
Any errors from 'captive-lufs' are written to '/var/log/messages'.
+Any errors from 'captive-fuse' are written to '/var/log/messages'.
Needed drivers (at least ntoskrnl.exe+ntfs.sys) must be in '/var/lib/captive'.
'captive' package creates 'captive' user and 'captive' group on your system.
-@{[ a_href 'http://lufs.sourceforge.net/lufs/','LUFS' ]} (Linux Userland File -System) needs Linux kernel module driver (lufs.o) compatible with your -running Linux kernel. The binary driver is supplied already precompiled for many -Linux kernel versions in the binary packages above (.i386.rpm and -_i386.deb archives).
+If you cannot mount(8) your NTFS filesystem you should run /usr/share/lufs/prepmod 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 -kernel-source (Red Hat) or kernel-headers (Debian) matching your -Linux kernel version (rpm -q kernel) and re-run /usr/share/lufs/prepmod.
+@{[ a_href 'http://fuse.sourceforge.net/','FUSE' ]} (Filesystem in Userspace) +needs Linux kernel module driver (fuse.ko) compatible with your +running Linux kernel.
-WARNING: 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 /usr/share/lufs/prepmod 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' ]}.
+If you cannot mount(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.
HERE @@ -337,7 +314,6 @@ print <<"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'], diff --git a/project/captive/Lib.css b/project/captive/Lib.css index e213507..1e6c4e4 100644 --- a/project/captive/Lib.css +++ b/project/captive/Lib.css @@ -18,3 +18,5 @@ .name { font-style: italic; } +table.padded > tr > td { padding: 15px; } +table.vtop > tr > td { vertical-align: top; } diff --git a/project/captive/Makefile.am b/project/captive/Makefile.am index 85df28c..f292e20 100644 --- a/project/captive/Makefile.am +++ b/project/captive/Makefile.am @@ -28,5 +28,9 @@ MODPERL_PM+= \ Preview.pm \ CVS.pm \ Press.pm \ - TestimonialBrunoSantos.pm + TestimonialBrunoSantos.pm \ + DriverSurvey.pm + +EXTRA_DIST+= \ + DriverSurvey.js diff --git a/project/captive/dist/build-captive-static-2003-12-14-00.tar.gz b/project/captive/dist/build-captive-static-2003-12-14-00.tar.gz deleted file mode 100644 index 0497c51..0000000 Binary files a/project/captive/dist/build-captive-static-2003-12-14-00.tar.gz and /dev/null differ diff --git a/project/captive/dist/captive-1.1.5.tar.gz b/project/captive/dist/captive-1.1.5.tar.gz deleted file mode 100644 index 5b9d148..0000000 Binary files a/project/captive/dist/captive-1.1.5.tar.gz and /dev/null differ diff --git a/project/captive/dist/captive-1.1.6.1.tar.gz b/project/captive/dist/captive-1.1.6.1.tar.gz new file mode 100644 index 0000000..962285c Binary files /dev/null and b/project/captive/dist/captive-1.1.6.1.tar.gz differ diff --git a/project/captive/dist/captive-install_1.1.5_i386.deb b/project/captive/dist/captive-install_1.1.5_i386.deb deleted file mode 100644 index ecbb8de..0000000 Binary files a/project/captive/dist/captive-install_1.1.5_i386.deb and /dev/null differ diff --git a/project/captive/dist/captive-lufs_1.1.5_i386.deb b/project/captive/dist/captive-lufs_1.1.5_i386.deb deleted file mode 100644 index 26740f8..0000000 Binary files a/project/captive/dist/captive-lufs_1.1.5_i386.deb and /dev/null differ diff --git a/project/captive/dist/captive-static-1.1.5.tar.gz b/project/captive/dist/captive-static-1.1.5.tar.gz deleted file mode 100644 index 054d376..0000000 Binary files a/project/captive/dist/captive-static-1.1.5.tar.gz and /dev/null differ diff --git a/project/captive/dist/captive-static-1.1.6.1-0.i386.rpm b/project/captive/dist/captive-static-1.1.6.1-0.i386.rpm new file mode 100644 index 0000000..e2fe418 Binary files /dev/null and b/project/captive/dist/captive-static-1.1.6.1-0.i386.rpm differ diff --git a/project/captive/dist/captive-static-1.1.5-0.i386.rpm b/project/captive/dist/captive-static-1.1.6.1.tar.gz similarity index 55% rename from project/captive/dist/captive-static-1.1.5-0.i386.rpm rename to project/captive/dist/captive-static-1.1.6.1.tar.gz index 6320f79..ae5ec37 100644 Binary files a/project/captive/dist/captive-static-1.1.5-0.i386.rpm and b/project/captive/dist/captive-static-1.1.6.1.tar.gz differ diff --git a/project/captive/dist/captive_1.1.5_i386.deb b/project/captive/dist/captive_1.1.5_i386.deb deleted file mode 100644 index 723c0d6..0000000 Binary files a/project/captive/dist/captive_1.1.5_i386.deb and /dev/null differ diff --git a/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2-0.i386.rpm b/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2-0.i386.rpm deleted file mode 100644 index bad3365..0000000 Binary files a/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2-0.i386.rpm and /dev/null differ diff --git a/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2-0.src.rpm b/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2-0.src.rpm deleted file mode 100644 index b53e440..0000000 Binary files a/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2-0.src.rpm and /dev/null differ diff --git a/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2-0mdk91.i586.rpm b/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2-0mdk91.i586.rpm deleted file mode 100644 index 180a873..0000000 Binary files a/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2-0mdk91.i586.rpm and /dev/null differ diff --git a/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2-0rh8.i386.rpm b/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2-0rh8.i386.rpm deleted file mode 100644 index 995f6e0..0000000 Binary files a/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2-0rh8.i386.rpm and /dev/null differ diff --git a/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2.tar.gz b/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2.tar.gz deleted file mode 100644 index 848a25f..0000000 Binary files a/project/captive/dist/gnome-vfs-httpcaptive-2.3.8captive2.tar.gz and /dev/null differ diff --git a/project/captive/dist/gnome-vfs-httpcaptive-debuginfo-2.3.8captive2-0.i386.rpm b/project/captive/dist/gnome-vfs-httpcaptive-debuginfo-2.3.8captive2-0.i386.rpm deleted file mode 100644 index 2ed799b..0000000 Binary files a/project/captive/dist/gnome-vfs-httpcaptive-debuginfo-2.3.8captive2-0.i386.rpm and /dev/null differ diff --git a/project/captive/dist/gnome-vfs-httpcaptive_2.3.8captive2.dsc b/project/captive/dist/gnome-vfs-httpcaptive_2.3.8captive2.dsc deleted file mode 100644 index 404c5fd..0000000 --- a/project/captive/dist/gnome-vfs-httpcaptive_2.3.8captive2.dsc +++ /dev/null @@ -1,21 +0,0 @@ ------BEGIN PGP SIGNED MESSAGE----- -Hash: SHA1 - -Format: 1.0 -Source: gnome-vfs-httpcaptive -Version: 2.3.8captive2 -Binary: gnome-vfs-httpcaptive -Maintainer: Jan KratochvilSimple ftp(1)-like client to access disks by Microsoft Windows drivers. -Use if lufs-captivefs(7) not available; also useful during debugging.
+Use if mount.captive(8) not available; also useful during debugging.
All programs using captive(7) library share the common set of configuration options:
Pathname to .sys or .so filesystem module file. You will use exactly once this option. Possible choices are -/var/lib/captive/ntfs.sys -etc. +/usr/local/var/lib/captive/ntfs.sys +etc.
Pathname to any W32 module to load w/o initialization. Multiple modules can be loaded although in common case you will use just -/var/lib/captive/ntoskrnl.exe -here. +/usr/local/var/lib/captive/ntoskrnl.exe +here.
Pathname to the .captivemodid.xml database of existing W32 module +identifications. The default used one is: +/usr/local/etc/w32-mod-id.captivemodid.xml +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 --load-untested below.
+Load tthe W32 modules despite they may not match the current --modid-path +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 +--load-untested option.
+Read/write mode: Any write access will be forbidden. You should set this mode for cdfs.sys (CD-ROM filesystem). This option is mutually exclusive with ---blind and --rw. +--blind and --rw.
Read/write mode: All writes are just simulated in memory (default). Microsoft Windows filesystem driver will see no difference between --blind and --rw although the UNIX image file/device will be open read/only as for --ro. All the changes get 'written' as long as captive(7) program runs - all the changes will be lost afterwards. This mode is the most suitable for debugging. -This option is mutually exclusive with --ro and --rw. +This option is mutually exclusive with --ro and --rw.
Read/write mode: Write directly to the image file/device. Standard read/write disk mode. You should use --sandbox-server option in this case to have the disk protected against Microsoft Windows filesystem driver crashes. Modified disk image blocks are in --sandbox-server --rw 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 --ro and --blind. +This option is mutually exclusive with --ro and --blind.
Media type: CD-ROM. You must set this media type for cdfs.sys. Virtual Microsoft Windows block device driver used by Captive maps to -\Device\CdRom0. This option is mutually exclusive with --disk. +\Device\CdRom0. This option is mutually exclusive with --disk.
Media type: Disk (default). You must set this media type for all the Microsoft Windows filesystem drivers except cdfs.sys. Virtual Microsoft Windows block device driver used by Captive maps to \Device\CaptiveHarddisk0. -This option is mutually exclusive with --cdrom. +This option is mutually exclusive with --cdrom.
Turn on debugging messages. Be prepared for substation debug output. +Use of --syslog feature is not recommended in this case.
Pathname to +/usr/local/sbin/captive-sandbox-server program, turns on sandboxing. You should always use this option in conjunction with --rw, see it for details. Although this program is setuid root and it drops it privileges -to @CAPTIVE_SANDBOX_SETUID@ user. Your system gets protected by +to captive user. Your system gets protected by chroot(2), setuid(2), setgid(2) and setrlimit(2) UNIX security features against malicious Microsoft Windows drivers. You should never use this -option during debugging. +option during debugging.
This option is turned on automatically during the mount operation by mount.captive-ntfs(8). Option needs to be used by hand for the captive-cmdline(2) client.
Specify CORBA IOR of +/usr/local/sbin/captive-sandbox-server program, turns on sandboxing. Specified CORBA IOR should be the string starting by ``IOR:'' text. This option is useful only for debugging. No sandbox restarting is -possible in this case. +possible in this case.
Turn off sandboxing feature (default). No +/usr/local/sbin/captive-sandbox-server is run. Microsoft Windows filesystem driver is run in native UNIX environment without any CORBA separation. This option is recommended only for debugging. -It is dangerous to use --rw together, see its description for the details. +It is dangerous to use --rw together, see its description for the details.
Pathname to strftime(3) for .captivebug.xml.gz 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. --sandbox-server option is -required for --bug-pathname. +required for --bug-pathname.
!!! Be aware '.captivebug.xml.gz' will contain data from your disk drive !!!
Messages sent to syslog(3) instead of stderr. This option gets handy for mount(8) operation as the messages would be lost otherway. Watch our for possible ``Filesystem crash broke dirty object'' messages where some written filesystem data got lost in the case of Microsoft Windows -filesystem driver crash. +filesystem driver crash.
openlog(3) facility for --syslog. See facility section of openlog(3) man page for details. Lowercased values such as daemon or -user are supported. +user are supported.
captive(7), lufs-captivefs(7)
+captive(7), mount.captive(8)
Program acquires the needed Microsoft Windows XP driver files. Multiple methods of getting the driver files are supported. All the driver files are stored to the directory -/var/lib/captive/ +/usr/local/var/lib/captive/ where they are expected by mount.captive(8).
@@ -48,93 +46,86 @@ expected by mount.captive(8).
--scan-disks-quick, --scan-path or --microsoft-com) are specified. Otherwise the requestedaction(s)
is proceeded in silent batch mode.
Disable Gnome user interface even if X Window System 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).
Display additional information during disks scanning.
Perform all the operations but do not modify anything (no drivers are stored to -/var/lib/captive/ -directory). +/usr/local/var/lib/captive/ +directory).
Path to .captivemodid.xml database (default: +/usr/local/etc/w32-mod-id.captivemodid.xml). This file contains identifications (md5sum(1)) of known compatible Microsoft Windows XP driver files. captive-install-acquire(1) will ignore any files not identified by this file although you may try to copy them to -/var/lib/captive/ -manually for captive(7) clients. +/usr/local/var/lib/captive/ +manually for captive(7) clients.
Scan all files on any local hard drive (mounted or unmounted) NTFS or (mounted) FAT partitions. This scanning includes cabinet (.cab) -archives. This scanning can last for very long time. +archives. This scanning can last for very long time.
Reduced version of --scan-disks. Only windows/system32 subdirectory in the root of any local hard drive (mounted or unmounted) NTFS or (mounted) FAT partition is investigated. This scan should find existing driver files -in already existing Microsoft Windows XP installations. +in already existing Microsoft Windows XP installations.
Scan the specified path/URI for device driver files. You may use either filename (/tmp/ntoskrnl.ex_), directory (/tmp/servicepack.cab), NTFS disk file/directory (file:///dev/hda1#libntfs:/windows/system32) or remote URI filename (http://server/path/to/ntfs.sys). Remote URI directory -(such as http://server/subdir/) is not supported. +(such as http://server/subdir/) is not supported.
Possibly specified directory is always scanned recursively.
You can download the best available version of needed drivers from +Microsoft. They can be found in Microsoft Windows XP Service Pack 2 Checked Build (URL -http://www.microsoft.com/WindowsXP/pro/downloads/servicepacks/sp1/checkedbuild.asp) +http://msdn.microsoft.com/security/productinfo/xpsp2)
Legal: In some countries you need to have valid Microsoft Windows XP license to use it.
Program will need to download approx 29MB of data (the cabinet file is 151MB; +
Program will need to download approx 61MB of data (the cabinet file is 307MB; 1MB=1e6B here).
captive-install-fstab(1), captive(7), lufs-captivefs(7)
+captive-install-fstab(1), captive(7), mount.captive(8)
Display additional information during disks scanning.
+Perform all the operations but do not modify anything (file /etc/fstab). +You will probably use this option together with [-v|--verbose].
Add all the found NTFS disk drive partitions to /etc/fstab. +Previous captive-ntfs entries for the same device will be kept +if --replace is not used.
Remove all lines of filesystem type captive-ntfs and device name in +/dev directory.
Replace existing entries by new ones on --add. By default the existing +captive-ntfs entries are kept untouched.
captive-install-acquire(1), captive(7), lufs-captivefs(7)
+captive-install-acquire(1), captive(7), mount.captive(8)
captive(7), captive-cmdline(1), lufs-captivefs(7)
+captive(7), captive-cmdline(1), mount.captive(8)
All programs using captive(7) library share the common set of configuration options:
Pathname to .sys or .so filesystem module file. You will use exactly once this option. Possible choices are -/var/lib/captive/ntfs.sys -etc. +/usr/local/var/lib/captive/ntfs.sys +etc.
Pathname to any W32 module to load w/o initialization. Multiple modules can be loaded although in common case you will use just -/var/lib/captive/ntoskrnl.exe -here. +/usr/local/var/lib/captive/ntoskrnl.exe +here.
Pathname to the .captivemodid.xml database of existing W32 module +identifications. The default used one is: +/usr/local/etc/w32-mod-id.captivemodid.xml +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 --load-untested below.
+Load tthe W32 modules despite they may not match the current --modid-path +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 +--load-untested option.
+Read/write mode: Any write access will be forbidden. You should set this mode for cdfs.sys (CD-ROM filesystem). This option is mutually exclusive with ---blind and --rw. +--blind and --rw.
Read/write mode: All writes are just simulated in memory (default). Microsoft Windows filesystem driver will see no difference between --blind and --rw although the UNIX image file/device will be open read/only as for --ro. All the changes get 'written' as long as captive(7) program runs - all the changes will be lost afterwards. This mode is the most suitable for debugging. -This option is mutually exclusive with --ro and --rw. +This option is mutually exclusive with --ro and --rw.
Read/write mode: Write directly to the image file/device. Standard read/write disk mode. You should use --sandbox-server option in this case to have the disk protected against Microsoft Windows filesystem driver crashes. Modified disk image blocks are in --sandbox-server --rw 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 --ro and --blind. +This option is mutually exclusive with --ro and --blind.
Media type: CD-ROM. You must set this media type for cdfs.sys. Virtual Microsoft Windows block device driver used by Captive maps to -\Device\CdRom0. This option is mutually exclusive with --disk. +\Device\CdRom0. This option is mutually exclusive with --disk.
Media type: Disk (default). You must set this media type for all the Microsoft Windows filesystem drivers except cdfs.sys. Virtual Microsoft Windows block device driver used by Captive maps to \Device\CaptiveHarddisk0. -This option is mutually exclusive with --cdrom. +This option is mutually exclusive with --cdrom.
Turn on debugging messages. Be prepared for substation debug output. +Use of --syslog feature is not recommended in this case.
Pathname to +/usr/local/sbin/captive-sandbox-server program, turns on sandboxing. You should always use this option in conjunction with --rw, see it for details. Although this program is setuid root and it drops it privileges -to @CAPTIVE_SANDBOX_SETUID@ user. Your system gets protected by +to captive user. Your system gets protected by chroot(2), setuid(2), setgid(2) and setrlimit(2) UNIX security features against malicious Microsoft Windows drivers. You should never use this -option during debugging. +option during debugging.
This option is turned on automatically during the mount operation by mount.captive-ntfs(8). Option needs to be used by hand for the captive-cmdline(2) client.
Specify CORBA IOR of +/usr/local/sbin/captive-sandbox-server program, turns on sandboxing. Specified CORBA IOR should be the string starting by ``IOR:'' text. This option is useful only for debugging. No sandbox restarting is -possible in this case. +possible in this case.
Turn off sandboxing feature (default). No +/usr/local/sbin/captive-sandbox-server is run. Microsoft Windows filesystem driver is run in native UNIX environment without any CORBA separation. This option is recommended only for debugging. -It is dangerous to use --rw together, see its description for the details. +It is dangerous to use --rw together, see its description for the details.
Pathname to strftime(3) for .captivebug.xml.gz 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. --sandbox-server option is -required for --bug-pathname. +required for --bug-pathname.
!!! Be aware '.captivebug.xml.gz' will contain data from your disk drive !!!
Messages sent to syslog(3) instead of stderr. This option gets handy for mount(8) operation as the messages would be lost otherway. Watch our for possible ``Filesystem crash broke dirty object'' messages where some written filesystem data got lost in the case of Microsoft Windows -filesystem driver crash. +filesystem driver crash.
openlog(3) facility for --syslog. See facility section of openlog(3) man page for details. Lowercased values such as daemon or -user are supported. +user are supported.
-
-lufs-captivefs - Linux Userland File System module for NTFS as filesystem
--
-lufs-captivefs(7) module for Linux Userland File System (LUFS) enables -GNU/Linux system to access NTFS drives by Microsoft Windows drivers in -the most common way of kernel-level filesystem implementation.
-{channels} option of lufsd(1) is respected -although the final filesystem operations are always processed in single-channel -mode. Do not set CHAN to 1 as it would invoke errors by LUFS kernel -driver.
--
-All programs using captive(7) library share the common set of configuration -options:
-This option is turned on automatically during the mount operation by -mount.captive-ntfs(8). -Option needs to be used by hand for the captive-cmdline(2) client.
-!!! Be aware '.captivebug.xml.gz' will contain data from your disk drive !!!
--
-mount.captive(8), lufsd(1), captive(7)
--
-Jan Kratochvil <project-captive@jankratochvil.net>, - | |
http://www.jankratochvil.net/ |
mount.captive(8) provides mount(8) interface to lufs-captivefs(7) -by calling lufsd(1) with appropriate arguments. You should never call -this command directly - use mount(8) instead.
+mount.captive(8) provides mount(8) interface to captive(7) library +You should never call this command directly - use mount(8) instead.
mount.captive(8) (captive filesystem type) is never used - this command
is provided just as a base mount(8)
interface to captive(7). You must always
use captive-fstype filesystem type such as captive-ntfs. Other supported
@@ -52,101 +49,202 @@ filesystem types are:
Pathname such as /dev/hda1 or /tmp/ntfs.bin. You should refer to the partition name, not the whole device (/dev/hda is forbidden). /dev/hda1 may correspond to /dev/ide/host0/bus0/target0/lun0/part1 -on your system. +on your system.
Existing empty target directory where {image-file|device} will be +mounted.
No effect. The standard functionality of 'do not modify /etc/mtab' is not +supported - /etc/mtab is always modified.
No effect. The standard functionality of 'verbose mode' is not supported.
Custom options passed to captive(7) separated by comma (,).
+Options without double-dashes (--) will be used for FUSE, please +see their description in the section ``Mount options'' of your local +/usr/share/doc/fuse/README or the online: +http://cvs.sourceforge.net/viewcvs.py/fuse/fuse/README
+Options prefixed by double-dashes (--) are used for libcaptive, the +options list:
Pathname to .sys or .so filesystem module file. You will use exactly +once this option. Possible choices are +/usr/local/var/lib/captive/ntfs.sys +etc.
This is the only option is interpreted by mount.captive itself; it is not -lufs-captivefs(7) nor lufsd(1) option.
+Pathname to any W32 module to load w/o initialization. Multiple modules can be +loaded although in common case you will use just +/usr/local/var/lib/captive/ntoskrnl.exe +here.
Pathname to the .captivemodid.xml database of existing W32 module +identifications. The default used one is: +/usr/local/etc/w32-mod-id.captivemodid.xml +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 --load-untested below.
Load tthe W32 modules despite they may not match the current --modid-path +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 +--load-untested option.
+Read/write mode: Any write access will be forbidden. You should set this mode +for cdfs.sys (CD-ROM filesystem). This option is mutually exclusive with +--blind and --rw.
+Read/write mode: All writes are just simulated in memory (default). Microsoft +Windows filesystem driver will see no difference between --blind and --rw +although the UNIX image file/device will be open read/only as for --ro. +All the changes get 'written' as long as captive(7) program runs - all the +changes will be lost afterwards. This mode is the most suitable for debugging. +This option is mutually exclusive with --ro and --rw.
Read/write mode: Write directly to the image file/device. Standard read/write +disk mode. You should use --sandbox-server option in this case to have the +disk protected against Microsoft Windows filesystem driver crashes. Modified +disk image blocks are in --sandbox-server --rw 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 --ro and --blind.
Media type: CD-ROM. You must set this media type for cdfs.sys. +Virtual Microsoft Windows block device driver used by Captive maps to +\Device\CdRom0. This option is mutually exclusive with --disk.
Media type: Disk (default). You must set this media type for all the Microsoft +Windows filesystem drivers except cdfs.sys. Virtual Microsoft Windows block +device driver used by Captive maps to \Device\CaptiveHarddisk0. +This option is mutually exclusive with --cdrom.
Turn on debugging messages. Be prepared for substation debug output. +Use of --syslog feature is not recommended in this case.
+Pathname to +/usr/local/sbin/captive-sandbox-server +program, turns on sandboxing. +You should always use this option in conjunction with --rw, see it for +details. Although this program is setuid root and it drops it privileges +to captive user. Your system gets protected by +chroot(2), setuid(2), setgid(2) and setrlimit(2) UNIX security +features against malicious Microsoft Windows drivers. You should never use this +option during debugging.
+This option is turned on automatically during the mount operation by +mount.captive-ntfs(8). +Option needs to be used by hand for the captive-cmdline(2) client.
+Specify CORBA IOR of +/usr/local/sbin/captive-sandbox-server +program, turns on +sandboxing. Specified CORBA IOR should be the string starting by ``IOR:'' +text. This option is useful only for debugging. No sandbox restarting is +possible in this case.
+Turn off sandboxing feature (default). No +/usr/local/sbin/captive-sandbox-server +is run. Microsoft Windows filesystem driver is run in native UNIX environment +without any CORBA separation. This option is recommended only for debugging. +It is dangerous to use --rw together, see its description for the details.
+Pathname to strftime(3) for .captivebug.xml.gz 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. --sandbox-server option is +required for --bug-pathname.
+!!! Be aware '.captivebug.xml.gz' will contain data from your disk drive !!!
+Messages sent to syslog(3) instead of stderr. This option gets handy +for mount(8) operation as the messages would be lost otherway. +Watch our for possible ``Filesystem crash broke dirty object'' messages where +some written filesystem data got lost in the case of Microsoft Windows +filesystem driver crash.
+openlog(3) facility for --syslog. See facility section of +openlog(3) man page for details. Lowercased values such as daemon or +user are supported.
+
lufs-captivefs(7), lufsd(1)
+captive(7)