On Fri, Dec 08, 2000 at 12:07:49AM -0700, Chad R. Larson wrote: > I thought the space staked out by the *BSD gang was approximately > this: > NetBSD - the least amount of platform-specific code possible; run > on most anything > OpenBSD - pro-active security, bullet-proof from attacks > FreeBSD - best performing on the Intel PC platform s/the Intel PC/server/ The Alpha has very good I/O bandwidth and 64-bit address space. Thus it fits our niche. You also mentioned Sparc, but really should have said sparc64(pci based). hopefully embeded soon too. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- PCIOCGETCONF/PCIOCREAD requires write permission? Lyndon Nerenberg
- Re: PCIOCGETCONF/PCIOCREAD requires write permiss... Kenneth D. Merry
- Re: PCIOCGETCONF/PCIOCREAD requires write per... Andrew Gallatin
- Re: PCIOCGETCONF/PCIOCREAD requires write... Matthew Jacob
- Re: PCIOCGETCONF/PCIOCREAD requires w... Chad R. Larson
- Re: PCIOCGETCONF/PCIOCREAD requi... Warner Losh
- Re: PCIOCGETCONF/PCIOCREAD requi... Mike Silbersack
- Re: Re: PCIOCGETCONF/PCIOCRE... Stefan Esser
- Re: PCIOCGETCONF/PCIOCREAD requi... David O'Brien
- Re: PCIOCGETCONF/PCIOCREAD r... Daniel C. Sobral
- Re: PCIOCGETCONF/PCIOCRE... Wes Peters
- Re: PCIOCGETCONF/PCIOCRE... Dag-Erling Smorgrav
- Re: PCIOCGETCONF/PCIOCRE... Wes Peters
- Re: PCIOCGETCONF/PCIOCREAD r... Warner Losh
- Re: PCIOCGETCONF/PCIOCRE... Daniel C. Sobral
- Re: PCIOCGETCONF/PCIOCRE... Wes Peters
- Re: PCIOCGETCONF/PCIOCREAD requires write... Peter Wemm
- Re: PCIOCGETCONF/PCIOCREAD requires write per... Lyndon Nerenberg
- Re: PCIOCGETCONF/PCIOCREAD requires write... Kenneth D. Merry