--nextPart1198247.7vFS6o7d4u
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Friday, 4. February 2005 14:05, Joerg Sonnenberger wrote:
> > A word from "the masses": this is completely justified -- developer's --
> > point of view. On the other hand: cleaning of the code per se gives
> > plenty of opportunities to break what's working. Like, reducing vinum
> > functionality (or breaking it), or having ipfw removed. Doesn't look
> > good.
> Concerning the removal of ipfw1, it won't happen soon. Once ipfw2
> fully works, it can die. Another requirement or ipfw(2) is to use
> the normal firewall API, since it currently hooks into way too
> much places directly. This means an improvement in usability too,
> because ipfw would be fully dynamically loadable.
i'm working on that (=3D ipfw into pfil)
cheers
simon
=2D-=20
/"\
\ /
\ ASCII Ribbon Campaign
/ \ Against HTML Mail and News
--nextPart1198247.7vFS6o7d4u
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)
iD8DBQBCA3mQr5S+dk6z85oRAuojAKDhJiZ+w6CrWBHzJB3WYEbpMZy9UgCgzgLn
WP4kUKBRYnyGUDLgPvE8RYM=
=dwwr
-----END PGP SIGNATURE-----
--nextPart1198247.7vFS6o7d4u--