Matt Dillon’s schedule

This week Matt Dillon is doing:

  • lwkt_token and IPI code optimization
  • GCC 3.x (just for support of the next item)
  • 64 bit AMD64 support
… and networking code with Jeff Hsu.

For those of you late to the party and wondering why his work schedule is spotlighted, Matt Dillon is the originator of the DragonFly project, and is doing much heavy lifting.

CARP vs. VRRP

Jeroen Ruigrok supplied these links about patent issues with Cisco’s VRRP during a thread about importing OpenBSD’s CARP as part of pf.

http://www.in-addr.de/pipermail/lvs-users/2001-November/004135.html
http://kerneltrap.org/node/view/477/1567
http://kerneltrap.org/comment/reply/477/1567
http://marc.theaimsgroup.com/?l=openbsd-misc&m=102883972229241&w=2
https://www1.ietf.org/mail-archive/working-groups/vrrp/current/msg00318.html

Bugzilla brought in

Jeroen Ruigrok is setting up Bugzilla for tracking bugs/requests for DragonFly. As part of the process, there’s some 6,000 (!) items brought over from FreeBSD-4. No link yet…

Things to come

In a thread about booting media, Matt Dillon noted he was going to:

  • Look at Jeff Hsu’s TCP thread code
  • implement variant symlinks
  • start VFS messaging and environments

VFS will make a number of other things – especially a new port system – possible.

Flames bad, info good

On the freebsd-hackers mailing list, a slight flamewar erupted over discussion of checkpointing code from DragonFly. Amidst the dumbness that normally ensues in a flamewar, there’s some interesting descriptions on what work has been done/will be done on DragonFly. Check out the archive, mostly in the “FreeBSD mail list etiquette” thread. Matt Dillon’s posts here, here, and here are all info-packed.