:Also, fixing the ipfw2 abi is probably a good item to put on the list
:for getting 5.x to 5-STABLE. Please don't waste time with band-aids
:that will make people forget that ipfw2 needs attention.
:
:Scott
This is a reasonable line of argument but my opinion is that it
hasn't been fixed for a long time now and unless someone decides
they really want to tackle the issue soon it isn't going to be
fixed for a long time to come, and we shouldn't continue to create
a major hassle for developers and sysads that hit up against
the issue.
I mean, hey, if someone asked me to rename the command from
'ipfw unbreak' to 'ipfw somelonggobblygookthatyouhavetocutandpaste'
I'm willing to do that too :-) But we need either the API fixed or
this hack and, right now, the only person willing to do anything is
me and my buddy Hack. If someone stood up and said "I will take on
fixing the API but it will take a month" then that's fine with me,
I would not feel that I would have to commit this now. But so far
nobody has stood up and said that.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
