Re: Preliminary restructuring layout (was Re: sys/ tree re-structuring proposal)

["Galen Sampson" <galen_sampson@xxxxxxxxx>]

There has been talk on this list about the import of a new snapshot of the
KAME network stack.  KAME produces snapshots for the freebsd 4.x branch
weekly.  A KAME update is also on the TODO list for freebsd 5.2 (so
dragonfly isn't the only project considering KAME updates).  Restructuring
the source tree might hinder the efforts of the people trying to import a
KAME snapshot if things get too different.

regards,
Galen

"Julian Elischer" <julian@xxxxxxxxxxxx> wrote in message
news:Pine.BSF.4.21.0308061450200.4704-100000@xxxxxxxxxxxxxxxxxxxxxxxx
>
>
> On Wed, 6 Aug 2003, Matthew Dillon wrote:
>
> > :...
> > :> ./kern
> > :> ./libkern
> > :> ./libkern/alpha
> > :> ./net
> > :> ./netgraph
> > :
> > :net/proto/inet
> > :net/proto/inet6
> >
> >     How about:
> >
> >     netproto/ip4 (move ip_* from netinet)
> >     netproto/tcp4 (move tcp_* from netinet)
> >     netproto/udp4 (move tcp_* from netinet)
> >     netproto/igmp4 (move igmp* from netinet)
> >     netproto/ip6 ...
> >     netproto/tcp6 ...
> >     netproto/udp6 ...
> >     netproto/esp6 ...
> >     netproto/nd6 ...
> >     netproto/ipsec6
>
>
>
>
> I might add I think splitting it differently give a hint to develpers
> as to where to put NEW things..
>
> e.g.
> netproto/inet/divert
> netproto/inet/mynewprotocol
> netproto/inet/ipfw
>
> >
> >     I think this fits well with everything else in netproto.  I
> >     should just do it all now rather then split the major
> >     surgery up into multiple stages.
> >
> > -Matt
> > Matthew Dillon
> > <dillon@xxxxxxxxxxxxx>
> >
>