Downloads

The Linux SCSI Target Wiki

(Difference between revisions)
Jump to: navigation, search
({{anchor|4|4.0}} LIO 4 (released Linux tip-of-tree kernels))
m (Contact)
 
(185 intermediate revisions not shown)
Line 1: Line 1:
-
The '''Downloads''' page contains the references to all free download repositories.
+
The '''Downloads''' page contains the instructions for all free download repositories.
-
== {{anchor|RTS OS}} [[RTS OS]] ==
+
== Linux inclusion ==
-
[[RTS OS]] provides a comprehensive, integrated single-node storage operating system based on LIO. RTS OS comes in form of an ISO that can be booted natively and/or in virtual machines ([[Kernel-based Virtual Machine|KVM]], [[VMware ESX]], etc.).
+
Versions of {{T}} and ''targetcli'' are included in most Linux distributions per default. Here is an overview over the most popular distributions:
-
== targetcli ==
+
{{Linux Inclusion}}
-
''targetcli'' is the general management platform for LIO. It is available under dual licensing:
+
== {{anchor|targetcli|cli}} [[targetcli]] ==
-
* The [[targetcli]] ''Community Edition'' is released under the [http://www.gnu.org/licenses/agpl.html GNU Affero General Public License] (AGPLv3), and the corresponding source code is available from our public git repository at [http://www.risingtidesystems.com/git risingtidesystems.com/git]. The Community Edition supports configuring the [[Target]] only. Everyone is welcome to [[Contributing|contribute]] to the Community Edition.
+
=== Overview ===
-
* The RTSadmin ''Enterprise Edition'' is released under the commercial [[RisingTide Systems|RTS]] license, and allows the management of complex full storage systems.
+
-
''targetcli'' was initially released in May 2011, and it supports all fabric modules, currently including [[iSCSI]], [[Fibre Channel]], [[Fibre Channel over Ethernet|FCoE]], [[InfiniBand]], [[IBM vSCSI]] and [[tcm_loop]], see also [[Target#Fabric modules|Target]]. It is is based on a modular, extensible architecture, with plug-in modules for additional functionality.
+
''[[targetcli]]'' is the general management platform for {{T}}. It comprises a shell that uses the {{Target}} library through a well-defined API, and is available under the {{Apache 2}}. Everyone is welcome to [[Contributing|contribute]].
-
== {{anchor|4|4.0}} LIO 4 (released Linux tip-of-tree kernels) ==
+
''targetcli'' was released on {{RTS releases|RTSadmin|initial_date}}, and supports all fabric modules, including [[FCoE]], [[Fibre Channel]], [[IBM vSCSI]], [[iSCSI]], [[iSER]], [[SRP]], [[tcm_loop]], and [[vHost]]. It is is based on a modular, extensible architecture, with plug-in modules for additional functionality.
-
[http://git.kernel.org/?p=linux/kernel/git/nab/target-pending.git target-pending.git (v4.1.0-rcX)] for kernel developers building on [http://kernel.org kernel.org]. This tree includes the core [[Target]] engine v4.x logic.
+
''targetcli'' consists of three Python modules ([[targetcli#Download|download and build]] instructions):
-
This tree tracks the Linux kernel tree and follows the upstream linux kernel release schedule. It for kernel developers who are interested in contributing to the upstream LIO code, and are comfortable running and debugging bleeding edge kernel code. It involves building a complete running Linux kernel and associated modules, and expects the user to have experience with configuring, building and installing kernels.
+
* the ''targetcli'' user shell itself ({{RTS releases|RTSadmin|module_cli}})
 +
* the underlying ''rtslib'' ({{RTS releases|RTSadmin|module_lib}}) and API {{Lib Ref Guide HTML}}{{Lib Ref Guide PDF}}
 +
* the ''configshell'' that provides extensibility ({{RTS releases|RTSadmin|module_cfg}})
 +
 
 +
=== Installation ===
 +
 
 +
If your Linux distribution doesn't already contain an adequate ''targetcli'' version, or ''targetcli'' can't be installed as described above, you can manually install it from the {{RTS short}} repositories as follows.
 +
 
 +
==== Clone GIT repositories ====
 +
 
 +
The source code of the three ''targetcli'' components ({{RTS releases|RTSadmin|module_cfg}}, {{RTS releases|RTSadmin|module_lib}}, {{RTS releases|RTSadmin|module_cli}}) is available for downloaded from their GIT repositories, respectively:
<pre>
<pre>
-
# Clone the full git tree
+
$ git clone https://github.com/Datera/configshell.git
-
git clone git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git target-pending.git
+
$ git clone https://github.com/Datera/rtslib.git
-
# Change dir
+
$ git clone https://github.com/Datera/targetcli.git
-
cd target-pending.git/
+
-
# Show available remote branches
+
-
git branch -vr
+
</pre>
</pre>
-
== {{anchor|3}} LIO 3 backports (Linux kernels &ge;2.6.18) ==
+
==== Install and Build ====
-
[http://risingtidesystems.com/git/?p=lio-core-backports.git;a=summary lio-core-backports.git] is for users who are interested in running LIO kernel code on a existing unmodified kernel environment, and therefore need "out-of-tree" Linux sources (available from {{RTS full}}).
+
Please follow the distribution-specific instructions:
-
This tree allows building the LIO kernel modules and packages on many popular distributions, and any kernel back to v2.6.18. It includes [[Target]]+[[iSCSI]] v3.1, and the [[Backports HOWTO]] on installing, configuring and building backport targets for older trees.
+
* [[CentOS]]
 +
* [[Debian]]
 +
* [[Fedora]]
 +
* [[openSUSE]]
 +
* [[RHEL]]
 +
* [[Scientific Linux]]
 +
* [[SLES]]
 +
* [[Ubuntu]]
-
There are two key parts to it:
+
==== Run ====
-
* LIO 3 source in a ''[http://en.wikipedia.org/wiki/Git_(software) git]'' tree (lio-core-2.6.git, which tracks linux-2.6.git, Linus' development tree for the next offical release for the kernel.org project).  LIO 3 for stable kernel.org releases (v2.6.x.y) is made available after Linus tags his first stable release of v2.6.x, and then (after a short break) begins the next development cycle (v2.6.x+1-rc1).
+
-
* [[lio-utils]] 3 userspace tools.
+
-
The [[Backports HOWTO]] describes how to build, install and run LIO&nbsp;3 and its tools.
+
Run ''targetcli'' as 'root' as follows:
-
=== LIO v3.4.0 for Linux v2.6.34 ===
+
<pre>
 +
# PYTHONPATH=. ./scripts/targetcli
 +
</pre>
-
This is tracking the <code>linux-2.6.34.y.git</code> tree.
+
== {{anchor|Target|LIO|4|4.0}} {{Target}} ==
 +
 
 +
=== Overview ===
 +
 
 +
[http://git.kernel.org/?p=linux/kernel/git/nab/target-pending.git target-pending.git (v4.1.0-rcX)] is for kernel developers and users who want to use the latest {{T}} code before it becomes available in the mainline [http://www.linux.com/ Linux] [http://www.kernel.org/ Kernel]. This tree tracks Linus' [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git mainline] and follows the quarterly kernel release schedule. It is intended for kernel developers who are interested in contributing to the upstream {{T}} code, and are comfortable running and debugging bleeding edge kernel code. It involves building a complete running Linux kernel and associated modules, and expects the user to have experience with configuring, building and installing kernels.
 +
 
 +
{{Ambox| type=warning| head=''lio-core.git'' is deprecated.| text=The ''lio-core.git'' development tree has been deprecated as of June 2012.}}
 +
 
 +
Starting with 3.5-rc code in June 2012, the target-pending.git tree is now setup using a [http://permalink.gmane.org/gmane.linux.scsi.target.devel/1974 work-flow] similar to [http://www.linux-kvm.org/page/Kvm-Git-Workflow Kvm-Git-Workflow] using the following branch structure:
 +
 
 +
* '''master''': contains latest target rc-fixes for the current release
 +
* '''for-next''': contains developmental patches for next merge window
 +
* '''for-next-merge''': contains new fabric drivers for next merge window
 +
* '''queue''': contains untested patches (usually) headed into for-next*
 +
* '''auto-next''': combination of current master + for-next* (rebased often)
 +
 
 +
If you're a developer, usually developing against 'for-next' is okay. If 'for-next' is unstable for you or you need a new upstream API, work against 'auto-next', but let the maintainers know that when posting your patch.
 +
 
 +
If you're working on a fix for the current cycle, work against upstream or 'master' (they should be equivalent most of the time).
 +
 
 +
If you're a sub-maintainer, post ''git'' pull requests against 'for-next' or 'master', according to your merge target.
 +
 
 +
{{Ambox| type=note| head=Backports| text=[[Datera]] offers stable qual'd backport trees for sale for most older Linux kernels and for most Linux distributions.}}
 +
 
 +
{{Ambox| type=info| head=SCSI test suite| text={{RTS releases|RTSadmin|module_test}} provides a complementary open-source SCSI test suite.}}
 +
 
 +
=== Installation ===
 +
 
 +
==== Clone GIT repositories ====
 +
 
 +
The source code of the {{Target}} ({{RTS releases|LIO|module_repo}}) engine is available for download from its kernel.org GIT repository. First, close the full git tree:
<pre>
<pre>
-
git clone git://git.kernel.org/pub/scm/linux/kernel/git/nab/lio-core-2.6.git lio-core-2.6.git
+
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git target-pending.git
-
git checkout origin/lio-3.4
+
</pre>
</pre>
-
=== LIO v3.3.0 for Linux v2.6.33 ===
+
Show the available remote branches:
-
This is tracking the <code>linux-2.6.33.y.git</code> tree.
+
<pre>
 +
$ cd target-pending.git/
 +
$ git branch -vr
 +
</pre>
 +
 
 +
==== Resolve dependencies ====
 +
 
 +
Install the necessary kernel development packages, including ''gcc'', ''make'', ''libncurses-dev''.
 +
 
 +
===== Debian =====
 +
 
 +
On a Debian based system these packages ([http://packages.debian.org/sid/gcc gcc], [http://packages.debian.org/sid/make make], [http://packages.debian.org/sid/libncurses5-dev libncurses5-dev]) can be installed as follows:
<pre>
<pre>
-
git clone git://git.kernel.org/pub/scm/linux/kernel/git/nab/lio-core-2.6.git lio-core-2.6.git
+
$ su -c 'apt-get install gcc make libncurses5-dev kernel-devel'
-
git checkout origin/lio-3.3
+
</pre>
</pre>
-
=== LIO v3.2.2 for Linux v2.6.32 ===
+
===== RHEL/CentOS/Fedora =====
-
This tracking the <code>linux-2.6.32.y.git</code> tree.
+
<pre>
 +
$ su -c 'yum install gcc make ncurses-devel kernel-devel'
 +
</pre>
 +
 
 +
===== SLES/openSUSE =====
<pre>
<pre>
-
git clone git://git.kernel.org/pub/scm/linux/kernel/git/nab/lio-core-2.6.git lio-core-2.6.git
+
$ su -c 'zypper install gcc make ncurses-devel kernel-devel'
-
git checkout origin/lio-3.2
+
</pre>
</pre>
-
=== LIO v3.1.4 for Linux v2.6.30 ===
+
===== Ubuntu =====
-
This is tracking the <code>linux-2.6.30.y.git</code> tree.
+
<pre>
 +
$ su -c 'apt-get install gcc make ncurses-devel kernel-devel'
 +
</pre>
 +
 
 +
==== Select modules ====
 +
 
 +
To configure the kernel build (hardware dependent), run:
<pre>
<pre>
-
git clone git://git.kernel.org/pub/scm/linux/kernel/git/nab/lio-core-2.6.30.git lio-core-2.6.30.git
+
$ make menuconfig
-
git checkout origin/lio-3.0
+
</pre>
</pre>
-
: and switch back to HEAD:
+
===== {{Target}} =====
 +
 
 +
Enable the {{T}} ({{RTS releases|LIO|module_repo}}) module and the desired backend driver modules.
 +
 
 +
Also, enable the desired fabric drivers for [[iSCSI]] ({{RTS releases|iSCSI|module_repo}}), [[FCoE]] ({{RTS releases|FCoE|module_repo}}), [[tcm_loop]] ({{RTS releases|tcm_loop|module_repo}}), and Firewire SBP-2:
<pre>
<pre>
-
git checkout origin/master
+
        Device Drivers  --->
 +
                <M> Generic Target Core Mod (TCM) and ConfigFS Infrastructure  --->
 +
 
 +
                --- Generic Target Core Mod (TCM) and ConfigFS Infrastructure
 +
                  <M>  TCM/IBLOCK Subsystem Plugin for Linux/BLOCK
 +
                  <M>  TCM/FILEIO Subsystem Plugin for Linux/VFS
 +
                  <M>  TCM/pSCSI Subsystem Plugin for Linux/SCSI
 +
                  <M>  TCM Virtual SAS target and Linux/SCSI LDD fabric loopback module
 +
                  <M>  TCM_FC fabric Plugin
 +
                  <M>  Linux-iSCSI.org iSCSI Target Mode Stack
 +
                  <M>  FireWire SBP-2 fabric module
</pre>
</pre>
-
=== LIO v3.0.0 for Linux v2.6.29 ===
+
===== Mellanox InfiniBand =====
-
This is tracking the <code>linux-2.6.29.y.git</code> tree.
+
Optionally, enable the [[InfiniBand]] target module ({{RTS releases|SRP-Mellanox|module_repo}}), plus the ''umad'' and ''verbs'' modules:
<pre>
<pre>
-
git clone git://git.kernel.org/pub/scm/linux/kernel/git/nab/lio-core-2.6.29.git lio-core-2.6.29.git
+
        Device Drivers --->
-
git checkout origin/lio-3.0
+
                <M> InfiniBand support  --->
 +
 
 +
                --- InfiniBand support                   
 +
                  <M>  InfiniBand userspace MAD support                           
 +
                  <M>  InfiniBand userspace access (verbs and CM) 
 +
                  <M>  InfiniBand SCSI RDMA Protocol target support         
</pre>
</pre>
-
And the [http://git.kernel.org/?p=linux/kernel/git/nab/lio-core-2.6.29.git;a=summary LIO v3.0 HEAD] is available at:
+
===== QLogic Fibre Channel =====
 +
 
 +
Optionally, enable the QLogic [[Fibre Channel]] target module ({{RTS releases|FC-QLogic|module_repo}}), including its SCSI LLD:
<pre>
<pre>
-
git checkout origin/master
+
        Device Drivers --->
 +
                SCSI device support  --->
 +
                        [*] SCSI low-level drivers  --->
 +
 
 +
                --- SCSI low-level drivers 
 +
                  <M>  QLogic QLA2XXX Fibre Channel Support
 +
                  <M>  TCM_QLA2XXX fabric module for Qlogic 2xxx series target mode HBAs
</pre>
</pre>
-
== {{anchor|2|2.9}} LIO 2.9 legacy (Linux kernels &le;2.6.28) ==
+
===== USB Gadget =====
 +
 
 +
Optionally, enable the USB Gadget module:
 +
 
 +
<pre>
 +
        Device Drivers --->
 +
                [*] USB support  --->
 +
                        <M>  USB Gadget Support  --->       
 +
 
 +
                --- USB Gadget Support
 +
                  <M>    USB Gadget Target Fabric Module
 +
</pre>
 +
 
 +
==== Build ====
 +
 
 +
Build the Linux kernel with the selected modules:
 +
 
 +
<pre>
 +
$ make bzImage ; make modules
 +
</pre>
 +
 
 +
==== Install ====
 +
 
 +
Install the Linux kernel with the selected modules:
 +
 
 +
<pre>
 +
$ su -c 'make modules_install ; make install'
 +
</pre>
 +
 
 +
==== Rebuild initrd ====
 +
 
 +
If necessary, back up and rebuild the initial RAM disk ''initrd'' depending on the distribution.
 +
 
 +
===== Debian =====
 +
 
 +
Rebuild ''initrd'' by running the following command:
 +
 
 +
<pre>
 +
$ su -c 'update-initrd -c -k $(uname -r)'
 +
</pre>
 +
 
 +
===== RHEL/CentOS/Fedora =====
 +
 
 +
Rebuild ''initrd'' by running the following command:
 +
 
 +
<pre>
 +
$ su -c 'mkinitrd -f /boot/initramfs-$(uname -r).img $(uname -r)'
 +
</pre>
 +
 
 +
===== SLES/OpenSUSE =====
 +
 
 +
Rebuild ''initrd'' by running the following command:
 +
 
 +
<pre>
 +
$ su -c 'mkinitrd'
 +
</pre>
 +
 
 +
===== Ubuntu =====
 +
 
 +
Rebuild ''initrd'' by running the following command:
 +
 
 +
<pre>
 +
$ su -c 'update-initramfs -c -k $(uname -r)'
 +
</pre>
 +
 
 +
== Contact ==
 +
 
 +
Please post your comments, questions or bug reports here:
 +
 
 +
* For {{T}} or ''[[targetcli]]'': the [http://www.spinics.net/lists/target-devel/ target-devel] mailing list ([mailto:target-devel@vger.kernel.org post], [mailto:majordomo@vger.kernel.org&body=subscribe%20target-devel subscribe], [http://vger.kernel.org/vger-lists.html#target-devel list info], [http://dir.gmane.org/gmane.linux.scsi.target.devel gmane archive])
 +
* For the [[Initiator]]: the [http://groups.google.com/group/Core-iSCSI Core-iSCSI] mailing list
 +
* For general SCSI: the [http://marc.info/?l=linux-scsi&r=1&w=2 linux-scsi] mailing list
 +
* For the Linux kernel: the [http://lkml.org/ Linux Kernel mailing list] ([http://marc.info/?l=linux-kernel&r=1&w=2 archive])
-
The v2.9-STABLE current release is v2.9.0.423 (r415) for Linux kernels &le;2.6.28. This is the legacy v2.9 tree, which has been in maintence mode since 2008.  It is still hosted in an SVN repositiry, yet does not contain support for modern features, such as [[Persistent Reservations]], [[Asymmetric Logical Unit Assignment|ALUA]], [[configFS]], etc. The [http://linux-iscsi.org/svn/trunk/README README] describes how to build [[iSCSI]] 2.9 for your distribution from the sources.
+
Please see [[Support]] for more information.
== See also ==
== See also ==
 +
* {{Target}}, [[targetcli]]
 +
* [[{{OS}}]]
* [[Support]]
* [[Support]]
-
* [[Backports HOWTO]]
 
== External links ==
== External links ==
-
* {{Official|http://www.risingtidesystems.com RisingTide Systems}}  
+
* {{Official|http://www.daterainc.com/}}  
[[Category:Support]]
[[Category:Support]]

Latest revision as of 05:17, 20 May 2015

The Downloads page contains the instructions for all free download repositories.

Contents

Linux inclusion

Versions of LIO and targetcli are included in most Linux distributions per default. Here is an overview over the most popular distributions:

Distribution Version[Linux 1] Release Archive Install Source git[Linux 2] Documentation
CentOS 6.2 2011-12-20 CentOS mirror su -c 'yum install fcoe-target-utils' targetcli-fb.git Tech Notes
Debian 7.0 ("wheezy") TBA Debian pool su -c 'apt-get install targetcli' targetcli
Fedora 16, 17/18 2011-11-08 Fedora Rawhide su -c 'yum install targetcli' targetcli-fb.git Target Wiki
openSUSE 12.1 2011-11-08 Requires manual installation from targetcli.
RHEL 6.2 2011-11-16 Fedora Rawhide su -c 'yum install fcoe-target-utils' targetcli-fb.git Tech Notes
Scientific Linux 6.2 2012-02-16 SL Mirror su -c 'yum install fcoe-target-utils' targetcli-fb.git Tech Notes
SLES SP2 2012-02-15 Requires manual installation from targetcli.
Ubuntu PrecisePangolin v12 2012-04-26 Ubuntu universe su -c 'apt-get install targetcli' targetcli
  1. The distribution release where LIO was included first.
  2. Technical support, and qualified backports to other kernels and distributions are available from Datera.

targetcli

Overview

targetcli is the general management platform for LIO. It comprises a shell that uses the LinuxIO library through a well-defined API, and is available under the Apache License, version 2.0 (Apache License). Everyone is welcome to contribute.

targetcli was released on October 14, 2009 (2009-10-14), and supports all fabric modules, including FCoE, Fibre Channel, IBM vSCSI, iSCSI, iSER, SRP, tcm_loop, and vHost. It is is based on a modular, extensible architecture, with plug-in modules for additional functionality.

targetcli consists of three Python modules (download and build instructions):

Installation

If your Linux distribution doesn't already contain an adequate targetcli version, or targetcli can't be installed as described above, you can manually install it from the Datera repositories as follows.

Clone GIT repositories

The source code of the three targetcli components (configshell, RTSlib, targetcli) is available for downloaded from their GIT repositories, respectively:

$ git clone https://github.com/Datera/configshell.git
$ git clone https://github.com/Datera/rtslib.git
$ git clone https://github.com/Datera/targetcli.git

Install and Build

Please follow the distribution-specific instructions:

Run

Run targetcli as 'root' as follows:

# PYTHONPATH=. ./scripts/targetcli

LinuxIO

Overview

target-pending.git (v4.1.0-rcX) is for kernel developers and users who want to use the latest LIO code before it becomes available in the mainline Linux Kernel. This tree tracks Linus' mainline and follows the quarterly kernel release schedule. It is intended for kernel developers who are interested in contributing to the upstream LIO code, and are comfortable running and debugging bleeding edge kernel code. It involves building a complete running Linux kernel and associated modules, and expects the user to have experience with configuring, building and installing kernels.

Starting with 3.5-rc code in June 2012, the target-pending.git tree is now setup using a work-flow similar to Kvm-Git-Workflow using the following branch structure:

If you're a developer, usually developing against 'for-next' is okay. If 'for-next' is unstable for you or you need a new upstream API, work against 'auto-next', but let the maintainers know that when posting your patch.

If you're working on a fix for the current cycle, work against upstream or 'master' (they should be equivalent most of the time).

If you're a sub-maintainer, post git pull requests against 'for-next' or 'master', according to your merge target.

Installation

Clone GIT repositories

The source code of the LinuxIO (target_core.ko) engine is available for download from its kernel.org GIT repository. First, close the full git tree:

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git target-pending.git

Show the available remote branches:

$ cd target-pending.git/
$ git branch -vr

Resolve dependencies

Install the necessary kernel development packages, including gcc, make, libncurses-dev.

Debian

On a Debian based system these packages (gcc, make, libncurses5-dev) can be installed as follows:

$ su -c 'apt-get install gcc make libncurses5-dev kernel-devel'
RHEL/CentOS/Fedora
$ su -c 'yum install gcc make ncurses-devel kernel-devel'
SLES/openSUSE
$ su -c 'zypper install gcc make ncurses-devel kernel-devel'
Ubuntu
$ su -c 'apt-get install gcc make ncurses-devel kernel-devel'

Select modules

To configure the kernel build (hardware dependent), run:

$ make menuconfig
LinuxIO

Enable the LIO (target_core.ko) module and the desired backend driver modules.

Also, enable the desired fabric drivers for iSCSI (iscsi.ko), FCoE (tcm_fc.ko), tcm_loop (loopback.ko), and Firewire SBP-2:

         Device Drivers  --->
                 <M> Generic Target Core Mod (TCM) and ConfigFS Infrastructure  --->

                 --- Generic Target Core Mod (TCM) and ConfigFS Infrastructure
                   <M>   TCM/IBLOCK Subsystem Plugin for Linux/BLOCK
                   <M>   TCM/FILEIO Subsystem Plugin for Linux/VFS
                   <M>   TCM/pSCSI Subsystem Plugin for Linux/SCSI
                   <M>   TCM Virtual SAS target and Linux/SCSI LDD fabric loopback module
                   <M>   TCM_FC fabric Plugin 
                   <M>   Linux-iSCSI.org iSCSI Target Mode Stack
                   <M>   FireWire SBP-2 fabric module
Mellanox InfiniBand

Optionally, enable the InfiniBand target module (srpt.ko), plus the umad and verbs modules:

        Device Drivers --->
                <M> InfiniBand support  --->

                --- InfiniBand support                     
                   <M>   InfiniBand userspace MAD support                             
                   <M>   InfiniBand userspace access (verbs and CM)  
                   <M>   InfiniBand SCSI RDMA Protocol target support           
QLogic Fibre Channel

Optionally, enable the QLogic Fibre Channel target module (qla2xxx.ko), including its SCSI LLD:

        Device Drivers --->
                 SCSI device support  --->
                         [*] SCSI low-level drivers  --->

                 --- SCSI low-level drivers   
                   <M>   QLogic QLA2XXX Fibre Channel Support
                   <M>   TCM_QLA2XXX fabric module for Qlogic 2xxx series target mode HBAs
USB Gadget

Optionally, enable the USB Gadget module:

        Device Drivers --->
                [*] USB support  ---> 
                         <M>   USB Gadget Support  --->        

                --- USB Gadget Support 
                  <M>     USB Gadget Target Fabric Module

Build

Build the Linux kernel with the selected modules:

$ make bzImage ; make modules 

Install

Install the Linux kernel with the selected modules:

$ su -c 'make modules_install ; make install'

Rebuild initrd

If necessary, back up and rebuild the initial RAM disk initrd depending on the distribution.

Debian

Rebuild initrd by running the following command:

$ su -c 'update-initrd -c -k $(uname -r)'
RHEL/CentOS/Fedora

Rebuild initrd by running the following command:

$ su -c 'mkinitrd -f /boot/initramfs-$(uname -r).img $(uname -r)'
SLES/OpenSUSE

Rebuild initrd by running the following command:

$ su -c 'mkinitrd'
Ubuntu

Rebuild initrd by running the following command:

$ su -c 'update-initramfs -c -k $(uname -r)'

Contact

Please post your comments, questions or bug reports here:

Please see Support for more information.

See also

External links

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Google AdSense