Re: [Etherboot-developers] [COMMIT] Multicast & more.
Brought to you by:
marty_connor,
stefanhajnoczi
|
From: <ebi...@ln...> - 2002-06-14 19:16:29
|
Anselm Martin Hoffmeister <an...@ho...> writes: > On Wednesday, 12. June 2002 05:02, Eric W. Biederman wrote: > > I have committed my first first round of changes to be a productive > > bootloader for LinuxBIOS, into the etherboot-5.1 tree. I believe I > > have only included the good bits but I have only tested the merge with > > my tree to see if it compiles. Holler if it breaks, something for you/ > > Image_menu cannot compile, complains about something double defined.... Just > saw it, I will hunt for mknbi-menu instead :-) Oops. > > Included. > > - Added multicast support > > which I steal code from. Thanks so far. Note the memory allocate should be done more cleanly. I just hacked together a working solution. > > - Added a pc floppy driver > > which seems to be commented out ? Right. I didn't have the parsing code in a sane form. > > - added an experimental multicast download protocol > > Is there a server for it? Yes. But at the moment I can't release it. > I used the chance of the moment and changed the code to accept the following > URIs: > > "file:" (0,1 or 3 times "/") "disk/" (devicenumber, 0..3 allowed only) > to boot the MBR of a harddrive > > append "/" (partitionnumber, 0..8 allowed, 0=MBR) to explicitely boot a > partition. Hmm. 0=MBR I don't like... If you can just avoid giving a partition number to indicate the MBR it is better. > "file:" (0,1 or 3 times "/") "floppy/" (devicenumber, 0..3 allowed only) > to boot a floppy device. > > In plain language, you can enter into your dhcp "filename" parameter > > file:disk/0 > file:/disk/0/0 > file:///disk/0/0 Sounds like good work I will inspect it later. > I would like to > have the URI scheme "tftm:" (Trivial File Transfer protocol, Multicast mode) > officially assigned. I would like to use an ``x-'' prefix until the appropriate IETF commitee assigns an official prefix. Experimental protocols you are allowed to change as needed, the rest are a little more fixed. > While improving URI support, it would not be too much a hassle to implement > the ability to have both TFTP and NFS at hand, so filenames beginning with > one of the following should be treated "reserved" from now on: > (only the lowercase needs to be reserved for *n*x filenames, but written > uppercase to increase readability): Right. I was thinking along similiar lines. > FILE: > TFTP: > NFS: > X-SLAM: probably for the moment only > SLAM: probably in the near future, when it's no longer experimental > TFTM: > > Anselm > > Attachment: mainc-fileurl.diff. To be applied to main.c to have file: URI > support. A good step forward. Eric |