cvs commit: src/sys/compat/linux linux_socket.c

[Brooks Davis]

On Thu, Mar 10, 2005 at 05:20:50PM +0000, Paul Richards wrote:
> On Thu, Mar 10, 2005 at 11:55:10AM -0500, Brian Fundakowski Feldman wrote:
> > 
> > How is this even a problem?  The company targets 5.3-RELEASE, period,
> > for all of 5.x.  They do not need to upgrade their build computer to
> > anything past RELENG_5_3 even in the face of security issues.
> 
> That really irritating bug that causes their development tools to
> crash is fixed in 5.5. Clearly they'll want to run with that later
> version.

Then they should tell their customers that they only support 5.5 or they
should routinly test on 5.3 to make sure that keeps working.  For that
matter, in the case we are discussing, as long as they don't use the new
flags they would not have any problems and if they failed to test on the
old version they claimed to support that's their problem.

That said, there are things that could be done to make flag-like APIs
more robust like checking that all passed flags are valid and returning
an appropriate error (ENOSUP, etc) if they are not so developers could
write applications that use new flags when available and back off if
not.  Someone who is intrested in these issues would certaintly be doing
us a service by hunting down and fixing these kinds of things.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-src/attachments/20050310/521ae5e0/attachment.bin