From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1LecNR-000302-MV for mharc-grub-devel@gnu.org; Tue, 03 Mar 2009 16:42:13 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LecNO-0002wn-PV for grub-devel@gnu.org; Tue, 03 Mar 2009 16:42:10 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LecNN-0002w7-50 for grub-devel@gnu.org; Tue, 03 Mar 2009 16:42:10 -0500 Received: from [199.232.76.173] (port=33564 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LecNM-0002w4-W3 for grub-devel@gnu.org; Tue, 03 Mar 2009 16:42:09 -0500 Received: from mail-fx0-f172.google.com ([209.85.220.172]:41512) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LecNM-0004w0-EH for grub-devel@gnu.org; Tue, 03 Mar 2009 16:42:08 -0500 Received: by fxm20 with SMTP id 20so2630266fxm.42 for ; Tue, 03 Mar 2009 13:42:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=rC9+xTQTUPgL7gbA5sXDvW3MH6B3CSQAbKh5EkK3Duk=; b=OjhMdIfsnUNVzgZwnFcBba+PdvBzWmrwoYYWoU7cnpN+Qna4YVxk0bE2okLx02ju8H cVEL0Xgh0RkE7/w3Cd+ZpB0zD/36oWo4FNAQTT2LVFhVvQZnvNDp0yXoaBYKrYAl6z4v p/zPmI8RooxkwP2HsgNdQiRnKfyL7m6AcBDFI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=NMLSpnmGfDHRlvqQHf7sr6Rfe2MDynPhmBPNC1GI2/OpgN99dX7zsG16sr1UZ8Wt+2 bLEQy10pqxTo3oxZMKKwOS1YTkM9fXlFrQJjv/akbc3Pulsoztotq0wB2bAePF1v6W1q qcCpiHw55bnAPhO8PMGpMdxj3w8vc+lvbIeLU= Received: by 10.86.3.4 with SMTP id 4mr71697fgc.41.1236116526848; Tue, 03 Mar 2009 13:42:06 -0800 (PST) Received: from ?192.168.1.2? (20-72.3-85.cust.bluewin.ch [85.3.72.20]) by mx.google.com with ESMTPS id d6sm1219754fga.2.2009.03.03.13.42.06 (version=SSLv3 cipher=RC4-MD5); Tue, 03 Mar 2009 13:42:06 -0800 (PST) Message-ID: <49ADA42E.4020300@gmail.com> Date: Tue, 03 Mar 2009 22:42:06 +0100 From: phcoder User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: The development of GRUB 2 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: Summer of code proposition: TCP/IP Anybody want to mentor? X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Mar 2009 21:42:11 -0000 Hello. Here is a zeroth draft of SoC proposal: Complete TCP/IP stack GRUB Legacy supported tftp. This is a basic protocal specially adapted for netbooting. However we feel that grub2 can be much more flexible if it supports other widely-used protocols like ftp, http, smb, nfs and dns. The common base for these protocols can be lwIP(http://savannah.nongnu.org/projects/lwip/) which is under BSD licence. Drivers already present in grub1 can be easily ported to this framework. Then application layer protocols would have to be written. Each one offers its benefits: TFTP: classical netbooting protocol. Offers easy integration with existing netboot environment, including uniform configuration when some machines support pxe and other don't DNS: not only make configuration nice by using domain name instead of IP address but also makes configuration more robust against network changes NFS: this protocol is widely used to access remote server as if it was a local disk. In particular many netbooting environments use nfs for the root filesystem. If GRUB supports nfs such configurations can be simplified because no need of setupping separate service for kernel images SMB: is the easist protocol to setup. It would be beneficial for individual or small organisations. It also allows fast addition of netbooting on the top of existing file sharing architecture. FTP and HTTP: These two are the core protocols of internet. Their support will enable booting over internet. The typical usage case would be installing a linux distribution by simply pointing grub2 to right server Telnet: This protocol would allow a simple remote control of grub2 for headless machines. SSH: the secure version of previous item. Very useful for controlling over unsecure network or from internet Is anybody interested in mentoring this project? -- Regards Vladimir 'phcoder' Serbinenko