Hi,
On Thu, Jul 12, 2012 at 1:20 AM, Warner Losh wrote:
> I'm sorry you feel that way.
>
> Honestly, though, I think you'll be more pissed when you find out that the
> N:1 interface that you want is being done in the wrong domain. But I've been
> wrong before and look forward to seeing your re
TB --- 2012-07-12 06:10:00 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-07-12 06:10:00 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
Hi,
On behalf of the pkgng team I'm really pleased to announce pkg 1.0 RC1 (aka
pkgng)
Only bug fixes will be accepted in the RC phase.
What is pkg
---
pkg is a new package manager for FreeBSD. It is designed as a replacement for
the pkg_* tools, and as a full featured binary package ma
On Thu, Jul 12, 2012 at 12:01 PM, Baptiste Daroussin wrote:
> Third party tools
> -
>
> Tools supporting natively pkgng
> - ports-mgmt/portupgrade-devel (soon the main portupgrade will support)
> - ports-mgmt/pkg_cutleaves
> - ports-mgmt/poudriere
> - ports-mgmt/portdowngra
On Thursday, July 12, 2012 3:01:36 am Arnaud Lacombe wrote:
> Hi,
>
> On Thu, Jul 12, 2012 at 1:20 AM, Warner Losh wrote:
> > I'm sorry you feel that way.
> >
> > Honestly, though, I think you'll be more pissed when you find out that the
N:1 interface that you want is being done in the wrong dom
On Jul 12, 2012, at 6:01 AM, John Baldwin wrote:
> New-bus is certainly not the only way to organize a device hierarchy and is
> not perfect, but in your case I suggest you tone down your language until you
> have enough information to develop an informed opinion.
It is also not the only way to
I have a need to allocate static DMA memory via bus_dmamem_alloc() that is
also WC (for a PCI-e device so it can use "nosnoop" transactions). This is
similar to what the nvidia driver needs, but in my case it is much cleaner to
allocate the memory via bus dma since the existing code I am extend
On Thu, 2012-07-12 at 10:40 -0400, John Baldwin wrote:
> I have a need to allocate static DMA memory via bus_dmamem_alloc() that is
> also WC (for a PCI-e device so it can use "nosnoop" transactions). This is
> similar to what the nvidia driver needs, but in my case it is much cleaner to
> allo
On Thursday, July 12, 2012 11:02:07 am Ian Lepore wrote:
> On Thu, 2012-07-12 at 10:40 -0400, John Baldwin wrote:
> > I have a need to allocate static DMA memory via bus_dmamem_alloc() that is
> > also WC (for a PCI-e device so it can use "nosnoop" transactions). This is
> > similar to what the
Hi, all
I have created a netgraph node which performs a IPv6-to-IPv6 Network
Prefix Translation(RFC6296).
It works with ipfw(ng_ipfw). a sample configuration is follows.
1 setup netgraph
ngctl mkpeer ipfw: nptv6 1000 inbound
ngctl name ipfw:1000 nptv6
ngctl connect ipfw: nptv6: 2000
On Thu, 12 Jul 2012, Ian Lepore wrote:
To be clear, I'm not objecting to your proposed changes, I'm more just
musing that similar problems exist in non-x86 architectures and maybe an MI
solution is possible (or at least the groundwork could be laid)?
I was likewise going to comment that ther
- Original Message -
> From: John Baldwin
> To: curr...@freebsd.org
> Cc: sco...@freebsd.org; Peter Jeremy
> Sent: Thursday, July 12, 2012 7:40 AM
> Subject: Adding support for WC (write-combining) memory to bus_dma
>
> I have a need to allocate static DMA memory via bus_dmamem_alloc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenSSL 1.0.1c will be merged to head today. There will be several
important changes to note.
- - Several crypto/engine modules will be added or enabled by default to
closely match OpenSSL default, e.g., Camellia (crypto), SEED (crypto),
CHIL (engine
On Thursday, July 12, 2012 12:37:13 pm Scott Long wrote:
>
> - Original Message -
> > From: John Baldwin
> > To: curr...@freebsd.org
> > Cc: sco...@freebsd.org; Peter Jeremy
> > Sent: Thursday, July 12, 2012 7:40 AM
> > Subject: Adding support for WC (write-combining) memory to bus_dma
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-12 14:04:58 -0400, Jung-uk Kim wrote:
> - Several crypto/engine modules will be added or enabled by default
> to closely match OpenSSL default, e.g., Camellia (crypto), SEED
> (crypto), CHIL (engine), GOST (engine), etc.
Actually, CHIL is a
I do not mean this e-mail to be in any way critical. I was told after
the new OPTIONS framework discussion that I should have asked questions
before the change, so I'm asking these questions now; in a genuine
attempt to get information.
On 07/12/2012 03:01 AM, Baptiste Daroussin wrote:
In the tim
In article <20120712100110.ga34...@ithaqua.etoilebsd.net>,
b...@freebsd.org writes:
> - puppet support: (https://github.com/xaque208/puppet-pkgng)
I've actually already written one of these; it may be good to merge.
Would whoever is working on this please raise your hand?
-GAWollman
--
Garrett
TB --- 2012-07-12 20:13:29 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-07-12 20:13:29 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-07-12 20:28:59 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-07-12 20:28:59 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
TB --- 2012-07-12 20:43:02 - tinderbox 2.9 running on freebsd-current.sentex.ca
TB --- 2012-07-12 20:43:02 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2012-
On Thu, Jul 12, 2012 at 11:48 AM, Doug Barton wrote:
> 1. What are the goals for pkg?
> 2. Why can't the existing tools fulfill those goals?
> 3. How does pkg fulfill them?
>
>
Hi,
You might want to view Baptiste's pkgng presentation at BSDCan:
http://www.youtube.com/watch?v=4Hxq7AHZ27I
For me
On 07/12/2012 02:11 PM, Craig Rodrigues wrote:
> You might want to view Baptiste's pkgng presentation at BSDCan:
>
> http://www.youtube.com/watch?v=4Hxq7AHZ27I
Sure, the next time I have an hour to spare.
I don't think what I'm asking for is unreasonable. One could even
conclude that answering t
On Thu, Jul 12, 2012 at 11:48:41AM -0700, Doug Barton wrote:
> I do not mean this e-mail to be in any way critical. I was told after
> the new OPTIONS framework discussion that I should have asked questions
> before the change, so I'm asking these questions now; in a genuine
> attempt to get inform
On 07/12/2012 03:02 PM, Baptiste Daroussin wrote:
> On Thu, Jul 12, 2012 at 11:48:41AM -0700, Doug Barton wrote:
>> I do not mean this e-mail to be in any way critical. I was told after
>> the new OPTIONS framework discussion that I should have asked questions
>> before the change, so I'm asking th
2012/7/4 Attilio Rao :
> 2012/6/29 Attilio Rao :
>> As already published several times, according to the following plan:
>> http://wiki.freebsd.org/NONMPSAFE_DEORBIT_VFS
>>
>
> I still haven't heard from Vivien or Edward, anyway as NTFS is
> basically only used RO these days (also the mount_ntfs co
On 2012-Jul-12 10:40:27 -0400, John Baldwin wrote:
>contigmalloc(). In fact, even better is to call kmem_alloc_contig() directly
>rather than using contigmalloc().
...
>Peter, this is somewhat orthognal (but related) to your bus_dma patch which is
>what prompted me to post this.
Overall, the cha
When tracking down a panic exposed by INVARIANTS, I tried setting
DEBUG_MEMGUARD, so I could find the culprit that's trashing freed
memory. However, this causes a panic at bootup. It shows up right
after the first WARNING: WITNESS message, with the following:
panic: kmem_suballoc: bad sta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-07-12 14:04:58 -0400, Jung-uk Kim wrote:
> OpenSSL 1.0.1c will be merged to head today. There will be
> several important changes to note.
>
> - Several crypto/engine modules will be added or enabled by default
> to closely match OpenSSL defa
On Thu, Jul 12, 2012 at 4:43 PM, Justin Hibbits wrote:
> When tracking down a panic exposed by INVARIANTS, I tried setting
> DEBUG_MEMGUARD, so I could find the culprit that's trashing freed memory.
> However, this causes a panic at bootup. It shows up right after the first
> WARNING: WITNESS mes
On Jul 12, 2012, at 9:11 PM, m...@freebsd.org wrote:
On Thu, Jul 12, 2012 at 4:43 PM, Justin Hibbits
wrote:
When tracking down a panic exposed by INVARIANTS, I tried setting
DEBUG_MEMGUARD, so I could find the culprit that's trashing freed
memory.
However, this causes a panic at bootup. It
On Thu, Jul 12, 2012 at 6:33 PM, Justin Hibbits wrote:
> On Jul 12, 2012, at 9:11 PM, m...@freebsd.org wrote:
>
>> On Thu, Jul 12, 2012 at 4:43 PM, Justin Hibbits
>> wrote:
>>>
>>> When tracking down a panic exposed by INVARIANTS, I tried setting
>>> DEBUG_MEMGUARD, so I could find the culprit th
31 matches
Mail list logo