New name to reflect new functionality (was RE: DHCP code in 2.0.4+)

[Tim Sylvester]

How about FreeRADIUS and FreeDHCP?


            The "FreeXXXXX" Project
 ---------------------------------------------
|            |           |           |        |
| FreeRADIUS | FreeDHCP  | FreeTBD   |   ...  |
|   Server   |  Server   |  Server   |        |
 ---------------------------------------------
|                                             |
|              "Magic Server Code"            |
|                                             |
 ---------------------------------------------

FreeRADIUS migrates to the "FreeXXXXX" Project which includes the "Magic
Server Code", the FreeRADIUS Server, FreeDHCP Server, etc. There would be
distributions for FreeRADIUS, FreeDHCP and one that included everything. 

Tim



> -----Original Message-----
> From: freeradius-users-
> bounces+tim.sylvester=networkradius.com at lists.freeradius.org
> [mailto:freeradius-users-
> bounces+tim.sylvester=networkradius.com at lists.freeradius.org] On Behalf
> Of Alan DeKok
> Sent: Thursday, June 11, 2009 1:09 AM
> To: FreeRadius users mailing list
> Subject: Re: New name to reflect new functionality (was RE: DHCP code
> in 2.0.4+)
> 
> Martin Lorentz wrote:
> > FreeRadius should always be called FreeRadius. It's almost a brand
> name,
> > which is very well known, and has an excellent reputation.
> 
>   I agree.
> 
> > How could this be organized, in the source tree or elsewhere? A new
> > server core maybe called Flex-"Something" without any knowledge of
> > RADIUS, DHCP or the like? An "add-on" package called FreeRadius,
> another
> > called FlexDHCP? Kind of confusing, there must be a better way.
> 
>   I think the best way is to have a new project that contains
> additional
> documentation on the web explaining how to configure the additional
> protocols.  We could also have a git tree based on FreeRADIUS, but with
> the RADIUS parts stripped out, for example.
> 
>   I've started some of that work in the git "master" branch.  The
> various "listen" handlers are now in plug-in modules.  The server core
> is gradually having all of the RADIUS portions removed.  If I can
> figure
> out how to move the RADIUS state machine into the modules, then the
> core
> would be *completely* protocol agnostic.
> 
>   In the long term, migrating the FreeRADIUS code base into something
> more flexible is a good idea.
> 
>   Alan DeKok.
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html