Document and Finish an iSCSI C Programming Project

This is a simple and fun project for an experienced C Programmer. The project is to improve, complete, possibly re-implement and document an existing C-language based iSCSI system known as stgt. It must be modified so that it will compile and run using a non-GNU C compiler. Additionally, we are considering having the code re-implemented so that it absolutely will not infringe on any copyrights that may exist. The code is currently under a modified BSD license. ## Deliverables I'm hoping to have this project complete in two weeks from bid acceptance. Please make sure you indicate how long you think it will take in your bid. We're trying to keep the costs down, so these first two components of this project are Optional. Please include these options in your bid if you're willing to do them: O1) Optionally completely re-implement the user-space software using the C language to ensure there are no licensing problems. This is a fairly complex software package and the license is something that we can live with, but we'd prefer it were re-implemented. O2) Change it to use xml files for configuration. Currently it uses a windows-like [Section] configuration scheme. Mandatory components of this project: M1) Ensure that it will build and execute properly in both a FreeBSD 8.0p4 environment and CentOS 5.5 environment on 32-bit i386 and 64-bit X86-64 machines; M2) You must use Clang and LLVM replacements for the GNU gcc C compiler. Clang is a mature product and is being used in the FreeBSD and Linux worlds. M3) Ensure extensive debugging exists throughout the code, and that it can be turned on at compile and run time for all code paths. This should be accomplished using macros in a debugging header file so that debug code is not included in the object files when it is disabled. Debugging must be able to be turned on and off for each subsystem. Debugging should use the syslog facility. M4) Document the entire system describing all of the configuration file options, run-time command-line options, their effects and any side-effects; M5) The GNU Linux software is available at [login to view URL] You must, however, use the FreeBSD port and patches, as it is under a non-restrictive BSD-type license or you must re-write the code so that there are no copyright restrictions. See [login to view URL]~rse/iscsi/[login to view URL] If you are not re-implementing the software, you must create a set of diffs against the current release that can be applied with patch using quilt ([login to view URL]) or similar diff/patch manager. 8) The iscsi initiator kernel drivers are not a part of this project so you don't have to work with them at all; 9) All iscsi target types must be implemented, including SBC, SMC, SSC and OSD. Currently SMC and SSC are partly functional and will need to be completed. See [login to view URL] for more details. 10) You must review any assumptions you would like to make about the software's behavior before you effect any changes or create new code. The primary operating system target for this system is FreeBSD, so the FreeBSD version must be completed before the Linux version. We can provide Internet access to one or more FreeBSD and CentOS systems dedicated for your use via OpenVPN for development/testing. Although you must thoroughly test this code yourself, we have personnel who can help perform testing and who will perform the final testing.