[haiku-gsoc] Re: [HCD] ICMP errors handling & propagation project
- From: "Yin Qiu" <allenchue@xxxxxxxxx>
- To: haiku-gsoc@xxxxxxxxxxxxx
- Date: Fri, 27 Jun 2008 17:27:36 +0800
Ignore my previous problem. It has been solved after I installed the texinfo
package. My status is already late, and I'm catching up.
On Fri, Jun 27, 2008 at 5:15 PM, 仇寅 <qiuyin04@xxxxxxxxxxxxxxxxxxx> wrote:
> Hi,
>
> Thanks to Axel for your links. I think I can learn something from Alan's
> original proposal.
>
> Currently I'm reading RFC 792, RFC 1122#section 3.2.2 and some other
> supplementary materials. The haiku source code will also be my primary
> focus.
>
> For the development environment, I have checked out the haiku code and the
> build tools on Linux box. Jam utility has been built, but something went
> wrong when I built the cross compiler. The following is the stderr output:
>
> configure: WARNING:
> *** Makeinfo is missing. Info documentation will not be built.
> WARNING: `makeinfo' is missing on your system. You should only need it if
> you modified a `.texi' or `.texinfo' file, or any other file
> indirectly affecting the aspect of the manual. The spurious
> call might also be the consequence of using a buggy `make' (AIX,
> DU, IRIX). You might want to install the `Texinfo' package or
> the `GNU make' package. Grab either from any GNU archive site.
> make[3]: ***
> [/home/qiuyin/develop/haiku/buildtools/legacy/binutils/bfd/doc/bfd.info]
> Error 1
> make[2]: *** [info-recursive] Error 1
> make[1]: *** [all-bfd] Error 2
> make: *** [all] Error 2
>
> Any comments on this? Thanks.
>
>
> On Thu, Jun 26, 2008 at 4:46 PM, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
> wrote:
>
>> <philippe.houdoin@xxxxxxx> wrote:
>> > Last year, IIRC, Hugo Santos, a GSoC 2007 student, introduced two new
>> > hooks
>> > to net_protocol API: error() and error_reply().
>>
>> Actually that was me -- and I mostly copied it from the BONE headers
>> without giving it too much thought :-)
>>
>> > My understanding on the way these hooks should be used is that one:
>> > - The error() hook is supposed to be called when an error is
>> > propagated toward
>> > *upper* protocols, like on host unreachable ICMP message reception,
>> > which should
>> > be propagate up to UDP, TCP.
>> > - The error_reply() hook is supposed to be called by a protocol to
>> > propagated to *lower*
>> > protocols an error, like... source quench notification from TCP ?
>>
>> Exactly. We could rename error() to error_received() to make this a bit
>> clearer.
>>
>> > A good starting point would be code in trunk/src/add-ons/kernel/
>> > network/protocols/icmp/,
>> > to see what level of ICMP feature is already there (minimal only).
>>
>> Currently, it's mostly the echo feature.
>> Also of interest would be the following discussion:
>> //www.freelists.org/archives/haiku-development/03-2008/msg00462.html
>>
>> This was the initial proposal by Alan Alvarez who we lost to KDE.
>> Also of interest might be the basic overview over the network stack:
>> http://www.haiku-os.org/documents/dev/haiku_network_stack_architecture
>>
>> Bye,
>> Axel.
>>
>>
>>
>
>
> --
> Yin Qiu
> Nanjing University, China
> -------------------------------------------
>
--
Yin Qiu
Nanjing University, China
-------------------------------------------
Other related posts:
