All of lore.kernel.org
 help / color / mirror / Atom feed
From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Summer of code proposition: TCP/IP Anybody want to mentor?
Date: Tue, 03 Mar 2009 22:42:06 +0100	[thread overview]
Message-ID: <49ADA42E.4020300@gmail.com> (raw)

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



                 reply	other threads:[~2009-03-03 21:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49ADA42E.4020300@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.