[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
howtos:network_services:iscsi [2019/11/09 01:08 (UTC)] – [Configuration] bifferoshowtos:network_services:iscsi [2019/12/01 00:05 (UTC)] – [Configuration] bifferos
Line 42: Line 42:
 The kernel modules are also loaded automatically by Slackware-current.  open-iscsi SlackBuild on SBO has been recently fixed, so should install with slpkg -s sbo open-isci. The kernel modules are also loaded automatically by Slackware-current.  open-iscsi SlackBuild on SBO has been recently fixed, so should install with slpkg -s sbo open-isci.
  
-==== Configuration ====+==== Target Configuration ====
  
-First, get the initiator ID from the client:+First, get the initiator ID from the initiator (client):
 <code> <code>
 # cat /etc/iscsi/initiatorname.iscsi  # cat /etc/iscsi/initiatorname.iscsi 
 </code> </code>
  
-Then on the server+It will be important later. 
 + 
 +Next we need to configure our target (that's the 'server' remember?).  In order to do this we use something called target-cli, so get targetcli-fb from Slackbuilds and install it: 
 + 
 +<code> 
 +slpkg -s sbo targetcli-fb 
 +</code> 
 + 
 +Targetcli requires a directory to store its data, make sure it exists:
  
 <code> <code>
Line 55: Line 63:
 </code> </code>
  
-TO BE CONTINUED....+targetcli is a bit like a command-line directory browser except you use it to change values in a hierarchical store. That same hierarchy also contains the commands you invoke to make changes, however.  You've probably not seen anything like it before and it's best just described by example. 
 + 
 + 
 + 
 + 
  
  

Trace:

howtos:network_services:iscsi ()