>-----Original Message----- >From: Gaurav Gupta [mailto:[EMAIL PROTECTED] >Sent: Thursday, July 31, 2008 9:17 AM >To: Lakshmi Thiruvillamala Ganesh >Cc: Brown, Aaron F; [email protected] >Subject: Re: [Open-FCoE] Installation help -reg > >On Thu, Jul 31, 2008 at 4:18 AM, Lakshmi Thiruvillamala Ganesh ><[EMAIL PROTECTED]> wrote: >> Thanks Brown for your suggestion. I did download the recent >code dump from "snapshot" link. Couple of questions here: >> >> >> 1. What is the approximate size of the source code? >> 2. Any other way we can download the source code?
The command line git and gitweb are the only ways I know of. >> >> I am asking the above questions because the size of the >downloaded code looks as below: >> >> [EMAIL PROTECTED] lakshmi]# ls -lh open-*.gz >> -rw-r--r-- 1 root root 23K 2008-07-31 09:18 >> open-fcoe-upstream-62c1a671f9e1075185c7914a34bc9c7bb347375e[1].tar.gz >> [EMAIL PROTECTED] lakshmi]# >> Yes, the tarball should be somewhere around 60 Megs, it contains the kernel and unless I'm mistaken the branch history. I'm working from the "rearch/open-fcoe-upstream/.git" branch and my pull from gitweb shows: -rw-r--r-- 1 xfer xfer 61M 2008-07-30 04:17 open-fcoe-upstream-9c5b5d6557b401b51bac3313e8260a616f8f65d0.tar.gz An md5sum for it is: $ md5sum open-fcoe-upstream-9c5b5d6557b401b51bac3313e8260a616f8f65d0.tar.gz e8032122e79f7894c30272d096f1ab60 open-fcoe-upstream-9c5b5d6557b401b51bac3313e8260a616f8f65d0.tar.gz > >I just downloaded the source (using git-web) from the most recent HEAD >(62c1..375e) and the size of the tarball is 60M: >-rw-r--r-- 1 60M Jul 31 09:06 >open-fcoe-upstream-62c1a671f9e1075185c7914a34bc9c7bb347375e.tar.gz > >I think you may have downloaded a single commit instead of the >whole repository. That is why you are getting the error while >trying to untar. > Or maybe the download just got corrupted in the process. I would suggest trying the rearch branch as that is the one targeting kernel inclusion and the other branch is not really getting any development effort. The documentation and user tools are more complete in the older branch, and it may even be a bit more stable at the moment, but the rearch branch is the one currently getting attention. Building the rearch branch is really just like building any other kernel. Since I don't think the process for the rearch is well documented yet, if you try it, once you get a good download: - extract it to wherever you wan the kernel source (e.g. /usr/src/kernels on a Red Hat box) - copy a good .config from another kernel build into the upstream kernel directory - Run make menuconfig and select libfc and then fcoe from the Device Drivers -> SCSI device support -> SCSI low-level drivers - Build, install and reboot to the new kernel - To enable fcoe (modprobe fcoe if it is compiled as a module) and echo the ethernet interface into /sys/module/fcoe/create virtual file (on my current system the command is "echo eth2 > /sys/module/fcoe/create - To disable fcoe echo the ethernet interface into /sys/module/fcoe/destroy virtual file - Details about the fcoe interfac can then be found by catting out virtual files in /sys/class/fc_host/hostX/ directory (e.g.j> cat /sys/class/fc_host/host3/port_id for the FCID.) - Enjoy! >> And I get an error when I try to untar the code dump. >> >> [EMAIL PROTECTED] lakshmi]# tar -zvxf >> open-fcoe-upstream-62c1a671f9e1075185c7914a34bc9c7bb347375e[1].tar.gz >> >> gzip: stdin: unexpected end of file >> open-fcoe-upstream/ >> open-fcoe-upstream/.gitignore >> open-fcoe-upstream/.mailmap >> open-fcoe-upstream/COPYING >> open-fcoe-upstream/CREDITS >> tar: Unexpected EOF in archive >> tar: Unexpected EOF in archive >> tar: Error is not recoverable: exiting now >> >> Any help would be appreciated. >> >> Regards, >> Lakshmi >> ________________________________ >> From: Brown, Aaron F [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, July 30, 2008 11:12 PM >> To: Love, Robert W; Lakshmi Thiruvillamala Ganesh; >[email protected] >> Subject: RE: Installation help -reg >> >> If you are being blocked by a firewall for the command line, >you can probably still pull it down with gitweb. Select the >"Code tab" from the open-fcoe.org home page and tehn you can >view the code branch via the "summary" or project column link, >and download the most recent build via the "snapshot" link... >> >> >> ________________________________ >> From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] >> On Behalf Of Love, Robert W >> Sent: Wednesday, July 30, 2008 8:25 AM >> To: Lakshmi Thiruvillamala Ganesh; [email protected] >> Subject: Re: [Open-FCoE] Installation help -reg We have firewall >> issues that prevent us from cloning using the git protocol. >We have to work-around our corporate firewall. Is it possible >that you have a firewall that is blocking you? I just cloned >the repo, using your exact command syntax, from my home and it >worked fine. So, I don't think that the problem is on the server side. >> >> From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] >> On Behalf Of Lakshmi Thiruvillamala Ganesh >> Sent: Wednesday, July 30, 2008 4:05 AM >> To: [email protected] >> Subject: [Open-FCoE] Installation help -reg >> >> Hi FCoE developers, >> >> Kudos on the great work! >> >> I am a new entrant into the FCoE community. After the >initial study on FCoE I am now looking at installing the FCoE >initiator and target. I would require your help on this as I >am stuck at one particular point. >> >> In the "git clone "step I am encountering an error and it >looks as below: >> >> [EMAIL PROTECTED] lakshmi]# git clone >> git://open-fcoe.org/openfc/open-fcoe-upstream.git >> Initialized empty Git repository in >> /root/lakshmi/open-fcoe-upstream/.git/ >> open-fcoe.org[0: 204.253.143.250]: errno=Connection timed out >> fatal: unable to connect a socket (Connection timed out) >> [EMAIL PROTECTED] lakshmi]# >> >> Could anybody please help me resolving this error? >> >> Thanks, >> Lakshmi. >> -- >> R&D Services | MindTree Ltd., Mahindra World City, Chengalpet | >> +91.9962580338 (Mob) >> [EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]> | >> www.mindtree.com<http://www.mindtree.com> >> >> >> >> ________________________________ >> This message (including attachment if any) is confidential >and may be privileged. If you have received this message by >mistake please notify the sender by return e-mail and delete >this message from your system. Any unauthorized use or >dissemination of this message in whole or in part is strictly >prohibited. E-mail may contain viruses. Before opening >attachments please check them for viruses and defects. While >MindTree Limited (MindTree) has put in place checks to >minimize the risks, MindTree will not be responsible for any >viruses or defects or any forwarded attachments emanating >either from within MindTree or outside. >> >> Please note that e-mails are susceptible to change and >MindTree shall not be liable for any improper, untimely or >incomplete transmission. >> >> MindTree reserves the right to monitor and review the >content of all messages sent to or from MindTree e-mail >address. Messages sent to or from this e-mail address may be >stored on the MindTree e-mail system or else where. >> >> ________________________________ >> This message (including attachment if any) is confidential >and may be privileged. If you have received this message by >mistake please notify the sender by return e-mail and delete >this message from your system. Any unauthorized use or >dissemination of this message in whole or in part is strictly >prohibited. E-mail may contain viruses. Before opening >attachments please check them for viruses and defects. While >MindTree Limited (MindTree) has put in place checks to >minimize the risks, MindTree will not be responsible for any >viruses or defects or any forwarded attachments emanating >either from within MindTree or outside. >> >> Please note that e-mails are susceptible to change and >MindTree shall not be liable for any improper, untimely or >incomplete transmission. >> >> MindTree reserves the right to monitor and review the >content of all messages sent to or from MindTree e-mail >address. Messages sent to or from this e-mail address may be >stored on the MindTree e-mail system or else where. >> _______________________________________________ >> devel mailing list >> [email protected] >> http://www.open-fcoe.org/mailman/listinfo/devel >> > _______________________________________________ devel mailing list [email protected] http://www.open-fcoe.org/mailman/listinfo/devel
