Re: Any objections/comments on axing out old ATA stack?

2013-03-30 Thread Peter Wemm
On Sat, Mar 30, 2013 at 4:29 PM, Matthias Andree wrote: > Am 27.03.2013 22:22, schrieb Alexander Motin: >> Hi. >> >> Since FreeBSD 9.0 we are successfully running on the new CAM-based ATA >> stack, using only some controller drivers of old ata(4) by having >> `options ATA_CAM` enabled in all kerne

Re: Question on building from sources.

2013-03-30 Thread Erich Dollansky
Hi, On Sat, 30 Mar 2013 19:05:47 -0400 Super Bisquit wrote: > Okay. I already have 10.0 on the machine from a year ago. What I have this sounds a bit old. > come up against is CLANG_IS_CC ="no" when trying to build run(4). > What is the current state of clang as cc compiler on ppc32? <-- This

Re: Question on building from sources.

2013-03-30 Thread Super Bisquit
That was the error that came up, apologies for not specifying such. I'm not trying to disable clang but am trying to build the system using what is there. This is about the time I need a powerpc laptop or a connection.. On Sat, Mar 30, 2013 at 7:09 PM, Glen Barber wrote: > On Sat, Mar 30,

Re: Any objections/comments on axing out old ATA stack?

2013-03-30 Thread Matthias Andree
Am 27.03.2013 22:22, schrieb Alexander Motin: > Hi. > > Since FreeBSD 9.0 we are successfully running on the new CAM-based ATA > stack, using only some controller drivers of old ata(4) by having > `options ATA_CAM` enabled in all kernels by default. I have a wish to > drop non-ATA_CAM ata(4) code,

Re: Question on building from sources.

2013-03-30 Thread Glen Barber
On Sat, Mar 30, 2013 at 07:05:47PM -0400, Super Bisquit wrote: > Okay. I already have 10.0 on the machine from a year ago. What I have come > up against is CLANG_IS_CC ="no" when trying to build run(4). If you are trying to disable clang, you want to use: WITHOUT_CLANG_IS_CC=yes > What is th

Re: Question on building from sources.

2013-03-30 Thread Super Bisquit
Okay. I already have 10.0 on the machine from a year ago. What I have come up against is CLANG_IS_CC ="no" when trying to build run(4). What is the current state of clang as cc compiler on ppc32? <-- This needs to be fixed first. Thanks for the replies and sorry for any noise. On Fri, Mar 29, 20

Re: ports/177488: qemu-1.4

2013-03-30 Thread Oliver Pinter
and one more On 3/30/13, Oliver Pinter wrote: > yes this is git head, sorry > > On 3/30/13, Juergen Lock wrote: >> On Sat, Mar 30, 2013 at 02:36:35AM +0100, Oliver Pinter wrote: >>>[..] >>> >>> disable some unneeded function, and make qemu 1.4 compilable on FreeBSD >>> 9.1 >>> >> >> I think you

Re: ports/177488: qemu-1.4

2013-03-30 Thread Oliver Pinter
yes this is git head, sorry On 3/30/13, Juergen Lock wrote: > On Sat, Mar 30, 2013 at 02:36:35AM +0100, Oliver Pinter wrote: >>[..] >> >> disable some unneeded function, and make qemu 1.4 compilable on FreeBSD >> 9.1 >> > > I think you are building qemu git head as the hexdump function at least >

Re: big change to devfs rules path matching

2013-03-30 Thread Jaakko Heinonen
On 2013-03-28, Andriy Gapon wrote: > > Would like to ask for opinions on this topic... > > Please read this PR for context: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/122838 > > Especially Jaakko's insightful description of the problem. > > So I would like to commit the following patch so

Re: ports/177488: qemu-1.4

2013-03-30 Thread Juergen Lock
On Sat, Mar 30, 2013 at 02:36:35AM +0100, Oliver Pinter wrote: >[..] > > disable some unneeded function, and make qemu 1.4 compilable on FreeBSD 9.1 > I think you are building qemu git head as the hexdump function at least isn't in 1.4.0? Anyway I have meanwhile updated the qemu-devel port to 1

Re: [RFC] vfs.read_min proposal

2013-03-30 Thread Scott Long
On Mar 29, 2013, at 2:58 PM, Konstantin Belousov wrote: >> > I think this is definitely a feature that should be set by a flag to > either file descriptor used for aio_read, or aio_read call itself. > Adding a flag to aio_read() might be cumbersome from the ABI perspective. > Fine if you thin