In message <[EMAIL PROTECTED]> "Chad R. Larson" writes: : Has the core group ever weighed in on this? Does the BSDi merger : change any of the FreeBSD focus with regard to other hardware : architectures? Core, per se, hasn't. There's a very strong history in this project that if a port is supported, breaking it is unacceptible. FreeBSD has moved beyond intel only, and we need to deal with that, even if there are things we can get away with on i386 and can't on other platforms. Warner 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