Re: [Etherboot-developers] [RFC] Multicast reception....
Brought to you by:
marty_connor,
stefanhajnoczi
|
From: <ebi...@ln...> - 2002-06-11 18:37:00
|
Anselm Martin Hoffmeister <an...@ho...> writes: > > Right the code is already doing this correct. But thanks for the catch. > > You wrote about putting public your code. Did you? Where can I get it, is the > CVS always the uptodate source (I never worked with CVS before)? I'm getting there. I'm so busy working on it that I haen't had a free moment to do that yet. Hopefully I can get that done later today. > As now minor changes to some (sooner or later most/all) hardware drivers > arise (though only triggered when MULTICAST is enabled) perhaps 5.0.7-rc > should stay rc for some days, so that these changes can make their way to the > next release. The opposite argumentation would be to release stable and > old-fashioned, giving the multicast out to public retarded. That's not what I > (my two cents, you know, thanks to Peter Billson for explaning me that > phrase) like, the more public the better the testing. We don't force anyone > to enable that configuration switch. There are pieces that could make 5.0.7-rc but I have enough changes in other parts of the code with hard driver booting etc, that I'd rather push it to 5.0.8. > To Eric: > What about the standard protocol (or less-standard?) you want to have for > multicast? Do you have documentation at hand? Yes I have one but I'm not going to fix anything in stone until I get some successful large scale testing. My biggest hold up is someone let the test environment at work get into a sorry state. And I have been rebuilding it. > Else I would like to start > adding tftp-mcast support as my quickly hacked daemon for that protocol at > least runs, on low-load-testing with two clients stably. Perhaps if ready I > could have a mass-test (ok, 15 clients is not much, but better that nothing) > the after-next weekend at my "private testing laboratory", until then I > should have made a release out of it, announce will follow. But of course, if > you have a better protocol at hand, please let me know. Given that I will definentily see what I can push into the 5.1 tree in cvs. > An*getting CVS to work right now*selm Good luck on that. CVS works as a pretty good distribution mechanism. If you prefer patches I can go that route to. Eric |