On Sat, Oct 21, 2000 at 04:24:54PM -0400, Dan Papasian wrote:
> Right, except Linux isn't BSD, and vice versa- there's no way > to just plug-and-play the kernels.
Only BSD kernels, and not plug-n-play, but rebuild the whole package tree also. Suppose someone would want to run Debian/NetBSD on the whole range of platforms the kernel runs at :)
> But for things like my SBLive, it's FreeBSD or bust. Until someone > ports newpcm to NetBSD... (gears turning in head)
_That_'s what I was talking about also -- SB Live. ;) -- Regards, Wartan.
so, is it Freebsd with better peripheral support etc... with SMP (with BSD/OS also contributing to fbsd's strengths soon here..., they have better SMP support i think, will merge the codebase by 4.2 maybe.) or netbsd with multitude of platform support...
With combined BSD packaging systems, if we can assume that a lot of efforts in
that direction will get reduced, netbsd can focus on adding support for those
devices using existing code from freebsd anyway. But then even freebsd with it's increased commercial clout with BSDi can support other platforms.
I would like debian's distribution strengths combined with netbsd's campaign to better organisation of the code in kernel.
Both organisations also don't care about release dates :) , very stringant to mission statements, and are probably most non-commercial in nature, and will most likely remain so.
What will be the profile of the users, will they be also using it as a workstation
and will then be needing support for sound cards etc, or server level.
And will SMP support matter ?
And if _openpackages_ clicks soon, who can quickly get the currently lacking functionality, I think netbsd !
So my vote to netbsd kernel.
/prasad gadgil (se-mumbai)
"What you do when you don't have to, determines what you will be when you can no longer help it." -Rudyard Kipling
