>> === Support version 2.0 development ===
"""" The next major version of FSproxy will feature:
~- **Significant performance improvement due to usage of hardware virtualization**
~- **Support for all major filesystems as well as LVM2 and software RAID partitions**
~- Running as priviledged Windows service (no more UAC nagging)
~- Better Windows integration including graphical status monitor
~- Safe read/write mode and fixed autostart option
~- Automatic updates
~- 100% open source code
=== Download version 1.0 ===
//Released 30th July 2009.//
Deletions:
>> === Download ===
//Latest release (30th July 2009).//
FSproxy is a small application that runs in the system tray and lets you access GNU/Linux partitions from within Microsoft Windows. The list of detected partitions is always availible at ##\\fsproxy## and a single one can easily be mapped to a network drive using address like ##\\fsproxy\##. By default partitions are mounted as read-only but experimental write support can be enabled. FSproxy currently supports: ''ext2'', ''ext3'', ''ext4'', ''reiserfs'', ''jfs'', ''xfs'' and few other filesystems. For many of them there is no known Windows driver available (although note that [[HowItWorks FSproxy is not a driver]] itself).
Deletions:
FSproxy is a small application that runs in the system tray and lets you access GNU/Linux partitions from within Microsoft Windows. The list of detected partitions is always availible at ##\\fsproxy## and a single one can easily be mapped to a netowrk drive using address like ##\\fsproxy\##. By default partitions are mounted as read-only but experimental write support can be enabled. FSproxy currently supports: ''ext2'', ''ext3'', ''ext4'', ''reiserfs'', ''jfs'', ''xfs'' and few other filesystems. For many of them there is no known Windows driver availible (although note that [[HowItWorks FSproxy is not a driver]] itself).
FSproxy is a small application that runs in the system tray and lets you access GNU/Linux partitions from within Microsoft Windows. The list of detected partitions is always availible at ##\\fsproxy## and a single one can easily be mapped to a netowrk drive using address like ##\\fsproxy\##. By default partitions are mounted as read-only but experimental write support can be enabled. FSproxy currently supports: ''ext2'', ''ext3'', ''ext4'', ''reiserfs'', ''jfs'', ''xfs'' and few other filesystems. For many of them there is no known Windows driver availible (although note that [[HowItWorks FSproxy is not a driver]] itself).
Deletions:
FSproxy is a small application that runs in the system's tray and lets you access your GNU/Linux partitions from within Microsoft Windows. Filesystem of a partition mounted by FSproxy can be accessed by mapping ''\\fsproxy\\'' as a network drive. List of detected partitions is available at ''\\fsproxy''. Partitions are by default mounted read-only, but experimental write support can be enabled. FSproxy supports: ''ext2'', ''ext3'', ''ext4'', ''reiserfs'', ''jfs'', ''xfs'' and few other filesystems. For many of them no known Windows driver exists (although note that [[HowItWorks FSproxy is not a driver]] itself).
FSproxy is a small application that runs in the system's tray and lets you access your GNU/Linux partitions from within Microsoft Windows. Filesystem of a partition mounted by FSproxy can be accessed by mapping ''\\fsproxy\\'' as a network drive. List of detected partitions is available at ''\\fsproxy''. Partitions are by default mounted read-only, but experimental write support can be enabled. FSproxy supports: ''ext2'', ''ext3'', ''ext4'', ''reiserfs'', ''jfs'', ''xfs'' and few other filesystems. For many of them no known Windows driver exists (although note that [[HowItWorks FSproxy is not a driver]] itself).
Deletions:
FSproxy is a small application that runs in system's tray and lets you access your GNU/Linux partitions from within Microsoft Windows. Filesystem of a partition mounted by FSproxy can be accessed by mapping ''\\fsproxy\\'' as a network drive. List of detected partitions is available at ''\\fsproxy''. Partitions are by default mounted read-only, but experimental write support can be enabled. FSproxy supports: ''ext2'', ''ext3'', ''ext4'', ''reiserfs'', ''jfs'', ''xfs'' and few other filesystems. For many of them no known Windows driver exists (although note that [[HowItWorks FSproxy is not a driver]] itself).
FSproxy is a small application that runs in system's tray and lets you access your GNU/Linux partitions from within Microsoft Windows. Filesystem of a partition mounted by FSproxy can be accessed by mapping ''\\fsproxy\\'' as a network drive. List of detected partitions is available at ''\\fsproxy''. Partitions are by default mounted read-only, but experimental write support can be enabled. FSproxy supports: ''ext2'', ''ext3'', ''ext4'', ''reiserfs'', ''jfs'', ''xfs'' and few other filesystems. For many of them no known Windows driver exists (although note that [[HowItWorks FSproxy is not a driver]] itself).
~- [[Disclaimer Disclaimer]]: Read before installing.
Deletions:
FSproxy is a small application that runs in system's tray and lets you access your GNU/Linux partitions from within Microsoft Windows. Filesystem of a partition mounted by FSproxy can be accessed by mapping ''\\fsproxy\\'' as a network drive. List of detected partitions is available at ''\\fsproxy''. Partitions are by default mounted read-only, but experimental write support can be enabled. FSproxy supports: ''ext2'', ''ext3'', ''ext4'', ''reiserfs'', ''jfs'', ''xfs'' and few other filesystems. For many of them no known Windows driver exists (although note that FSproxy is not a driver itself).
=== Documentation ===
~- [[Tutorial Using FSproxy]]: How to install and configure FSproxy.
~- [[Troubleshooting Troubleshooting guide]]
~- [[HowItWorks How it works under the hood]]
Deletions:
=== How to use it ===
For usage howto refer to [[Tutorial this tutorial]]. Keep in mind that you must have __administrative privileges__ on the system.
=== How it works ===
Well to be honest it's quite a hack. :) And not an elegant one, but it works. The whole thing consists of two main parts: FSproxy Agent and Server. The first one, agent, is a small application written entirely in C using ""Win32"" API. It's main function is to present the user a nice GUI with simple configuration dialog and monitor/control the server process. It feeds the server data about what hard drives to use, virtual network interface configuration (about which later) and so on. It can also send various control commands to the server and start/stop it's process.
The server is a background QEMU process which runs a minimal GNU/Linux system. Emulated hardware consists of an i386 CPU with 16MB of RAM, no graphics card and an Intel PRO/1000 network adapter. Operating system is contained within 18MB disk image mounted read-only. When the server (QEMU process) is started by FSproxy Agent, the operating system running in a virtual machine detects types of partitions on physical hard drives attached to QEMU, loads appropriate kernel modules an mounts them. Then it starts a Samba server with each mount point being exported as a share. Minimal HTTP server is also started to handle control commands sent by agent and to report status. QEMU process uses a virtual TAP network adapter to provide connectivity with Windows. At this point one can access server's samba shares at ''\\fsproxy'' and map them as network drives. When the server is stopped or restarted by FSproxy Agent all partitions are unmounted/remounted read-only and QEMU process terminates.
Well to be honest it's quite a hack. :) And not an elegant one, but it works. The whole thing consists of two main parts: FSproxy Agent and Server. The first one, agent, is a small application written entirely in C using ""Win32"" API. It's main function is to present the user a nice GUI with simple configuration dialog and monitor/control the server process. It feeds the server data about what hard drives to use, virtual network interface configuration (about which later) and so on. It can also send various control commands to the server and start/stop it's process.
Deletions:
Well to be honest it's quite a hack. :) And not an elegant one, but it works. The whole thing consists of two main parts: FSproxy Agent and Server. The first one, agent, is a small application written entirely in C using Win32 API. It's main function is to present the user a nice GUI with simple configuration dialog and monitor/control the server process. It feeds the server data about what hard drives to use, virtual network interface configuration (about which later) and so on. It can also send various control commands to the server and start/stop it's process.