Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-06 Thread Erwin Lansing
On Thu, Aug 06, 2015 at 05:19:54PM -0700, Xin Li wrote: > Hi, > > Currently the default portsnap.conf would generate INDEX-11, INDEX-10 > and INDEX-9. The INDEX file is only used for searching ports, and only > one (INDEX-${OSREL:R}) file is actually used. > This is default behaviour for other

Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-06 Thread Xin Li
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 8/6/15 22:24, Kevin Oberman wrote: > Or the code in portsnap could be modified to get the current > running version. I thought about this today but it won't work as advertised: someone (currently me) still have to tweak the portsnap builder con

Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-06 Thread Kevin Oberman
On Thu, Aug 6, 2015 at 9:58 PM, Jamie Landeg-Jones wrote: > Kevin Oberman wrote: > > > Isn't rebuilding the index useful for people running STABLE? I assume > that > > I need a current index to get useful output from "pkg version -vL=". I am > > probably a bit unusual in that I keep a current po

Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-06 Thread Jamie Landeg-Jones
Kevin Oberman wrote: > Isn't rebuilding the index useful for people running STABLE? I assume that > I need a current index to get useful output from "pkg version -vL=". I am > probably a bit unusual in that I keep a current ports tre on a STABLE > system, but there are a couple of ports that I ne

Re: Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-06 Thread Kevin Oberman
On Thu, Aug 6, 2015 at 5:19 PM, Xin Li wrote: > Hi, > > Currently the default portsnap.conf would generate INDEX-11, INDEX-10 > and INDEX-9. The INDEX file is only used for searching ports, and only > one (INDEX-${OSREL:R}) file is actually used. > > Traditionally, we create all supported INDEX-

Proposal: make portsnap generate INDEX-${OSREL:R} only by default

2015-08-06 Thread Xin Li
Hi, Currently the default portsnap.conf would generate INDEX-11, INDEX-10 and INDEX-9. The INDEX file is only used for searching ports, and only one (INDEX-${OSREL:R}) file is actually used. Traditionally, we create all supported INDEX-* files by default, but the only users who would benefit fro

Re: Instant panic while trying run ports-mgmt/poudriere

2015-08-06 Thread Mateusz Guzik
On Thu, Aug 06, 2015 at 11:33:28PM +0200, Pawel Pekala wrote: > Hi K., > > On 2015-08-06 12:33 -0700, "K. Macy" wrote: > >Is this still happening? > > Still crashes: > > Thu Aug 6 23:22:05 CEST 2015 > > FreeBSD blaviken.slowicza.org 11.0-CURRENT FreeBSD 11.0-CURRENT #50 r286370: > Thu Aug 6

Re: Instant panic while trying run ports-mgmt/poudriere

2015-08-06 Thread Pawel Pekala
Hi K., On 2015-08-06 12:33 -0700, "K. Macy" wrote: >Is this still happening? Still crashes: Thu Aug 6 23:22:05 CEST 2015 FreeBSD blaviken.slowicza.org 11.0-CURRENT FreeBSD 11.0-CURRENT #50 r286370: Thu Aug 6 19:55:29 CEST 2015 r...@blaviken.slowicza.org:/usr/obj/hdd/src/sys/GENERIC am

Re: Instant panic while trying run ports-mgmt/poudriere

2015-08-06 Thread K. Macy
Is this still happening? On Jul 15, 2015 1:41 PM, "Pawel Pekala" wrote: > Hi John-Mark, > > On 2015-07-15 11:05 -0700, John-Mark Gurney wrote: > >Please repost the entire panic message, and the back trace w/o X > >running... Also, if you could share the core and kernel w/ me (you can > >email m

[head up!] WiFi drivers changes

2015-08-06 Thread Gleb Smirnoff
Hi! As part of the "opaque ifnet project" [1], all 802.11 (WiFi) drivers undergo change of not being an interface anymore. Historically in FreeBSD 802.11 stack, 802.11 devices called if_attach() and created an interface. Later this was generalized and real functioning interface is created by n

Re: CFT: ndis(4) testers needed!

2015-08-06 Thread Gleb Smirnoff
On Thu, Aug 06, 2015 at 07:49:56AM +, Thomas Mueller wrote: T> > I ended with doing the aforementioned 2 changes as one. T> T> > The diff is living here: T> T> > https://reviews.freebsd.org/D2655 T> T> > It spans the net80211 layer and converts (almost) all 802.11 drivers T> > to new KPI. No

Re: CFT: ndis(4) testers needed!

2015-08-06 Thread Thomas Mueller
> I ended with doing the aforementioned 2 changes as one. > The diff is living here: > https://reviews.freebsd.org/D2655 > It spans the net80211 layer and converts (almost) all 802.11 drivers > to new KPI. Now it also converts if_ndis, and this is the change I > am asking you to test. > Unlike