Dana H. Myers wrote:
The thought occurred to me, but doing so would effectively fork
the community source (FreeBSD) into a FreeBSD version and an OpenSolaris
version, making it more work to merge changes from/to the original community.
I'm much more inclined to build a set of netgraph shims over STREAMS
to ease porting the FreeBSD stack, if that's where we end up.
IMHO, ideally, community source is integrated into OpenSolaris with
low/no-touch, so that changes can be (mostly) mechanically applied.
This is a golden rule for how I maintain ACPI CA.
I think projects need to think about this from several viewpoints -
the invasiveness of the code, the rate of change of the community
source, and the needs of the project. For the CIFS client [1],
we're not trying to make uptake of changes easy, because we want
to add a filesystem module that's familiar to our engineers and
because we don't expect all that much activity in the community.
Rob T
[1] - The CIFS client is porting the BSD-Darwin "smbfs" sources,
see our wiki for more:
http://cifs.central.sun.com/wiki/index.php/A_native_CIFS_client_for_Solaris
_______________________________________________
opensolaris-discuss mailing list
[email protected]
