LSOF import into base system?
Excerpt from po...@freebsd.org: MVHO - lsof should be in contrib/ and _very_ thoroughly grovelled through. If people feel this is desired, I can easily bmake and import it. From working with Vic Abell, I know he is interested in any problems/issues that we may find in LSOF if we find issues when scrutinizing it. Before discussing this issue, one should ``man 1 fstat''. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: LSOF import into base system?
On Tue, 23 Feb 1999 01:18:42 PST, David O'Brien wrote: If people feel this is desired, I can easily bmake and import it. From working with Vic Abell, I know he is interested in any problems/issues that we may find in LSOF if we find issues when scrutinizing it. Hi David, I think Vic's responsiveness and enthusiasm for team-work means that the software gets excellent attention when it comes to FreeBSD issues. And since the software is under very active development by him, it looks like the following trade-off is in the air on this one: 1) We score rapid FreeBSD-specific tweaking if it's in the base system. 2) We score off up-to-date software if it's in the ports tree. My worry is that we won't really score _that_ much FreeBSD-specific tweaking against the loss of having the version in the base system fall behind Vic's development edge. Or do you reckon lsof will be kept up to date in the base system? Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: LSOF import into base system?
David O'Brien wrote: Excerpt from po...@freebsd.org: MVHO - lsof should be in contrib/ and _very_ thoroughly grovelled through. If people feel this is desired, I can easily bmake and import it. From working with Vic Abell, I know he is interested in any problems/issues that we may find in LSOF if we find issues when scrutinizing it. Before discussing this issue, one should ``man 1 fstat''. Garrett feels happier about fstat as it is Original BSD Code. Any chances of engineering the functional diffs between fstat(1) and lsof(1) back into fstat? If the problem is too great, I'll vote for an import. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: LSOF import into base system?
Garrett feels happier about fstat as it is Original BSD Code. Any chances of engineering the functional diffs between fstat(1) and lsof(1) back into fstat? I guess it is possible, but it would probably take someone like Peter, bde, or Matt Dillon that understands well all of our layerd filesystem ops. If the problem is too great, I'll vote for an import. IMO, either importing LSOF or doing nothing is the most time efficient and productive options. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: LSOF import into base system?
I think Vic's responsiveness and enthusiasm for team-work means that the software gets excellent attention when it comes to FreeBSD issues. We get very high attention by Vic. I've provided him access (or obtained access) to FreeBSD-CURRENT many times when he requested so he could test things. I've never seen attention to this degree before for FreeBSD from a software author. He truly cares that LSOF runs excellent on FreeBSD. My worry is that we won't really score _that_ much FreeBSD-specific tweaking against the loss of having the version in the base system fall behind Vic's development edge. IMHO, the only thing we gain is that one doesn't have to install the port anymore to get LSOF. If we import it into contrib/, I think we will be doing vendor branch imports quite often. A few seemed to feel strongly that it should be imported. Some were worried about it's security (really safe software engr.). Of course the port can still be audited and diffs passed back to Vic. Or do you reckon lsof will be kept up to date in the base system? If nobody else does, I would. -- -- David(obr...@nuxi.com -or- obr...@freebsd.org) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: LSOF import into base system?
According to David E . O'Brien: If people feel this is desired, I can easily bmake and import it. From working with Vic Abell, I know he is interested in any problems/issues that we may find in LSOF if we find issues when scrutinizing it. Well, the way I see it, Vic is already maintaining LSOF for so many platforms that I don't see any real advantage in importing it. As long as he can sync with FreeBSD internal changes (and he can because he has access to such systems -- thanks you for that), we have a a working lsof. That way, Vic doesn't have divergent versions (you don't plan to update contrib/lsof for each change Vic makes to other platforms don't you ?). To be honest, I would not miss fstat(1), even if it is good ol' BSD code, I install lsof everywhere. Putting lsof features into fstat is just IMO a waste of time and code. Now, can we import Postfix instead ? :-) :-) [ducks and runs] -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: LSOF import into base system?
On Tue, 23 Feb 1999, Ollivier Robert wrote: According to David E . O'Brien: If people feel this is desired, I can easily bmake and import it. From working with Vic Abell, I know he is interested in any problems/issues that we may find in LSOF if we find issues when scrutinizing it. Well, the way I see it, Vic is already maintaining LSOF for so many platforms that I don't see any real advantage in importing it. As long as he can sync with FreeBSD internal changes (and he can because he has access to such systems -- thanks you for that), we have a a working lsof. That way, Vic doesn't have divergent versions (you don't plan to update contrib/lsof for each change Vic makes to other platforms don't you ?). To be honest, I would not miss fstat(1), even if it is good ol' BSD code, I install lsof everywhere. Putting lsof features into fstat is just IMO a waste of time and code. AHEM! I use it. Often. I'm certain many others do to. Don't get rid of it, ever! Now, can we import Postfix instead ? :-) :-) [ducks and runs] -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
