Docs updated

git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@2136 d57e44dd-8a1f-0410-8b47-8ef2f437770f

iscsi-scst/README

@@ -116,6 +116,16 @@ See HOWTOs in the doc/ subdirectory.
 In 2.0.0 usage of iscsi-scstd.conf as well as iscsi-scst-adm utility is
 obsolete. Use the sysfs interface facilities instead.
 
+The flow of iSCSI-SCST inialization should be as the following:
+
+1. Load of SCST and iSCSI-SCST kernel modules with necessary module
+parameters, if needed.
+
+2. Start iSCSI-SCST service.
+
+3. Configure targets, devices, LUNs, etc. either using scstadmin
+(recommended), or using the sysfs interface directly as described below.
+
 It is recommended to use TEST UNIT READY ("tur") command to check if
 iSCSI-SCST target is alive in MPIO configurations.
 
@@ -143,11 +153,18 @@ configuration to the sysfs interface:
 5. Check new_config_file and make sure it has everything written
 properly.
 
-6. Delete /etc/iscsi-scst.conf and forget about it.
+6. IMPORTANT! Delete /etc/iscsi-scst.conf and forget about it.
 
 7. Start using "scstadmin -config new_config_file" to configure both
 SCST and iSCSI-SCST.
 
+IMPORTANT: With the sysfs interface the flow of iSCSI-SCST initialization
+=========  has changed (see above). Now scstadmin should be run as the FINAL
+	   step of the initialization and only ONCE.
+
+Also it is recommended to convert initiators.allow and initiators.deny
+files to the corresponding sysfs facilities.
+
 
 Migration from IET
 ------------------

iscsi-scst/README_in-tree

@@ -20,6 +20,16 @@ configure iSCSI-SCST.
 In 2.0.0 usage of iscsi-scstd.conf as well as iscsi-scst-adm utility is
 obsolete. Use the sysfs interface facilities instead.
 
+The flow of iSCSI-SCST inialization should be as the following:
+
+1. Load of SCST and iSCSI-SCST kernel modules with necessary module
+parameters, if needed.
+
+2. Start iSCSI-SCST service.
+
+3. Configure targets, devices, LUNs, etc. either using scstadmin
+(recommended), or using the sysfs interface directly as described below.
+
 It is recommended to use TEST UNIT READY ("tur") command to check if
 iSCSI-SCST target is alive in MPIO configurations.
 

iscsi-scst/doc/iscsi-scst-howto.txt

@@ -99,12 +99,16 @@ Then run the following commands:
 
   modprobe scst
   modprobe scst_vdisk
-  service iscsi-scst start
+  modprobe iscsi-scst
+  iscsi-scstd
   scstadmin -config /etc/scst.conf
 
 Note that for each SCSI device LUN 0 must exist. This is required by the SCSI
 protocol and is also documented in SCST's README file.
 
+You should have the working iSCSI-SCST now. Do the following steps if
+you need to automatically configure it upon reboot.
+
 4. Edit /etc/init.d/scst
 
 Remove the modules you do not need from the SCST_MODULES variable,
@@ -145,9 +149,8 @@ Next load the scst_disk and scst_vdisk kernel modules as follows:
 
 modprobe scst_disk
 modprobe scst_vdisk
-
-The shell script /etc/init.d/iscsi-scst can now be used to start/stop/restart or
-check the status of iSCSI-SCST.
+modprobe iscsi-scst
+iscsi-scstd
 
 
 Creating targets

iscsi-scst/etc/initd/initd

@@ -51,9 +51,9 @@ start_server()
 		modprobe ${module} || { exit 1 ; }
 	done
 
-	$SCST_CMD -config $SCST_CFG || { exit $? ; }
-
 	/usr/local/sbin/iscsi-scstd
+
+	$SCST_CMD -config $SCST_CFG || { exit $? ; }
 }
 
 stop_server()

scst/README

@@ -128,6 +128,13 @@ log message: "tgt_dev for LUN 0 not found, command to unexisting LU?"
 It is highly recommended to use scstadmin utility for configuring
 devices and security groups.
 
+The flow of SCST inialization should be as the following:
+
+1. Load of SCST modules with necessary module parameters, if needed.
+
+2. Configure targets, devices, LUNs, etc. using either scstadmin
+(recommended), or the sysfs interface directly as described below.
+
 If you experience problems during modules load or running, check your
 kernel logs (or run dmesg command for the few most recent messages).
 
@@ -165,7 +172,6 @@ IMPORTANT: In the current version simultaneous access to local SCSI devices
 
 To uninstall, type 'make scst_uninstall'.
 
-
 Migration from the obsolete proc interface
 ------------------------------------------
 

scst/README_in-tree

@@ -49,6 +49,13 @@ log message: "tgt_dev for LUN 0 not found, command to unexisting LU?"
 It is highly recommended to use scstadmin utility for configuring
 devices and security groups.
 
+The flow of SCST inialization should be as the following:
+
+1. Load of SCST modules with necessary module parameters, if needed.
+
+2. Configure targets, devices, LUNs, etc. using either scstadmin
+(recommended), or the sysfs interface directly as described below.
+
 If you experience problems during modules load or running, check your
 kernel logs (or run dmesg command for the few most recent messages).