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
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
