Re: [PATCH] switching to if_xname

On Fri, Nov 01, 2002 at 01:15:45PM -0800, Nate Lawson wrote: > On Fri, 1 Nov 2002, Brooks Davis wrote: > > The bigger deal is breaking > > the network interface API and ABI which in turn breaks a few user land > > programs that use libkvm ("netstat -r" for exmaple). That's why this is > > a .0 f

Re: [PATCH] switching to if_xname

On Fri, 1 Nov 2002, Brooks Davis wrote: > The bigger deal is breaking > the network interface API and ABI which in turn breaks a few user land > programs that use libkvm ("netstat -r" for exmaple). That's why this is > a .0 feature. > > Thanks, > Brooks Please check the libdnet port and possib

Subscribe

Please subscribe me to the mailing list! Thanks! Jeffrey A. Ward EDS Information Analyst

Re: Socket so_linger setting

Matthew Dillon wrote: I think your patch is fine as is, Mike! Good find! Even though so_linger cannot be negative, it is often convenient to use a signed integer to store the value to avoid unexpected arithmatic results when mixing with signed operations. My quick perusal does

Re: [PATCH] switching to if_xname

On Fri, Nov 01, 2002 at 12:07:05PM -0800, Nate Lawson wrote: > Couple comments. > > * You interchangeably use strlcpy and snprintf(... "%s", ...) and even > strncpy/strcpy(!). You probably want to go with just strlcpy. I forgot to sweep for those again. I'll do another pass shortly. > * There

Re: Socket so_linger setting

I think your patch is fine as is, Mike! Good find! Even though so_linger cannot be negative, it is often convenient to use a signed integer to store the value to avoid unexpected arithmatic results when mixing with signed operations. My quick perusal does not show any cases

Re: [PATCH] switching to if_xname

You might also try -net or -arch. On Fri, 1 Nov 2002, Brooks Davis wrote: > I'm trying to get some review for the following patch. I realize it's > quite large, but most it is is trivial. The ipfw code is the only thing > that worries me significantly. I have promised Kris that I will fix > por

[brooks@one-eyed-alien.net: [PATCH] switching to if_xname]

I'm trying to get some review for the following patch. I realize it's quite large, but most it is is trivial. The ipfw code is the only thing that worries me significantly. I have promised Kris that I will fix ports that break with this change so you don't need to worry about that issue. I'd li

Re: Request for submissions: FreeBSD Bi-Monthly Development Status Report Sept-Oct 2002

On Fri, 1 Nov 2002, Robert Watson wrote: > All submissions are due by October 10, 2002. Needless to say, the deadline is actually November 10, 2002. Rather than thinking of this as an "off the hook" scenario, think of it as an extra month to submit the status report, starting about a month ago :

Request for submissions: FreeBSD Bi-Monthly Development Status Report Sept-Oct 2002

This is a solicitation for submissions for the September 2002 - October 2002 FreeBSD Bi-Monthly Development Status Report. All submissions are due by October 10, 2002. Submissions should be made by filling out the template found at: http://www.FreeBSD.org/news/status/report-sample.xml Sub

Seek and Find KGKQSUUQSI

READY TO KNOW? REALLY? CONFIDENTIAL! The SOFTWARE They Want BANNED In all 50 STATES. Why??? Because these secrets were never intended to reach your eyes... Get the facts on anyone Locate Missing Persons, find Lost Relatives, obtain Addresses and Phone Numbers of old school friends, even

Socket so_linger setting

During some parameter limit checking work, I ran into what I believe to be an error in FreeBSD. (Albeit unlikely to be hit) A setsockopt of the SO_LINGER field will cause strange results if the value is set above 32767. This is due to the fact that in struct socket, the so_linger field is a sign