A user should be able to grab a released kernel from kernel.org and one of the Open-FCoE.org releases to get started quickly. Refer to the QUICKSTART guide within the fcoe-utils directory for setup instructions. Cloning the hbaapi_build, libhbalinux and fcoe-utils repositories can be skipped since that code is already included in the release.
For every Linux kernel release the non-kernel components’ source code is collected, archived in a tarball and posted on the Open-FCoE.org downloads page. These releases include the hbaapi_build, libhbalinux and fcoe-utils source code. Only minimal testing is done on these releases and there is no backporting of patches to previous releases. These tarballs are simply snapshots of the codebase when the mainline kernels are released.
A user should be able to grab a released kernel from kernel.org and one of the Open-FCoE.org releases to get started quickly. Refer to the QUICKSTART guide within the fcoe-utils directory for setup instructions. Cloning the hbaapi_build, libhbalinux and fcoe-utils repositories can be skipped since that code is already included in the release.
For every Linux kernel release the non-kernel components’ source code is collected, archived in a tarball and posted on the Open-FCoE.org downloads page. These releases include the hbaapi_build, libhbalinux and fcoe-utils source code. Only minimal testing is done on these releases and there is no backporting of patches to previous releases. These tarballs are simply snapshots of the codebase when the mainline kernels are released.
A user should be able to grab a released kernel from kernel.org and one of the Open-FCoE.org releases to get started quickly. Refer to the QUICKSTART guide within the fcoe-utils directory for setup instructions. Cloning the hbaapi_build, libhbalinux and fcoe-utils repositories can be skipped since that code is already included in the release.
A user should be able to grab a released kernel from kernel.org and one of the Open-FCoE.org releases to get started quickly. Refer to the QUICKSTART guide within the fcoe-utils directory for setup instructions. Cloning the hbaapi_build, libhbalinux and fcoe-utils repositories can be skipped since that code is already included in the release.
A user should be able to grab a released kernel from kernel.org and one of the Open-FCoE.org releases to get started quickly. Refer to the QUICKSTART guide within the fcoe-utils directory for setup instructions. Cloning the hbaapi_build, libhbalinux and fcoe-utils repositories can be skipped since that code is already included in the release.
For every Linux kernel release the non-kernel components’ source code is collected, archived in a tarball and posted on the Open-FCoE.org downloads page. These releases include the hbaapi_build, libhbalinux and fcoe-utils source code. Only minimal testing is done on these releases and there is no backporting of patches to previous releases. These tarballs are simply snapshots of the codebase when the mainline kernels are released.
A user should be able to grab a released kernel from kernel.org and one of the Open-FCoE.org releases to get started quickly. Refer to the QUICKSTART guide within the fcoe-utils directory for setup instructions. Cloning the hbaapi_build, libhbalinux and fcoe-utils repositories can be skipped since that code is already included in the release.
A user should be able to grab a released kernel from kernel.org and one of the Open-FCoE.org releases to get started quickly. Refer to the QUICKSTART guide within the fcoe-utils directory for setup instructions. Cloning the hbaapi_build, libhbalinux and fcoe-utils repositories can be skipped since that code is already included in the release.
]]>A user should be able to grab a released kernel from kernel.org and one of the Open-FCoE.org releases to get started quickly. Refer to the QUICKSTART guide within the fcoe-utils directory for setup instructions. Cloning the hbaapi_build, libhbalinux and fcoe-utils repositories can be skipped since that code is already included in the release.
The Open-FCoE.org user space tarball has been posted on the downloads page to coincide with the 2.6.35 kernel release
]]>For every Linux kernel release the non-kernel components’ source code is collected, archived in a tarball and posted on the Open-FCoE.org downloads page. These releases include the hbaapi_build, libhbalinux and fcoe-utils source code. Only minimal testing is done on these releases and there is no backporting of patches to previous releases. These tarballs are simply snapshots of the codebase when the mainline kernels are released.
A user should be able to grab a released kernel from kernel.org and one of the Open-FCoE.org releases to get started quickly. Refer to the QUICKSTART guide within the fcoe-utils directory for setup instructions. Cloning the hbaapi_build, libhbalinux and fcoe-utils repositories can be skipped since that code is already included in the release.
]]>
The repository is visible on our gitweb page and is accessable from the following git URL.
git://open-fcoe.org/openfc/libhbalinux.git
We’ll also add new options to fcoeadm to display information about Open-FCoE HBAs using libhbalinux.
]]>Open-FCoE is the home of the Fibre Channel over Ethernet implementation for the Linux operating system. Our code base provides some Fibre Channel protocol processing as well as the encapsulation of FC frames within Ethernet packets. We are excited to bring this technology to the public and will do our best to facilitate everyone on this site.
We’ve created a mailing list for developers. However, we believe that most discussions will take place on the SCSI mailing list. We will post details as we understand more about how we’ll work with the existing SCSI community.
The Bugzilla and Wiki are open for anyone. We would like to keep it that way unless spam becomes a problem in which case we will tighten up access. We will also be configuring them more as this project evolves. We would like for these tools to be used heavily as they’ll help ensure we have a quality experience for both developers and users.
The download page has a single tarball of our open-fcoe tree at the time of this project’s launch. It is a derivative of the SCSI –rc tree and is therefore currently under development, which means it might be a bit unstable. We will work to make more stable tarballs available for download as the project matures.
Our SW Target, which resides in the –misc repository, relies on SCST. At this project’s launch time we did not have SCST working with the 2.6.24-rc2 tree. We wanted something usable so we’ve copied our old 2.6.23 compatible code into this repository for now. You’ll need to get a vanilla 2.6.23 kernel and follow the INSTALL document in the –misc tree to get the target to work.
To reiterate, the initiator is working with the SCSI 2.6.24-rc tree (which is contained in the –upstream repository) and the SW Target works on a vanilla 2.6.23 tree. We’ve written a rough quickstart guide to help everyone get started.
Thank you and welcome to Open-FCoE.org!
]]>